From: James Bottomley <James.Bottomley@SteelEye.com>
To: Douglas Gilbert <dougg@torque.net>
Cc: Mike Christie <mikenc@us.ibm.com>,
Mateusz.Blaszczyk@nask.pl, Alan Stern <stern@rowland.harvard.edu>,
SCSI development list <linux-scsi@vger.kernel.org>,
Matthew Dharm <mdharm-usb@one-eyed-alien.net>,
USB development list <linux-usb-devel@lists.sourceforge.net>
Subject: Re: [linux-usb-devel] 2.6.9-rc4mm1:badness in drivers/scsi/scsi_lib.c
Date: 27 Oct 2004 09:42:11 -0400 [thread overview]
Message-ID: <1098884542.1829.3.camel@mulgrave> (raw)
In-Reply-To: <417F2BD3.5010901@torque.net>
On Wed, 2004-10-27 at 01:02, Douglas Gilbert wrote:
> I have been seeing an oops (or badness) since about the lk 2.5
> series if I left my USB Sandisk CF (ImageMate) plug in with a
> mounted file system open when I halted the machine. As the logs
> had already been closed down there was nothing captured.
Yes, that's known and expected. The devices have a complete state
transition model. Some of the states (like deleted->cancel) are
explicitly forbidden (once a device is deleted, we actually don't allow
it to do anything other than die). The attempts at bogus transitions
usually show up in error handling for a dead device.
The badness is simply a stack trace caused by a WARN_ON(1) in the code
that forbids the transition. However, for the time being I'd like to
keep it in to help us debug problems which result in an oops later.
As long as you only get "badness" messages and no oops, everything is
actually fine.
James
next prev parent reply other threads:[~2004-10-27 13:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 12:51 2.6.9-rc4mm1:badness in drivers/scsi/scsi_lib.c Mateusz.Blaszczyk
2004-10-18 15:30 ` [linux-usb-devel] " Alan Stern
2004-10-21 9:28 ` Mateusz.Blaszczyk
2004-10-21 14:41 ` Alan Stern
2004-10-26 7:57 ` Mateusz.Blaszczyk
2004-10-26 15:07 ` [linux-usb-devel] " Alan Stern
2004-10-26 18:03 ` Mike Christie
2004-10-26 18:08 ` Mike Christie
2004-10-27 1:53 ` [linux-usb-devel] " James Bottomley
2004-10-27 5:02 ` Douglas Gilbert
2004-10-27 13:42 ` James Bottomley [this message]
2004-10-27 6:41 ` Mike Christie
2004-10-27 8:29 ` [linux-usb-devel] " Mike Christie
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=1098884542.1829.3.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Mateusz.Blaszczyk@nask.pl \
--cc=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mdharm-usb@one-eyed-alien.net \
--cc=mikenc@us.ibm.com \
--cc=stern@rowland.harvard.edu \
/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).