mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
	Len Brown <len.brown@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: Linux 2.6.28-rc5
Date: Sun, 16 Nov 2008 18:50:23 +0100	[thread overview]
Message-ID: <20081116185023.0c8c6717@neptune.home> (raw)
In-Reply-To: <alpine.LFD.2.00.0811160917220.3468@nehalem.linux-foundation.org>

On Sun, 16 November 2008 Linus Torvalds wrote:
> On Sun, 16 Nov 2008, Bruno Prémont wrote:
> > 
> > The following change is guilty on my machine (though I could not
> > find the matching commit on git.kernel.org :( )
> 
> It's commit 0794469da3f7b2093575cbdfc1108308dd3641ce: "ACPI: struct
> device 
> - replace bus_id with dev_name(), dev_set_name()", and yes, it seems 
> totally buggy. It replaced a test for "dev->bus" with
> "dev_name(dev)", which makes no sense.

Looks like the reason I couldn't find it was old cache on
git.kernel.org or something like that as the matching commit
now shows up.

> > Reverting the change below makes the error go away.
> 
> Does this smaller patch just make it go away?
Yes, that smaller patch fixes it as well

> That said, that whole function looks potentially buggy. Len - why is
> it safe to do "list_for_each_safe()" when you drop the
> acpi_device_lock in the middle? The "next" pointer that we look up
> may go away while the lock is dropped, I think.
> 
> 		Linus
> 
> ---
>  drivers/acpi/sleep/proc.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/acpi/sleep/proc.c b/drivers/acpi/sleep/proc.c
> index 64e591b..4dbc227 100644
> --- a/drivers/acpi/sleep/proc.c
> +++ b/drivers/acpi/sleep/proc.c
> @@ -366,7 +366,7 @@ acpi_system_wakeup_device_seq_show(struct
> seq_file *seq, void *offset) dev->wakeup.state.enabled ? "enabled" :
> "disabled"); if (ldev)
>  			seq_printf(seq, "%s:%s",
> -				   dev_name(ldev) ?
> ldev->bus->name : "no-bus",
> +				   ldev->bus ? ldev->bus->name :
> "no-bus", dev_name(ldev));
>  		seq_printf(seq, "\n");
>  		put_device(ldev);
> 

      reply	other threads:[~2008-11-16 17:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-15 22:55 Linus Torvalds
2008-11-15 23:34 ` [git pull] PCMCIA updates and fixes for 2.6.28-rc5 Dominik Brodowski
2008-11-16 13:04 ` Linux 2.6.28-rc5 Bruno Prémont
2008-11-16 13:59   ` Frans Pop
2008-11-16 17:25   ` Linus Torvalds
2008-11-16 17:50     ` Bruno Prémont [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081116185023.0c8c6717@neptune.home \
    --to=bonbons@linux-vserver.org \
    --cc=gregkh@suse.de \
    --cc=kay.sievers@vrfy.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®