From: Ben Collins <bcollins@debian.org>
To: Matthias Urlichs <smurf@smurf.noris.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.7-mm4: regression: ieee1394: sbp2: null pointer dereference
Date: Wed, 30 Jun 2004 11:46:24 -0400 [thread overview]
Message-ID: <20040630154623.GB18174@phunnypharm.org> (raw)
In-Reply-To: <pan.2004.06.30.04.01.10.828506@smurf.noris.de>
On Wed, Jun 30, 2004 at 06:01:10AM +0200, Matthias Urlichs wrote:
> Hi, Matthias Urlichs wrote:
>
> > 2.6.7-mm4 oopses when confronted with an unresponsive iee1394 disk.
>
> (Andrew helpfully forwarded this to 1394-dev. Thanks.)
>
> Further tests show that the problem just shows up more reliably (if that's
> the word...) under -mm4. However, I just got the error on plain 2.6.7.
This oops traces back into the scsi stack, right? The spaghetti of
trying to get things to work right with the scsi stack is getting to be
a pain. I guess USB doesn't have too many problems since it does a
scsi-host per device, but that's not as easy with sbp2 and 1394, since a
single sbp2 device can have multiple LUN's, and it's just easier to
treat that as one scsi host.
I can't reproduce it, but I'll try to get into the logic of sbp2 device
removal again to see if I can find out where and why this is occuring.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
next prev parent reply other threads:[~2004-06-30 16:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 18:13 2.6.7-mm4: regression: ieee1394: sbp2: null pointer dereference Matthias Urlichs
2004-06-30 4:01 ` Matthias Urlichs
2004-06-30 15:46 ` Ben Collins [this message]
2004-06-30 18:45 ` Matthias Urlichs
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=20040630154623.GB18174@phunnypharm.org \
--to=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smurf@smurf.noris.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.