public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Matthias Urlichs" <smurf@smurf.noris.de>
To: Ben Collins <bcollins@debian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.7-mm4: regression: ieee1394: sbp2: null pointer dereference
Date: Wed, 30 Jun 2004 20:45:13 +0200	[thread overview]
Message-ID: <20040630184509.GD5389@kiste> (raw)
In-Reply-To: <20040630154623.GB18174@phunnypharm.org>

Hi,

Ben Collins:
> This oops traces back into the scsi stack, right?

Umm ... not that I know of. It basically says

                      sbp2_logout_device+0x13/0x140 [sbp2]
kernel:  [<fb2c49f1>] sbp2_update+0x21/0x80 [sbp2]

No SCSI anywhere (that I can see).

sbp2_update+0x21 points to the instruction after a call to
sbp2_logout_device(), so that matches up. GDB says the error is here:

sbp2.c:1323:	scsi_id->logout_orb->reserved1 = 0x0;

which probably means that either scsi_id or logout_orb is NULL.

>         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.
> 
So can USB; I have a card reader here which registers a different LUN
per card interface.

> 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.

FWIW, here's the device info (from gscanbus):

SelfID Info
-----------
Physical ID: 2
Link active: Yes
Gap Count: 10
PHY Speed: S400
PHY Delay: <=144ns
IRM Capable: No
Power Class: None
Port 0: Connected to parent node
Port 1: Connected to child node
Init. reset: No

CSR ROM Info
------------
GUID: 0x00A0B80A0000144F
Node Capabilities: 0x000083C0
Vendor ID: 0x0000A0B8
Unit Spec ID: 0x0000609E
Unit SW Version: 0x00010483
Model ID: 0x00000000
Nr. Textual Leafes: 2

Vendor:  SYMBIOS LOGIC INC.
Textual Leafes: 
LSI Logic
LSI 501 rev B3

AV/C Subunits
-------------
N/A



-- 
Matthias Urlichs   |   {M:U} IT Design @ m-u-it.de   |  smurf@smurf.noris.de

      reply	other threads:[~2004-06-30 18:48 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
2004-06-30 18:45     ` Matthias Urlichs [this message]

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=20040630184509.GD5389@kiste \
    --to=smurf@smurf.noris.de \
    --cc=bcollins@debian.org \
    --cc=linux-kernel@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