[9381] in linux-scsi channel archive
URGENT 2.4.0 BUG! command abort function called in interrupt!
daemon@ATHENA.MIT.EDU (Matthew Dharm)
Sun Aug 13 16:13:59 2000
Date: Sun, 13 Aug 2000 13:07:22 -0700
From: Matthew Dharm <mdharm-scsi@one-eyed-alien.net>
To: Linux SCSI list <linux-scsi@vger.rutgers.edu>
Message-ID: <20000813130722.E10455@one-eyed-alien.net>
Mail-Followup-To: Linux SCSI list <linux-scsi@vger.rutgers.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
I've confirmed the presence of (what I consider to be) an urgent 2.4.0 bug
in the scsi error handling code. For a long time I thought this was a bug
in the usb-storage code, but it's now clearly a SCSI layer bug.
The following comes from 2.4.0-test6.
This is what appears on the console:
-----------------------------------
usb-storage: command_abort() called from an interrupt!!! BAD!!! ...
usb-storage: bus_reset() requested but not implemented
usb-storage: bus_reset() requested but not implemented
usb-storage: host_reset() requested but not implemented
Note that the first line comes from the usb-storage command abort function,
and is a test to see if(in_interrupt()) -- this is the primary indication
of the bug. This function is supposed to be called from a thread context
only, and is not IRQ context safe. But, it's not supposed to have to be
IRQ safe.
Matt Dharm
--
Matthew Dharm Home: mdharm@one-eyed-alien.net
Senior Engineer, QCP Inc. Work: mdharm@qcpi.com
Department of Justice agent. I have come to purify the flock.
-- DOJ agent
User Friendly, 5/22/1998
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
