From: Douglas Gilbert <dgilbert@interlog.com>
To: Sudhakar <ssudhakarp@gmail.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: race condition between scsi device add/remove code paths in 2.6.28
Date: Fri, 23 Jan 2009 21:13:15 -0500 [thread overview]
Message-ID: <497A793B.7010103@interlog.com> (raw)
In-Reply-To: <8b62ef2d0901231608y8df423ema178ae8700173ea1@mail.gmail.com>
Sudhakar wrote:
> Hi,
>
> In our labs, we encountered a kernel crash, while stressing scsi
> device add/remove code path of 2.6.28 kernel. lsscsi output on my
> machine looks like this:
>
> *******Start******
>
> [root@IMIT2S005 ~]# lsscsi
> [0:0:0:0] disk ATA ST3250620NS 3BKS -
> [0:0:1:0] disk ATA ST3250620NS 3BKS -
> [0:0:2:0] disk ATA ST3250620NS 3BKS -
> [0:0:3:0] disk ATA ST3250620NS 3BKS -
> [0:1:0:0] disk Dell VIRTUAL DISK 1028 /dev/sda
> [1:0:0:0] cd/dvd Optiarc DVD RW AD-7190S 1.00 /dev/scd0
> [5:0:0:0] disk Linux scsi_debug 0004 /dev/sdb
As an aside, do you know why the first 4 "ATA" disks are
not showing a device node?
Doug Gilbert
next prev parent reply other threads:[~2009-01-24 2:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 0:08 race condition between scsi device add/remove code paths in 2.6.28 Sudhakar
2009-01-24 2:13 ` Douglas Gilbert [this message]
2009-01-24 5:06 ` 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=497A793B.7010103@interlog.com \
--to=dgilbert@interlog.com \
--cc=linux-scsi@vger.kernel.org \
--cc=ssudhakarp@gmail.com \
/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