linux-kernel - Re: [GIT PATCH] USB autosuspend fixes for 2.6.23-rc6

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.0709131629010.8150-100000@iolanthe.rowland.org>
Date:	Thu, 13 Sep 2007 16:31:56 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Adrian Bunk <bunk@...nel.org>
cc:	Greg KH <gregkh@...e.de>, Linus Torvalds <torvalds@...l.org>,
	Andrew Morton <akpm@...l.org>, <linux-kernel@...r.kernel.org>,
	<linux-usb-devel@...ts.sourceforge.net>,
	Oliver Neukum <oneukum@...e.de>
Subject: Re: [GIT PATCH] USB autosuspend fixes for 2.6.23-rc6

On Thu, 13 Sep 2007, Adrian Bunk wrote:

> > Maybe you're concerned about propagating updates as painlessly as 
> > possible -- if the whitelist is in the kernel then every kernel release 
> > would include an update.  But in userspace it's possible to do updates 
> > even more quickly and painlessly.  For example, there could be a 
> > network server available for both interactive lookups and automatic 
> > queries from HAL.
> >...
> 
> No, what I'm concerned about is that this would require userspace for 
> something that is completely in-kernel.

But it isn't completely in-kernel.  It is policy, and policy belongs in 
userspace.

The kernel provides the mechanism for autosuspending idle devices and 
setting the idle-delay length.  But userspace must be responsible for 
deciding what devices to autosuspend and how long the idle delays 
should be.

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/