linux-kernel - Re: [PATCH] PM: Do not create wakeup sysfs files for devices that cannot wake up (v2)

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.1102061024150.20379-100000@netrider.rowland.org>
Date:	Sun, 6 Feb 2011 10:29:24 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
cc:	LKML <linux-kernel@...r.kernel.org>,
	Linux PM mailing list <linux-pm@...ts.linux-foundation.org>,
	Minchan Kim <minchan.kim@...il.com>, Greg KH <greg@...ah.com>
Subject: Re: [PATCH] PM: Do not create wakeup sysfs files for devices that
 cannot wake up (v2)

On Sun, 6 Feb 2011, Rafael J. Wysocki wrote:

> Hi,
> 
> Below is the next version of the patch changing the PM core to only create
> wakeup sysfs files for devices that are wakeup-capable.  It contains a change
> in drivers/usb/core/hub.c that should avoid the problem described in the thread
> at https://lkml.org/lkml/2011/2/5/108 , but I'm not 100% it's the right
> approach.  Please have a look.

Yes, that's right -- in fact, it's exactly the same as what I was going
to do.  Of course, it should be separated out into a separate patch, to
be applied before the other wakeup changes.

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/