From: Matthew Wilcox <matthew@wil.cx>
To: Chris Webb <chris@arachsys.com>
Cc: linux-scsi@vger.kernel.org, Arjan van de Ven <arjan@infradead.org>
Subject: Re: oops during scsi scanning disk setup
Date: Thu, 20 Aug 2009 14:01:04 -0600 [thread overview]
Message-ID: <20090820200104.GH11966@parisc-linux.org> (raw)
In-Reply-To: <20090820180549.GD7542@arachsys.com>
On Thu, Aug 20, 2009 at 07:05:49PM +0100, Chris Webb wrote:
> in Linux 2.6.30.4 x86-64 with async scsi bus scanning turned on. I've now
> seen it again a couple of times with CONFIG_SCSI_SCAN_ASYNC turned off. The
> machine locks up hard shortly after the oops.
^^^ that option
> I'm not quite clear how I can be in sd_probe_async when asynchronous bus
> scanning is compiled out completely, but perhaps I'm misunderstanding how
> this function is used.
^^^ has nothing to do with sd_probe_async.
I wrote the code covered by the former, and it's really annoying me
that people keep reporting it as buggy, when it's actually the code in
kernel/async.c that's buggy.
--
Matthew Wilcox Intel Open Source Technology Centre
"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."
next prev parent reply other threads:[~2009-08-20 20:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 18:05 oops during scsi scanning disk setup Chris Webb
2009-08-20 20:01 ` Matthew Wilcox [this message]
2009-08-20 20:10 ` Yinghai Lu
2009-08-21 4:26 ` Arjan van de Ven
2009-08-20 22:26 ` James Bottomley
2009-08-21 8:16 ` Chris Webb
2009-08-21 8:33 ` Chris Webb
2009-08-21 9:23 ` Chris Webb
2009-08-21 14:00 ` James Bottomley
2009-08-21 14:51 ` Chris Webb
2009-08-21 15:47 ` James Bottomley
2009-08-21 22:59 ` Chris Webb
2009-08-21 23:39 ` James Bottomley
2009-08-22 11:55 ` Chris Webb
2009-08-22 14:56 ` James Bottomley
2009-08-22 15:50 ` Chris Webb
2009-09-05 16:45 ` Chris Webb
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=20090820200104.GH11966@parisc-linux.org \
--to=matthew@wil.cx \
--cc=arjan@infradead.org \
--cc=chris@arachsys.com \
--cc=linux-scsi@vger.kernel.org \
/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).