From: Roland Dreier <roland@purestorage.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Ric Wheeler <rwheeler@redhat.com>,
linux-fsdevel@vger.kernel.org,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [LSF/MM TOPIC] linux servers as a storage server - what's missing?
Date: Wed, 18 Jan 2012 11:00:19 -0800 [thread overview]
Message-ID: <CAL1RGDXX2FH_MoE-W40WOzymmfyFWVE8vmVoAUtPxufGe408EQ@mail.gmail.com> (raw)
In-Reply-To: <CAO+b5-qHGLXr7HtzV9R81sk8=h_L2i9-pR+uZ7yrGiKktsGZUQ@mail.gmail.com>
On Wed, Jan 18, 2012 at 10:51 AM, Bart Van Assche <bvanassche@acm.org> wrote:
>> cf http://www.spinics.net/lists/linux-scsi/msg56254.html
> With which SCSI low-level diver does that occur and how does the call
> stack look like ? I haven't encountered any such issues while testing
> the srp-ha patch set. However, I have to admit that the issues
> mentioned in the description of commit 3308511 were discovered while
> testing the srp-ha patch set.
I assume you're asking about the crash on hot unplug...
Anyway, I've seen it with mp2tsas, looking like
[<ffffffff8130078b>] scsi_setup_blk_pc_cmnd+0x2b/0x170
[<ffffffff8130091d>] scsi_prep_fn+0x4d/0x60
[<ffffffff81227794>] blk_peek_request+0xb4/0x240
[<ffffffff813010cd>] scsi_request_fn+0x47d/0x4b0
[<ffffffff81223bff>] __blk_run_queue+0x1f/0x80
[<ffffffff8122b808>] blk_execute_rq_nowait+0x68/0xc0
in my case I think there is some SG_IO stuff in flight
for SCSI reservations; the cdrom case I linked to also
has scsi_setup_blk_pc_cmnd in the trace and mentions
an ioctl for medium presence. So maybe regular block
IO is OK now but not non-IO commands.
- R.
next prev parent reply other threads:[~2012-01-18 19:00 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 15:59 [LSF/MM TOPIC] linux servers as a storage server - what's missing? Ric Wheeler
2011-12-22 8:14 ` Shyam_Iyer
2011-12-22 15:58 ` Vivek Goyal
2011-12-22 20:54 ` Shyam_Iyer
2011-12-23 3:06 ` Vivek Goyal
2011-12-23 4:35 ` Shyam_Iyer
2012-01-09 12:18 ` Hannes Reinecke
2012-01-09 12:59 ` Tom Coughlan
2012-01-10 6:53 ` Ric Wheeler
2012-01-20 8:55 ` Hannes Reinecke
2012-01-19 16:17 ` [LSF/MM TOPIC] linux servers as a storage server - what'smissing? Loke, Chetan
2012-01-19 16:19 ` Ric Wheeler
2012-01-19 16:26 ` Loke, Chetan
2012-01-19 16:29 ` Ric Wheeler
2012-01-19 17:32 ` Loke, Chetan
2012-01-19 17:44 ` Ric Wheeler
2012-01-19 21:30 ` Loke, Chetan
2012-01-19 21:39 ` Ric Wheeler
2012-01-24 17:05 ` Loke, Chetan
2012-01-24 18:13 ` Ric Wheeler
2012-01-26 22:24 ` Dave Chinner
2012-01-26 22:29 ` Ric Wheeler
2012-01-03 19:26 ` [LSF/MM TOPIC][ATTEND] linux servers as a storage server - what's missing? Jeff Layton
2012-01-03 19:32 ` Chuck Lever
2012-01-17 21:16 ` J. Bruce Fields
2012-01-17 21:25 ` Chuck Lever
2012-01-24 21:36 ` J. Bruce Fields
2012-01-24 23:13 ` Ric Wheeler
2012-01-25 19:05 ` Christopher R. Hertel
2012-01-25 20:25 ` Christopher R. Hertel
2012-01-25 21:56 ` Roland Dreier
2012-01-25 22:09 ` Christopher R. Hertel
2012-01-26 21:52 ` Andy Grover
2012-01-26 11:15 ` Bart Van Assche
2012-01-18 17:00 ` [LSF/MM TOPIC] " Roland Dreier
2012-01-18 17:51 ` Ric Wheeler
2012-01-18 18:46 ` Roland Dreier
2012-01-18 18:51 ` Bart Van Assche
2012-01-18 19:00 ` Roland Dreier [this message]
2012-01-19 8:16 ` Rolf Eike Beer
2012-01-19 17:50 ` Loke, Chetan
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=CAL1RGDXX2FH_MoE-W40WOzymmfyFWVE8vmVoAUtPxufGe408EQ@mail.gmail.com \
--to=roland@purestorage.com \
--cc=bvanassche@acm.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rwheeler@redhat.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;
as well as URLs for NNTP newsgroup(s).