From: Oliver.Neukum@lrz.uni-muenchen.de
To: linux-hotplug@vger.kernel.org
Subject: Re: hotplug (was devfs)
Date: Wed, 13 Nov 2002 14:15:01 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-103719698302880@msgid-missing> (raw)
On Wed, 13 Nov 2002, Nick Craig-Wood wrote:
> On Tue, Nov 12, 2002 at 01:51:08PM +0100, Oliver Neukum wrote:
> > > Actually, here's a question: are /sbin/hotplug upcalls serialized in
> > > some fashion? I'd hate to online a thousand devices in my disk array
> > > and have the machine forkbomb itself.
> >
> > Nope, no serialisation. You don't have any guarantee even that
> > addition will be delivered before removal.
>
> And that is why (we finally discovered) we were getting
> non-deterministic device numbering of USB nodes.
>
> We have machines with 6 x 4 port USB <-> serial converters attached.
> These would get randomly assigned usb device ids and hence random
> /dev/ttyUSB nodes. Not very useful when there is a load of different
> things attached to the 24 serial ports!
Please clarify. Did this happen if you connected a hub these gadgets
sit on? Do you use the same type of device six times ?
> Sometimes we also found that one of the devices wouldn't get
> initialised properly.
>
> We fixed these problems by removing hotplug and loading the relevant
> kernel modules in the correct order and voila a perfectly
Modules ? Plural?
> deterministic order for the /dev/ttyUSBs with all devices initialised.
> Plugging in our USB bus with 24 devices on it does indeed produce a
> mini-forkbomb effect ;-) (Especially since these Keyspan devices are
> initialised twice - once without firmware and once with firmware.)
There's a further problem.
> So - perhaps hotplug ought to be serialised?
Definitely, but how far?
Regards
Oliver
-------------------------------------------------------
This sf.net email is sponsored by: Are you worried about
your web server security? Click here for a FREE Thawte
Apache SSL Guide and answer your Apache SSL security
needs: http://www.gothawte.com/rd523.html
_______________________________________________
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
next reply other threads:[~2002-11-13 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 14:15 Oliver.Neukum [this message]
2002-11-13 15:14 ` hotplug (was devfs) David Brownell
2002-11-13 15:48 ` Nick Craig-Wood
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-103719698302880@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).