linux-kernel - Re: [PATCH] move eject code from zd1211rw to usb-storage

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: <200912171402.42168.oliver@neukum.org>
Date:	Thu, 17 Dec 2009 14:02:41 +0100
From:	Oliver Neukum <oliver@...kum.org>
To:	Matthew Dharm <mdharm-kernel@...-eyed-alien.net>
Cc:	Dan Williams <dcbw@...hat.com>,
	Josua Dietze <digidietze@...isberghof.de>,
	Stefan Seyfried <stefan.seyfried@...glemail.com>,
	linux-usb@...r.kernel.org, linux-wireless@...r.kernel.org,
	linux-kernel@...r.kernel.org, usb-storage@...ts.one-eyed-alien.net,
	Stefan Seyfried <seife@...airon.com>
Subject: Re: [PATCH] move eject code from zd1211rw to usb-storage

Am Mittwoch, 16. Dezember 2009 20:52:58 schrieb Matthew Dharm:
> > > If this is the case, then the only reasonable answer to is to push the
> > > modeswitch code for both into udev and out of the kernel.  It will take
> > 
> > you mean usb_modeswitch, not udev actually.
> 
> That is correct; I had mis-typed.  Tho, the actual implementation is udev
> calling usb_modeswitch and/or eject.

Can storage tell the devices apart so that it knows which ones to leave
to the kernel solution and which devices to accept so that udev can
issue an eject command?

	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/