From: Matthew Wilcox <matthew@wil.cx>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: James Smart <James.Smart@Emulex.Com>,
linux-scsi@vger.kernel.org, tore@linpro.no
Subject: Re: [Patch] plug async scan race at 1st node scan
Date: Sat, 1 Mar 2008 07:26:45 -0700 [thread overview]
Message-ID: <20080301142644.GC24386@parisc-linux.org> (raw)
In-Reply-To: <47C9419D.1040402@cs.wisc.edu>
On Sat, Mar 01, 2008 at 05:44:29AM -0600, Mike Christie wrote:
> >Possibly we should be less forgiving, and require drivers to have a
> >scan_start, otherwise they can't avoid this race.
>
> I am hitting this problem with qla4xxx (added async scanning to
> 2.6.25-rc). Was the final decision that we have to add a scan_start? I
> did not see scan_start be made mandatory and I did not see James's patch
> go in.
You can't really make it mandatory ... it's only mandatory *if* you have
a scan_finished.
The documentation should be updated though. Possibly the function
prototype should be changed from returning void to returning int, to
allow drivers to say "Oh no, I can't start after all".
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
prev parent reply other threads:[~2008-03-01 14:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 13:10 [Patch] plug async scan race at 1st node scan James Smart
2007-08-20 13:49 ` Matthew Wilcox
2007-08-20 14:02 ` James Smart
2007-08-20 14:32 ` Matthew Wilcox
2008-03-01 11:44 ` Mike Christie
2008-03-01 14:26 ` Matthew Wilcox [this message]
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=20080301142644.GC24386@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Smart@Emulex.Com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=tore@linpro.no \
/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).