From: Sebastian Parschauer <sebastian.riemer@profitbricks.com>
To: Fam Zheng <famz@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Eduardo Otubo <eduardo.otubo@profitbricks.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
virtualization@lists.linux-foundation.org
Subject: Re: blk-mq v3.18: Oops during virtio_blk hot-unplug
Date: Mon, 12 Jan 2015 10:30:21 +0100 [thread overview]
Message-ID: <54B3942D.2080006@profitbricks.com> (raw)
In-Reply-To: <20150110012036.GC8570@fam-t430.nay.redhat.com>
On 10.01.2015 02:20, Fam Zheng wrote:
> On Fri, 01/09 15:32, Sebastian Parschauer wrote:
>> Hi Jens,
>>
>> my colleague Eduardo is sporadically seeing an Oops in blk-mq while
>> running continuous virtio_blk hot-plug/hot-unplug tests with I/O to the
>> device within an x86_64 QEMU/KVM 2.0 Debian Wheezy VM.
>>
>> Please find the call trace attached and the full log here:
>> http://paste.ubuntu.com/9691873/
>>
>> The kernel image has been taken from here and is the mainline kernel
>> from tag v3.18:
>> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-vivid/
>>
>> Is there still an issue with block queue freezing?
>
> This one?
>
> commit 45a9c9d909b24c6ad0e28a7946e7486e73010319
> Author: Bart Van Assche <bvanassche@acm.org>
> Date: Tue Dec 9 16:57:48 2014 +0100
>
> blk-mq: Fix a use-after-free
>
> Fam
Yes, pretty much looks like it, thanks!
Cheers,
Sebastian
prev parent reply other threads:[~2015-01-12 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 14:32 blk-mq v3.18: Oops during virtio_blk hot-unplug Sebastian Parschauer
2015-01-10 1:20 ` Fam Zheng
2015-01-12 9:30 ` Sebastian Parschauer [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=54B3942D.2080006@profitbricks.com \
--to=sebastian.riemer@profitbricks.com \
--cc=axboe@kernel.dk \
--cc=eduardo.otubo@profitbricks.com \
--cc=famz@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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