linux-kernel - USB autosuspend and turning of usb pendrive leds

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-next>] [day] [month] [year] [list]

Date:	Fri, 21 Sep 2007 15:28:36 +0200
From:	Hans de Goede <j.w.r.degoede@....nl>
To:	linux-kernel <linux-kernel@...r.kernel.org>
CC:	Hans de Goede <j.w.r.degoede@....nl>
Subject: USB autosuspend and turning of usb pendrive leds

Hi All,

Please keep me CC-ed as I'm not subscribed.

Some time ago a mail about turning of the leds on usb pendrives once unmounted 
by hal was send to the fedora-devel list:
https://www.redhat.com/archives/fedora-devel-list/2007-August/msg01807.html

This mail talked about echo 2 > power/state for usb devices.

I tested the method described in the mail to turn of the drive light and it 
worked well.

As I think that turning of the drive led (as windows does) would be good visual 
feedback to the end user that its safe to remove the device I've written a 
patch for hal which does the power state change automatically when the last 
partition of a usb massstorage device gets unmounted.

However when testing the patch I found out that my now newer kernel no longer 
has power/state for usb devices, it only has power/level. I can send suspend to 
power/level, but then remounting the device won't work and me syslog fills 
itself with:
sd 2:0:0:0: [sdc] READ CAPACITY failed
sd 2:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
sd 2:0:0:0: [sdc] Sense not available.
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 00 00 00 00
sd 2:0:0:0: [sdc] Assuming drive cache: write through

Because hal keeps polling the device.

So this leads me to a couple of questions:
1) Would it be possible to funtionality to the kernel to suspend a device in
    such a way that it will automatically unsuspend when used again?
2) Would it be possible to still make the polls succeed then with out
    unsuspending the device (or atleast without doing something that would make
    the led light again, what makes the led light exactly is unknown), or should
    hal stop polling then?

Note I'm aware that some usb devices may not like being suspended, but thats a 
problem for later, if this cannot be made to work with devices which do handle 
suspend properly, then thinking about white and/or blacklisting it irrelevant.

Regards,

Hans

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