linux-kernel - Re: RFC: Platform data for onboard USB assets

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:	Wed, 23 Mar 2011 16:45:48 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	andy.green@...aro.org
Cc:	Greg KH <greg@...ah.com>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Nicolas Pitre <nicolas.pitre@...aro.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Jaswinder Singh <jaswinder.singh@...aro.org>,
	Linux USB list <linux-usb@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>, roger.quadros@...ia.com,
	grant.likely@...retlab.ca
Subject: Re: RFC: Platform data for onboard USB assets

On Wednesday 23 March 2011, Andy Green wrote:
> > So again, this problem, for this device, has been solved in userspace
> > without any kernel changes needed.  If there are other devices that you,
> 
> Not sure what you mean by 'again', 'solved in userspace' and so on. 
> Your saying: "go away and do it in userspace" is different from it being 
> "solved in userspace" in reality.  The mess it would create in userspace 
> isn't acceptable.  The outcome of this is it's not fixed in the driver 
> nor userspace.

I agree, doing the device naming in user space to solve this problem would
require identifying the board with the particular bug in a table that
is kept by the distro, and we currently don't even have a way to identify
a specific board. I certainly wouldn't want to rely on things like the
recently proposed /sys/devices/socinfo for identifying whether or not we
want to rename a USB ethernet device.

	Arnd
--
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/