linux-kernel - Re: [RFC PATCH] USB: remove CONFIG_USB

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:	Thu, 26 Apr 2012 08:12:42 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
	Kay Sievers <kay@...y.org>
Subject: Re: [RFC PATCH] USB: remove CONFIG_USB_DEVICEFS

On Thu, Apr 26, 2012 at 11:06:45AM -0400, Alan Stern wrote:
> On Wed, 25 Apr 2012, Greg Kroah-Hartman wrote:
> 
> > This option has been deprecated for many years now, and no userspace
> > tools use it anymore, so it should be safe to finally remove it.
> > 
> > Reported-by: Kay Sievers <kay@...y.org>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> > 
> > ---
> > Anyone object to me queuing this up for the 3.5 kernel release?
> 
> I'm not sure about this.  There are a few systems still floating around
> that don't use udev; on those systems /proc/bus/usb is the only way for 
> user programs to control USB devices.  Admittedly, I have no idea 
> whether any such systems will be using 3.5 or later kernels...

They don't have to use udev, they can use devtmpfs (which is what the
majority of embedded systems use today), or they can just use static
device nodes to get access to these devices, the char node is still
present, we aren't getting rid of them at all.

thanks,

greg k-h
--
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/