From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Core scsi layer crashes in 2.6.8.1
Date: Wed, 29 Sep 2004 14:24:10 +0100 [thread overview]
Message-ID: <1096464245.15907.27.camel@localhost.localdomain> (raw)
In-Reply-To: <1096467125.2028.11.camel@mulgrave>
On Mer, 2004-09-29 at 15:11, James Bottomley wrote:
> What was the oops?
>
> I have a theory that we should be taking a device reference before
> waking up the error handler, otherwise host removal can race with error
> handling.
The sequence I scribbled down from the console was
Illegal state transition Cancel->Offline
Badness in scsi_device_set_state
scsi_device_set_state
scsi_unjam_host
scsi_error_handler
badness in kref_get
kobject_get, get_device, scsi_request_fn
blk_insert_request, scsi_queue_insert
scsi_eh_flush_done_q, scsi_unjam_host
scsi_error_handler
OOPS scsi_device_dev_release
device_release
kobject_cleanup
kobject_release
kref_put
scsi_request_fn
Alan
next prev parent reply other threads:[~2004-09-29 14:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 20:03 Core scsi layer crashes in 2.6.8.1 Alan Cox
2004-09-29 14:11 ` James Bottomley
2004-09-29 13:24 ` Alan Cox [this message]
2004-09-29 14:34 ` James Bottomley
2004-09-29 14:27 ` Matthew Wilcox
2004-10-05 11:49 ` Anton Blanchard
2004-10-05 13:56 ` James Bottomley
2004-10-05 14:44 ` Mark Lord
2004-10-05 14:56 ` James Bottomley
2004-10-05 15:46 ` Mark Lord
2004-10-05 15:49 ` Oliver Neukum
2004-10-05 15:54 ` James Bottomley
2004-10-05 15:57 ` Mark Lord
2004-10-05 16:01 ` James Bottomley
2004-10-05 16:53 ` Jeff Garzik
2004-10-05 16:01 ` Oliver Neukum
2004-10-05 16:07 ` James Bottomley
2004-10-05 16:26 ` Oliver Neukum
2004-10-05 16:38 ` 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=1096464245.15907.27.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-kernel@vger.kernel.org \
--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