linux-kernel - Re: [RFC][PATCH 1/10] PM: Add flag for devices capable of generating run-time wake-up events

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.0911161629310.2971-100000@iolanthe.rowland.org>
Date:	Mon, 16 Nov 2009 16:31:20 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Matthew Garrett <mjg59@...f.ucam.org>
cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	pm list <linux-pm@...ts.linux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Linux PCI <linux-pci@...r.kernel.org>,
	ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Oliver Neukum <oliver@...kum.org>,
	Shaohua Li <shaohua.li@...el.com>,
	Bjorn Helgaas <bjorn.helgaas@...com>
Subject: Re: [RFC][PATCH 1/10] PM: Add flag for devices capable of generating
 run-time wake-up events

On Mon, 16 Nov 2009, Matthew Garrett wrote:

> On Mon, Nov 16, 2009 at 04:00:49PM -0500, Alan Stern wrote:
> > On Mon, 16 Nov 2009, Rafael J. Wysocki wrote:
> > > Yes, in general.  The platform.
> > 
> > And for non-platform devices (hot-pluggable, for example)?  Presumably 
> > you would want the driver that detects and registers the device to set 
> > this flag.
> 
> Are there any cases where the bus code won't know this?

None that I'm aware of.  I merely wanted to clarify where the flag was 
supposed to get set.

> > > > What if the kernel can't tell whether or not the device can generate 
> > > > runtime wake-up events?
> > > 
> > > Do you have any specific examples in mind?
> > 
> > What about Matthew's example of an ACPI GPE which might or might not 
> > cause a runtime wake-up event, depending on the AML code in the BIOS?
> 
> The platform knows whether or not that's the case.

Okay, then it isn't a problem.  Except perhaps in the case of buggy 
devices which _should_ generate these events but don't.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/