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]

Message-ID: <4D8A10BF.8010406@linaro.org>
Date:	Wed, 23 Mar 2011 15:24:47 +0000
From:	Andy Green <andy@...mcat.com>
To:	Greg KH <greg@...ah.com>
CC:	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>, arnd@...db.de,
	roger.quadros@...ia.com, grant.likely@...retlab.ca
Subject: Re: RFC: Platform data for onboard USB assets

On 03/23/2011 03:04 PM, Somebody in the thread at some point said:
> On Wed, Mar 23, 2011 at 10:53:35AM +0000, Mark Brown wrote:
>> In the specific case of MACs and device names for network adaptors we
>> have userspace solutions which are obscuring the discussion but there
>> are other things which get configured this way which one would usually
>> expect to be handled in kernel.
>
> No, this isn't obsucuring the discussion, it's exactly the point here.
>
> I asked for concrete examples of a need for this type of thing (i.e.
> platform data on USB devices), and this was the only need cited.  I
> then pointed out that this is correctly solved in userspace, as it has
> for other devices like this, and that it's not a valid example of this
> need.
>
> 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 am currently trying working around it elsewhere in kernel along the 
lines of Alan's idea, since I am not able to fix the actual driver.

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