linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Which node has the device been bound to?
Date: Mon, 03 Jun 2002 22:46:32 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-102314455730701@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-102266789207618@msgid-missing>

On Tue, Jun 04, 2002 at 12:43:38AM +0200, Oliver Neukum wrote:
> Am Montag, 3. Juni 2002 23:58 schrieb Greg KH:
> > On Mon, Jun 03, 2002 at 11:09:36PM +0200, Oliver Neukum wrote:
> > > > But what is the real problem here?  What do you want to solve? 
> > > > Mapping of a /dev node to a physical device?  Or mapping of a
> > > > physical device to a /dev node?  Or something else?
> > >
> > > The former. The latter has some principal problems.
> > > To do the former you need to have an atomic operation on an
> > > opened device.
> > > Thus you need to have the device node open and you need
> > > the ioctl to not return a pointer to a driverfs file. You either
> > > return its content or an fd.
> >
> > Ok, I understand a bit better now (sorry, I'm slow today...).  So what
> > fd do you want returned in the ioctl()?  driverfs implements a tree for
> > every device, not a single file.  Do you want a fd for the directory?
> 
> No problem, I am dense at times, too.
> There's a problem. You cannot open() based on a directory fd,
> unless I am mistaken.

I think you are correct, that's why I asked.

> I can't come up with anything better than a set of ioctls that return
> the contents of the individual files. And I know that this is ugly.
> I don't claim that this is a good solution, just that it's the only
> solution I have and that there's a race otherwise.
> You simply cannot use names, thus parsing files for the name of the
> node won't work.

Or we could just drop the whole idea of using ioctl() and live with the
"instability" of parsing a filesystem :)

> I've thought about finding the device node to a physical device.
> It really is problematic. Firstly there can be several nodes.
> Secondly you'd need device nodes in driverfs, in effect merging it
> with devfs.

I saw a patch to driverfs that did this a while ago, but see Linus's
comments on lkml about why this will probably never happen.

thanks

greg k-h

_______________________________________________________________

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

  parent reply	other threads:[~2002-06-03 22:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-29 10:23 Which node has the device been bound to? Kim Deokhwan
2002-05-31 16:53 ` Oliver Neukum
2002-05-31 17:12 ` Dmitri
2002-05-31 18:26 ` Greg KH
2002-06-01  0:05 ` Oliver Neukum
2002-06-01  0:21 ` Greg KH
2002-06-01  1:14 ` Oliver Neukum
2002-06-03 18:00 ` Greg KH
2002-06-03 21:09 ` Oliver Neukum
2002-06-03 21:58 ` Greg KH
2002-06-03 22:43 ` Oliver Neukum
2002-06-03 22:46 ` Greg KH [this message]
2002-06-03 23:05 ` Oliver Neukum
2002-06-03 23:16 ` Greg KH
2002-06-03 23:37 ` Oliver Neukum
2002-06-03 23:50 ` Greg KH
2002-06-04 19:00 ` David Brownell

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-102314455730701@msgid-missing \
    --to=greg@kroah.com \
    --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).