From: Greg KH <greg@kroah.com>
To: Brad Hards <bhards@bigpond.net.au>
Cc: oliver@neukum.name, Brian Craft <bcboy@thecraftstudio.com>,
linux-kernel@vger.kernel.org
Subject: Re: delay before open() works
Date: Sat, 14 Sep 2002 23:49:44 -0700 [thread overview]
Message-ID: <20020915064944.GA727@kroah.com> (raw)
In-Reply-To: <200209151638.32883.bhards@bigpond.net.au>
On Sun, Sep 15, 2002 at 04:38:32PM +1000, Brad Hards wrote:
> On Sun, 15 Sep 2002 16:10, Greg KH wrote:
> > This "second" hotplug event will happen when the driver registers with
> > the "class". So for the example of the USB scanner driver, it registers
> > itself with the USB "class" to set up the file_ops structure (this is
> > done in usb_register_dev(). At that point in time, /sbin/hotplug will
> > be called again.
> This is too soon, at least for the scanner driver. Look at how much code runs
> in scanner_probe() between the fops registration and the devfs registration.
>
> Hmmm, that is probably a race anyway. Oliver?
You're right, that is a race. And is due to the historical fact that
usb_register() used to also register the fops structure at the same
time. Now that the functions are split apart, the call to
usb_register_dev() should be done at the same place as the call to
devfs_register(). Patches gladly accepted :)
thanks,
greg k-h
next prev parent reply other threads:[~2002-09-15 6:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-14 16:42 delay before open() works Brian Craft
2002-09-15 5:25 ` Brad Hards
2002-09-15 6:10 ` Greg KH
2002-09-15 6:38 ` Brad Hards
2002-09-15 6:49 ` Greg KH [this message]
2002-09-15 6:20 ` Greg KH
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=20020915064944.GA727@kroah.com \
--to=greg@kroah.com \
--cc=bcboy@thecraftstudio.com \
--cc=bhards@bigpond.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.name \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.