From: Jens Axboe <axboe@kernel.dk>
To: hari krishnan <p.harikrishnan22@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bug found in block/scsi_ioctl.c
Date: Wed, 5 Jun 2013 16:53:13 +0200 [thread overview]
Message-ID: <20130605145313.GC32665@kernel.dk> (raw)
In-Reply-To: <CANk961ZtHzC0cyzGc9WxC9mvqmHpixRKsavuMGMzeuLe+QA5TQ@mail.gmail.com>
On Wed, Jun 05 2013, hari krishnan wrote:
> I got a kernel crash, and dump is pointing to "IP: [<ffffffff81260e86>]
> sg_scsi_ioctl+0x166/0x3b0".
>
> Test case: *I was just deleting few NPIV port to which some of LUN's where
> exported, after sometime I was running parted on some devices"*
>
> The crash is in sg_scsi_ioctl of block/scsi_ioctl.c.
> From code and dump it seems sg_scsi_ioctl is allocating request by calling
> blk_get_request and assuming it will never fail, but it will fail if device
> is dead, here in this case some of SCSI devices are dead.
It's a known bug, Joe Lawrence has posted a patch to fix it up that will
be muscled into 3.10.
Can you give it a go?
http://www.spinics.net/lists/linux-scsi/msg66294.html
--
Jens Axboe
parent reply other threads:[~2013-06-05 14:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CANk961ZtHzC0cyzGc9WxC9mvqmHpixRKsavuMGMzeuLe+QA5TQ@mail.gmail.com>]
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=20130605145313.GC32665@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=p.harikrishnan22@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