From: Nick Craig-Wood <ncw1@axis.demon.co.uk>
To: Oliver Neukum <oliver@neukum.name>
Cc: Sean Neakums <sneakums@zork.net>, linux-kernel@vger.kernel.org
Subject: Re: hotplug (was devfs)
Date: Wed, 13 Nov 2002 10:48:09 +0000 [thread overview]
Message-ID: <20021113104809.D2386@axis.demon.co.uk> (raw)
In-Reply-To: <200211121351.08328.oliver@neukum.name>; from oliver@neukum.name on Tue, Nov 12, 2002 at 01:51:08PM +0100
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!
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
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.)
So - perhaps hotplug ought to be serialised?
--
Nick Craig-Wood
ncw1@axis.demon.co.uk
next prev parent reply other threads:[~2002-11-13 10:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-12 9:32 devfs Ian Molton
2002-11-12 9:43 ` devfs Xavier Bestel
2002-11-12 9:49 ` devfs john slee
2002-11-12 10:01 ` devfs Sean Neakums
2002-11-12 12:51 ` devfs Oliver Neukum
2002-11-13 10:48 ` Nick Craig-Wood [this message]
2002-11-13 17:02 ` hotplug (was devfs) Greg KH
2002-11-13 18:06 ` Nick Craig-Wood
2002-11-13 18:04 ` Greg KH
2002-11-14 11:46 ` Oliver Neukum
2002-11-12 10:05 ` devfs Xavier Bestel
2002-11-12 10:04 ` devfs Alexander Viro
2002-11-12 10:25 ` devfs Ian Molton
2002-11-12 10:46 ` devfs Dave Jones
2002-11-12 11:08 ` devfs Ian Molton
2002-11-12 11:24 ` devfs Rando Christensen
2002-11-12 13:30 ` devfs Alexander Viro
2002-11-12 14:53 ` devfs Alan Cox
2002-11-12 15:37 ` devfs Ian Molton
2002-11-12 11:29 ` devfs Helge Hafting
2002-11-12 15:40 ` devfs Greg KH
-- strict thread matches above, loose matches on Subject: below --
2002-11-13 18:45 hotplug (was devfs) Ed Vance
2002-11-13 18:45 ` Greg KH
2002-11-13 18:59 Ed Vance
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=20021113104809.D2386@axis.demon.co.uk \
--to=ncw1@axis.demon.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.name \
--cc=sneakums@zork.net \
/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