From: Matthew Wilcox <matthew@wil.cx>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-scsi@vger.kernel.org, Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: Re: Asynchronous scsi scanning, version 9
Date: Mon, 29 May 2006 07:19:00 -0600 [thread overview]
Message-ID: <20060529131900.GA20416@parisc-linux.org> (raw)
In-Reply-To: <1148908267.3291.82.camel@laptopd505.fenrus.org>
On Mon, May 29, 2006 at 03:11:07PM +0200, Arjan van de Ven wrote:
> > 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.
>
> that sounds the wrong place, at least, I would expect the wait is needed
> before starting the initramfs, since that is where some distros mount
> their root (mount-by-label and I suspect many other cases will do it
> from there, such as iscsi rootfs etc)
It's a late_initcall(), so it happens before initramfs too.
next prev parent reply other threads:[~2006-05-29 13:19 UTC|newest]
Thread overview: 41+ 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 [this message]
2006-05-31 23:21 ` Patrick Mansfield
2006-06-01 12:22 ` Kay Sievers
2006-10-26 19:53 ` maximilian attems
2006-06-01 13:14 ` Alexander E. Patrakov
2006-06-01 13:21 ` maximilian attems
2006-06-01 13:23 ` Matthew Wilcox
2006-06-01 13:26 ` Alexander E. Patrakov
2006-06-01 14:00 ` Arjan van de Ven
2006-06-25 21:15 ` James Bottomley
2006-06-25 22:46 ` Matthew Wilcox
2006-06-26 8:24 ` Arjan van de Ven
2006-06-26 12:40 ` Matthew Wilcox
2006-06-26 12:59 ` Arjan van de Ven
2006-06-26 16:03 ` Greg KH
2006-06-26 14:44 ` Matthew Dharm
2006-06-26 15:18 ` Matthew Wilcox
2006-06-26 15:44 ` James Bottomley
2006-06-26 16:02 ` Greg KH
2006-06-26 21:08 ` Matthew Dharm
2006-06-26 22:15 ` Matthew Wilcox
2006-06-26 18:55 ` [SPAM] " Doug Ledford
2006-06-26 21:04 ` Matthew Dharm
2006-06-26 21:20 ` Doug Ledford
2006-06-26 20:58 ` Linas Vepstas
2006-06-26 21:14 ` James Bottomley
2006-06-26 21:21 ` Linas Vepstas
2006-06-26 21:41 ` James Bottomley
2006-06-28 7:52 ` Hannes Reinecke
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=20060529131900.GA20416@parisc-linux.org \
--to=matthew@wil.cx \
--cc=arjan@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--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 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).