linux-kernel - Re: [PATCH] USB: Only enable autosuspend by default on certain device classes

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: <200708030701.11404.david-b@pacbell.net>
Date:	Fri, 3 Aug 2007 07:01:11 -0700
From:	David Brownell <david-b@...bell.net>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	Rogan Dawes <lists@...es.za.net>,
	Oliver Neukum <oliver@...kum.org>, Greg KH <gregkh@...e.de>,
	Alan Stern <stern@...land.harvard.edu>,
	linux-usb-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] USB: Only enable autosuspend by   default on certain device classes

On Friday 03 August 2007, Matthew Garrett wrote:
> On Fri, Aug 03, 2007 at 02:26:43PM +0200, Rogan Dawes wrote:
>
> > Which one is more likely to conclude at some point?

Good question ... though "how will it conclude" is also relevant.

> > Compare that to:
> > 
> > "My USB printer broke, guess I'd better report it to LKML".

Which is, as I pointed out, the wrong response.  Desktoppy
people should be making their tools do more intelligent things
with new USB devices they see ... like updating databases of
broken devices, and configuring *this* system to know that of
the devices it regularly deals with, this handful is broken.

Remember, these are the same users who wouldn't know what an
LKML is (do you plug them into the USB port??) if it bit them.

> But while this is still a likely probability, the chances are no 
> distribution is going to ship with CONFIG_USB_SUSPEND enabled.

So you're saying all the distros want to make PM problems worse?

And that with all the other desktoppy stuff they're doing, not one
of them is willing to help make things better?

Pardon me if I want to hear distro vendors agree with you before I
believe that.

> Breaking  
> people's hardware (even if, at a fundamental level, it's the hardware 
> that's broken) generally irritates users - and I suspect that the users 
> it'll irritate the most are the ones who won't report it to LKML.

Having a laptop drain its battery an hour before it needs to is
also irritating.  (As are the extortionate prices for each model's
unique batteries, but that's a different issue.)

-
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/