From: "Måns Rullgård" <mru@kth.se>
To: linux-kernel@vger.kernel.org
Subject: Re: Future devfs plans (sorry for previous incomplete message)
Date: Mon, 26 Jul 2004 11:09:51 +0200 [thread overview]
Message-ID: <yw1xzn5nrv6o.fsf@kth.se> (raw)
In-Reply-To: 20040726062435.GA22559@thump.bur.st
Trent Lloyd <lathiat@bur.st> writes:
> Wouldn't a possible solution to do this to develop an extension to tmpfs to
> catch files accessed that don't exist etc and use that in conjuction
> with udev?
There is a problem with that scheme. Imagine that a program attempts
to access a non-existing device. The special fs would call modprobe
or similar which would load the correct module. Loading this module
would cause hotplug events upon which udev would create the device
node. However, all this is asynchronous. The special fs could wait
for a while for the device to appear, but this doesn't quite look like
a nice solution. The exit status of modprobe can't be used, since
even if the module loads perfectly it might not cause the requested
device to be created. Even if it does, there will be some delay from
the module being loaded to udev creating the device node, so how long
should the kernel wait for the device to appear? I haven't thought
about it further, but I smell races here.
--
Måns Rullgård
mru@kth.se
next prev parent reply other threads:[~2004-07-26 9:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 17:37 Future devfs plans (sorry for previous incomplete message) Adam J. Richter
2004-07-26 3:34 ` Tim Connors
2004-07-26 6:24 ` Trent Lloyd
2004-07-26 6:32 ` Norberto Bensa
2004-07-26 7:11 ` Alexander E. Patrakov
2004-07-26 9:09 ` Måns Rullgård [this message]
2004-07-28 0:12 ` Trent Lloyd
2004-07-28 1:43 ` Måns Rullgård
2004-07-26 9:38 ` Ville Herva
2004-07-27 1:03 ` Matt Mackall
2004-07-28 3:16 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2004-07-28 4:16 Adam J. Richter
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=yw1xzn5nrv6o.fsf@kth.se \
--to=mru@kth.se \
--cc=linux-kernel@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