From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Xiangliang Yu <yuxiangl@marvell.com>,
Jack Wang <jack_wang@usish.com>,
"JBottomley@parallels.com" <JBottomley@parallels.com>,
Lindar Liu <lindar_liu@usish.com>, Ankit Jain <jankit@suse.de>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: BUG: linux-2.6.39 kernel panic issue when hot-plut disk during I/O
Date: Tue, 7 Jun 2011 21:34:30 +0200 [thread overview]
Message-ID: <20110607213430.0081c9f3@stein> (raw)
In-Reply-To: <BANLkTi=xzvV+Gv0EY1GVNn+UAmrhr4-FMw@mail.gmail.com>
On Jun 07 Dan Williams wrote:
> On Mon, Jun 6, 2011 at 8:32 PM, Xiangliang Yu <yuxiangl@marvell.com> wrote:
> > 2.6.39-rc4 work fine, but 2.6.39-rc5 has kernel panic.
>
> Still smells like a regression. If you run a git bisect between those
> two versions it should be pretty straightforward to identify the
> offending commit. There were some interesting block/scsi changes in
> that window:
>
> Jens Axboe (5):
> block: kill blk_flush_plug_list() export
> cfq-iosched: read_lock() does not always imply rcu_read_lock()
> block: get rid of QUEUE_FLAG_REENTER
> block: remove stale kerneldoc member from __blk_run_queue()
> elevator: check for ELEVATOR_INSERT_SORT_MERGE in !elvpriv case too
>
> Liu Yuan (1):
> block, blk-sysfs: Fix an err return path in blk_register_queue()
>
> Tao Ma (1):
> block: Remove the extra check in queue_requests_store
>
> Tejun Heo (1):
> block: don't propagate unlisted DISK_EVENTs to userland
Or try linux 3.0-rc2 which as yet another block queue lifetime vs. hotplug
fix (which is not yet available in a 2.6.39.y kernel).
--
Stefan Richter
-=====-==-== -==- --===
http://arcgraph.de/sr/
next prev parent reply other threads:[~2011-06-07 19:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 0:05 [PATCH v2] libsas: export sas_alloc_task() Dan Williams
2011-06-03 1:47 ` Jack Wang
2011-06-03 3:27 ` BUG: linux-2.6.39 kernel panic issue when hot-plut disk during I/O Xiangliang Yu
2011-06-03 6:09 ` Dan Williams
2011-06-03 6:45 ` Xiangliang Yu
2011-06-03 7:10 ` Dan Williams
2011-06-07 3:32 ` Xiangliang Yu
2011-06-07 18:57 ` Dan Williams
2011-06-07 19:34 ` Stefan Richter [this message]
2011-06-13 7:21 ` Xiangliang Yu
2011-06-13 19:15 ` Dan Williams
2011-06-14 1:30 ` Xiangliang Yu
2011-06-03 7:13 ` Bart Van Assche
2011-06-03 7:36 ` Jack Wang
2011-06-03 9:39 ` Jack Wang
2011-06-07 7:45 ` Xiangliang Yu
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=20110607213430.0081c9f3@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=JBottomley@parallels.com \
--cc=dan.j.williams@intel.com \
--cc=jack_wang@usish.com \
--cc=jankit@suse.de \
--cc=lindar_liu@usish.com \
--cc=linux-scsi@vger.kernel.org \
--cc=yuxiangl@marvell.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