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

Greg,

I wrote:
> I think you're telling me you won't accept either of:
> 
> a. uio_device_name()
> b. uio_device_chrdev()
[ snip ]
> With no sysfs, I cannot think of a way to get hold of the minor number allocated
> to this instance of the Linux UIO device, and without that I can't open() the
> device driver.

Would you consider :

	extern int uio_device_minor(struct uio_info *info);

?

That would allow me to reconstitute the coordinates of the Linux UIO device
instance from a combination of /proc/devices and a uio_device_minor() query.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ