From: Oliver Neukum <Oliver.Neukum@lrz.uni-muenchen.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: getting device info from device node
Date: Wed, 05 Jun 2002 08:13:34 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-102326488625448@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-102322904803349@msgid-missing>
Am Mittwoch, 5. Juni 2002 00:19 schrieben Sie:
> On Wed, Jun 05, 2002 at 12:13:18AM +0200, Oliver Neukum wrote:
> > Hi Greg,
> >
> > I must disagree. The most basic thing about configuring
> > a device is identifying it. You must be able to tell what it is.
> >
> > However I think I found a relatively clean way.
> > You can return a name from an ioctl().
> > You just can't return the one human readable name.
> > You can return a name which is unique and can only
> > be used while the device is still plugged in.
>
> Great, how does the kernel create this "name"?
I'd suggest a fixed prefix+pid+counter.
What it actually is doesn't matter if it's unique.
It's simply a directory with the files in it hard links
to the files in the persistent directory.
The trick is that we refuse to open files in it, if the
name has been invalidated by device removal.
I am not sure how much of the vfs locking we could use.
I am not Al Viro, that's why it didn't occur to me earlier.
Regards
Oliver
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2002-06-05 8:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 22:13 getting device info from device node Oliver Neukum
2002-06-04 22:19 ` Greg KH
2002-06-05 8:13 ` Oliver Neukum [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-hotplug-102326488625448@msgid-missing \
--to=oliver.neukum@lrz.uni-muenchen.de \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).