linux-kernel - Re: RFC: UIO null parent for __uio_register_device and uio_device

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: <4D376079.8020108@ixiacom.com>
Date:	Wed, 19 Jan 2011 14:06:49 -0800
From:	Earl Chew <echew@...acom.com>
To:	"Hans J. Koch" <hjk@...sjkoch.de>
CC:	Greg KH <greg@...ah.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: RFC: UIO  null parent for __uio_register_device and uio_device_name()

Hans Koch wrote:
> There's a small library with helper functions. Among other things, they
> allow searching the UIO device node by name (the name you gave your device
> in uio_info->name). The library is here:
> 
> git://git.linutronix.de/projects/libUIO.git
> 
> or with gitweb:
> 
> http://git.linutronix.de/gitweb.cgi?p=projects/libUIO.git;a=summary

Hans, Greg,

I appreciate the chance to discuss this change with you. I do understand your
point of view, and I can see how libUIO navigates sysfs from userspace
to figure out what's there.

Unfortunately I am not in a position to mandate the inclusion of sysfs in our
deployment, and Linux UIO has a dependency on sysfs to be usable.

I had hoped to stay within the confines of the mainline, but for now
we'll have to tolerate a local patch.

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