linux-kernel - Re: usbhid driver: replacing resume or using a post resume function

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: <201001271635.26295.oliver@neukum.org>
Date:	Wed, 27 Jan 2010 16:35:26 +0100
From:	Oliver Neukum <oliver@...kum.org>
To:	"Rick L. Vinyard, Jr." <rvinyard@...nmsu.edu>
Cc:	"Jiri Kosina" <jkosina@...e.cz>,
	"Linux" <linux-kernel@...r.kernel.org>,
	"Linux USB" <linux-usb@...r.kernel.org>
Subject: Re: usbhid driver: replacing resume or using a post resume function

Am Mittwoch, 27. Januar 2010 15:57:48 schrieb Rick L. Vinyard, Jr.:
> I think the most common case would be for something like the G13 to
> re-establish settings, which from the few devices I'm familiar with would
> need to restart the hid subsystem first and then re-establish through
> feature reports, et. al. after the hid_resume().
> 
> Also, that means that usbhid's hid_resume() doesn't need to be exposed in
> the API, or even need to be usb specific.

If you do do this please document that you may use only GFP_NOIO
and GFP_ATOMIC in that context.

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