netdev - Re: [PATCH 2/7 v3] initdev:kernel:USB init device discovery notification

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]

Date:	Fri, 7 Aug 2009 11:44:50 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Alan Jenkins <sourcejedi.lkml@...glemail.com>
cc:	David VomLehn <dvomlehn@...co.com>, <linux-kernel@...r.kernel.org>,
	<akpm@...ux-foundation.org>, <linux-usb@...r.kernel.org>,
	<greg@...ah.com>, <linux-scsi@...r.kernel.org>,
	<netdev@...r.kernel.org>, <arjan@...radead.org>
Subject: Re: [PATCH 2/7 v3] initdev:kernel:USB init device discovery 
 notification

On Fri, 7 Aug 2009, Alan Jenkins wrote:

> > +/* The mask of possible USB boot devices depends on what drivers and
> > + * options have been configured into the kernel.  There are too many
> > + * USB network config options to list here, so just assume it is always
> > + * possible to have a USB network device.
> > + */
> 
> That could be fixed though.  Make the "USB Network Adaptors" menu into
> an option.  Then you just have e.g. "CONFIG_NETDEV_USB", plus the two
> class devices outside the menu (CONFIG_USB_ACM and CONFIG_USB_WDM).

That could be done.  It might even meet with the approval of the
networking maintainer, independent of this patch series.

But what if somebody adds yet another networking class driver outside
the menu?

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html