From: maximilian attems <maks@sternwelten.at>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Patrick Mansfield <patmans@us.ibm.com>,
Matthew Wilcox <matthew@wil.cx>,
linux-hotplug-devel@lists.sourceforge.net,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
linux-scsi@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: Asynchronous scsi scanning, version 9
Date: Thu, 26 Oct 2006 19:53:22 +0000 [thread overview]
Message-ID: <20061026195322.GC12013@nancy> (raw)
In-Reply-To: <1149164533.3419.38.camel@pim.off.vrfy.org>
On Thu, 01 Jun 2006, Kay Sievers wrote:
> On Wed, 2006-05-31 at 16:21 -0700, Patrick Mansfield wrote:
> > [adding hotplug-devel ... maybe Marco or Kay can comment]
> >
> > On Mon, May 29, 2006 at 07:05:15AM -0600, Matthew Wilcox wrote:
> > > On Mon, May 29, 2006 at 10:38:13AM +0200, Stefan Richter wrote:
<snipp unrelated>
> > >
> > > That's what scsi_complete_async_scans() is for. If you have a built-in
> > > module, it will wait for the async scans to finish before we get as far
> > > as trying to mount root. It does change observable behaviour in that
> > > sys_module_init() will return before scans are complete. However, I
> > > believe most distros userspace copes with this these days. For example,
> > > Debian has:
> > >
> > > # wait for the udevd childs to finish
> > > log_action_begin_msg "Waiting for /dev to be fully populated"
> > > while [ -d /dev/.udev/queue/ ]; do
> > > sleep 1
> > > udevd_timeout=$(($udevd_timeout - 1))
> > > [...]
>
> That has replaced by a binary called "udevsettle" which waits for events
> to finish, by comparing the current kernel event sequence number
> exported in sysfs with the latest handled event by udev.
usb-storage is still giving troubles in that area.
in the case of usb-storage udevsettle exists much too early.
the /sys uevent_seqnum is the same as the udev worked on,
while dmesg is saying:
usb-storage: waiting for device to settle before scanning
it would be really helpful if udevsettle would have an uevent
to wait on. [adding gregkh to cc]
> > second, and the udev queue becomes empty even though the scsi /sd scan is
> > still in progress.
>
> Right. For the settle time of usb-storage we watch for the kernel tread
> to go away. :)
bug reports don't comfirm that statement.
nor do i see any code for it in udevsettle.c.
--
maks
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
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
WARNING: multiple messages have this Message-ID (diff)
From: maximilian attems <maks@sternwelten.at>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Patrick Mansfield <patmans@us.ibm.com>,
Matthew Wilcox <matthew@wil.cx>,
linux-hotplug-devel@lists.sourceforge.net,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
linux-scsi@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: Asynchronous scsi scanning, version 9
Date: Thu, 26 Oct 2006 21:53:22 +0200 [thread overview]
Message-ID: <20061026195322.GC12013@nancy> (raw)
In-Reply-To: <1149164533.3419.38.camel@pim.off.vrfy.org>
On Thu, 01 Jun 2006, Kay Sievers wrote:
> On Wed, 2006-05-31 at 16:21 -0700, Patrick Mansfield wrote:
> > [adding hotplug-devel ... maybe Marco or Kay can comment]
> >
> > On Mon, May 29, 2006 at 07:05:15AM -0600, Matthew Wilcox wrote:
> > > On Mon, May 29, 2006 at 10:38:13AM +0200, Stefan Richter wrote:
<snipp unrelated>
> > >
> > > That's what scsi_complete_async_scans() is for. If you have a built-in
> > > module, it will wait for the async scans to finish before we get as far
> > > as trying to mount root. It does change observable behaviour in that
> > > sys_module_init() will return before scans are complete. However, I
> > > believe most distros userspace copes with this these days. For example,
> > > Debian has:
> > >
> > > # wait for the udevd childs to finish
> > > log_action_begin_msg "Waiting for /dev to be fully populated"
> > > while [ -d /dev/.udev/queue/ ]; do
> > > sleep 1
> > > udevd_timeout=$(($udevd_timeout - 1))
> > > [...]
>
> That has replaced by a binary called "udevsettle" which waits for events
> to finish, by comparing the current kernel event sequence number
> exported in sysfs with the latest handled event by udev.
usb-storage is still giving troubles in that area.
in the case of usb-storage udevsettle exists much too early.
the /sys uevent_seqnum is the same as the udev worked on,
while dmesg is saying:
usb-storage: waiting for device to settle before scanning
it would be really helpful if udevsettle would have an uevent
to wait on. [adding gregkh to cc]
> > second, and the udev queue becomes empty even though the scsi /sd scan is
> > still in progress.
>
> Right. For the settle time of usb-storage we watch for the kernel tread
> to go away. :)
bug reports don't comfirm that statement.
nor do i see any code for it in udevsettle.c.
--
maks
next prev parent reply other threads:[~2006-10-26 19:53 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 14:33 [RFC] Asynchronous scsi scanning Matthew Wilcox
2006-05-11 18:15 ` Mike Christie
2006-05-11 18:21 ` Matthew Wilcox
2006-05-11 18:49 ` Mike Christie
2006-05-11 18:56 ` Matthew Wilcox
2006-05-11 19:09 ` Mike Christie
2006-05-18 17:22 ` [PATCH] " Matthew Wilcox
2006-05-29 3:19 ` Asynchronous scsi scanning, version 9 Matthew Wilcox
2006-05-29 8:38 ` Stefan Richter
2006-05-29 13:05 ` Matthew Wilcox
2006-05-29 13:11 ` Arjan van de Ven
2006-05-29 13:19 ` Matthew Wilcox
2006-05-31 23:21 ` Patrick Mansfield
2006-05-31 23:21 ` Patrick Mansfield
2006-06-01 12:22 ` Kay Sievers
2006-06-01 12:22 ` Kay Sievers
2006-10-26 19:53 ` maximilian attems [this message]
2006-10-26 19:53 ` maximilian attems
2006-06-01 13:14 ` Alexander E. Patrakov
2006-06-01 13:14 ` Alexander E. Patrakov
2006-06-01 13:21 ` maximilian attems
2006-06-01 13:21 ` maximilian attems
2006-06-01 13:23 ` Matthew Wilcox
2006-06-01 13:23 ` Matthew Wilcox
2006-06-01 13:26 ` Alexander E. Patrakov
2006-06-01 13:26 ` Alexander E. Patrakov
2006-06-01 14:00 ` Arjan van de Ven
2006-06-01 14:00 ` Arjan van de Ven
2006-06-25 21:15 ` James Bottomley
2006-06-25 21:15 ` James Bottomley
2006-06-25 22:46 ` Matthew Wilcox
2006-06-25 22:46 ` Matthew Wilcox
2006-06-26 8:24 ` Arjan van de Ven
2006-06-26 8:24 ` Arjan van de Ven
2006-06-26 12:40 ` Matthew Wilcox
2006-06-26 12:40 ` Matthew Wilcox
2006-06-26 12:59 ` Arjan van de Ven
2006-06-26 12:59 ` Arjan van de Ven
2006-06-26 16:03 ` Greg KH
2006-06-26 16:03 ` Greg KH
2006-06-26 14:44 ` Matthew Dharm
2006-06-26 14:44 ` Matthew Dharm
2006-06-26 15:18 ` Matthew Wilcox
2006-06-26 15:18 ` Matthew Wilcox
2006-06-26 15:44 ` James Bottomley
2006-06-26 15:44 ` James Bottomley
2006-06-26 16:02 ` Greg KH
2006-06-26 16:02 ` Greg KH
2006-06-26 21:08 ` Matthew Dharm
2006-06-26 21:08 ` Matthew Dharm
2006-06-26 22:15 ` Matthew Wilcox
2006-06-26 22:15 ` Matthew Wilcox
2006-06-26 18:55 ` [SPAM] " Doug Ledford
2006-06-26 18:55 ` Doug Ledford
2006-06-26 21:04 ` Matthew Dharm
2006-06-26 21:04 ` Matthew Dharm
2006-06-26 21:20 ` Doug Ledford
2006-06-26 21:20 ` Doug Ledford
2006-06-26 20:58 ` Linas Vepstas
2006-06-26 20:58 ` Linas Vepstas
2006-06-26 21:14 ` James Bottomley
2006-06-26 21:14 ` James Bottomley
2006-06-26 21:21 ` Linas Vepstas
2006-06-26 21:21 ` Linas Vepstas
2006-06-26 21:41 ` James Bottomley
2006-06-26 21:41 ` James Bottomley
2006-06-28 7:52 ` Hannes Reinecke
2006-06-28 7:52 ` Hannes Reinecke
2006-06-28 16:03 ` James Bottomley
2006-06-28 16:03 ` James Bottomley
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=20061026195322.GC12013@nancy \
--to=maks@sternwelten.at \
--cc=gregkh@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=patmans@us.ibm.com \
--cc=stefanr@s5r6.in-berlin.de \
/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.