linux-kernel - Re: UIO device name

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: <20080924093551.GB7591@linux-sh.org>
Date:	Wed, 24 Sep 2008 18:35:52 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Joakim Tjernlund <joakim.tjernlund@...nsmode.se>
Cc:	hjk@...utronix.de, gregkh@...e.de,
	Linux-Kernel <linux-kernel@...r.kernel.org>
Subject: Re: UIO device name

On Wed, Sep 24, 2008 at 11:21:33AM +0200, Joakim Tjernlund wrote:
> As far as I can see there isn't a way to name the /dev/uio%d device file
> to something more useful, is that so?
> I would like to name the device file from within the kernel so I can
> find the correct device from userspace.
> The very least is to control the minor(%d) number.
> 
You have a couple of options for this:

	- the 'name' sysfs entry for each of the uio devices, which
	  corresponds to the uio device name.
	- extracting the relevant data from things like 'lsuio'.
	- hooking in the pretty mame through udev to create an alias.

All of the information you need is available for userspace to play with,
and you want to be relying on the device name itself, not the minor
number (where you have no gaurantee of the ordering).

Documentation/DocBook/uio-howto.tmpl also has some more information on
what sort of information is exposed.
--
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/