linux-kernel - Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 20 May 2009 12:52:07 -0500
From:	Mario Limonciello <mario_limonciello@...l.com>
To:	Alan Stern <stern@...land.harvard.edu>
CC:	Oliver Neukum <oliver@...kum.org>, linux-usb@...r.kernel.org,
	Matthew Garrett <mjg59@...f.ucam.org>,
	Marcel Holtmann <marcel@...tmann.org>,
	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Explicitly disable BT radio using rfkill interface on
 suspend

Hi Alan:

Alan Stern wrote:
> On Wed, 20 May 2009, Oliver Neukum wrote:
>
>   
>
> That's okay.  Inelegant, perhaps, but workable.  Besides, as we see 
> below, the new rule would have to do more than the old rule.
>
>   
I agree this is a rather inelegant solution. A  new rule would have to
be added to hid2hci then.  It's much more preferable to be able to fix
kernel space from mucking up the device.  Is there a way to mark a
device to /not/ run reset-resume after S3?
>
> Does that create the same removal event?  If it does then you wouldd be
> in an unfortunate state.  The script would have to check somehow
> whether the removal was deliberate or spontaneous.
>   
Yes it does create the same removal event when you switch to HID mode. 
I don't know of any way that you can calculate if the switch was
intentional.


-- 
Mario Limonciello
*Dell | Linux Engineering*
mario_limonciello@...l.com


Download attachment "signature.asc" of type "application/pgp-signature" (261 bytes)