From: Sebastian Parschauer <sebastian.riemer@profitbricks.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Eduardo Otubo <eduardo.otubo@profitbricks.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
virtualization@lists.linux-foundation.org
Subject: blk-mq v3.18: Oops during virtio_blk hot-unplug
Date: Fri, 09 Jan 2015 15:32:04 +0100 [thread overview]
Message-ID: <54AFE664.6010002@profitbricks.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
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?
We are seeing a similar issue with v3.16 but more often as some block
queue freezing fixes have been added in v3.17.
All kernels without blk-mq used by virtio_blk (< v3.13) work fine.
Cheers,
Sebastian
[-- Attachment #2: blk-mq_3.18_virtio_blk_hot-unplug_oops.txt --]
[-- Type: text/plain, Size: 3324 bytes --]
[ 165.630508] BUG: unable to handle kernel NULL pointer dereference at (null)
[ 165.631027] IP: [<ffffffff817b1035>] __mutex_lock_slowpath+0x75/0x100
[ 165.631219] PGD 368a2067 PUD 797d3067 PMD 0
[ 165.631454] Oops: 0002 [#1] SMP
[ 165.631632] Modules linked in: parport_pc 8250_fintek pvpanic parport snd_pcm snd_timer snd soundcore i2c_piix4 joydev pcspkr psmouse serio_raw evbug mac_hid hid_generic usbhid hid floppy
[ 165.632010] CPU: 0 PID: 22838 Comm: dd Not tainted 3.18.0-031800-generic #201412071935
[ 165.632010] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
[ 165.633045] task: ffff8800685b6400 ti: ffff88007afc0000 task.ti: ffff88007afc0000
[ 165.633045] RIP: 0010:[<ffffffff817b1035>] [<ffffffff817b1035>] __mutex_lock_slowpath+0x75/0x100
[ 165.633045] RSP: 0018:ffff88007afc3c38 EFLAGS: 00010297
[ 165.633045] RAX: 0000000000000000 RBX: ffff880036b1fa08 RCX: 00000000c0000100
[ 165.633045] RDX: ffff88007afc3c40 RSI: ffff8800685b6400 RDI: ffff880036b1fa0c
[ 165.633045] RBP: ffff88007afc3c88 R08: ffff88007afc0000 R09: 0000000000000000
[ 165.633045] R10: 0000000000000001 R11: 0000000000000246 R12: ffff8800685b6400
[ 165.633045] R13: ffff880036b1fa0c R14: 00000000ffffffff R15: ffff880036b1fa10
[ 165.633045] FS: 00007fce39352700(0000) GS:ffff88007fc00000(0000) knlGS:0000000000000000
[ 165.633045] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 165.633045] CR2: 0000000000000000 CR3: 000000007ae5b000 CR4: 00000000000406f0
[ 165.633045] Stack:
[ 165.633045] ffff880036d552d8 ffff880036b1fa10 0000000000000000 ffff88007b5cf0c0
[ 165.633045] ffff88007afc3c98 ffff880036b1fa08 ffff880036d552d8 ffff880036b1f9d0
[ 165.633045] ffff8800795f3000 ffff88007b5cf0c0 ffff88007afc3ca8 ffffffff817b10e3
[ 165.633045] Call Trace:
[ 165.633045] [<ffffffff817b10e3>] mutex_lock+0x23/0x37
[ 165.633045] [<ffffffff81379706>] blk_mq_free_queue+0x26/0x1a0
[ 165.633045] [<ffffffff8136fe22>] blk_release_queue+0xa2/0x100
[ 165.633045] [<ffffffff8139f8a2>] kobject_cleanup+0x82/0x1c0
[ 165.633045] [<ffffffff8139f730>] kobject_put+0x30/0x70
[ 165.633045] [<ffffffff81369495>] blk_put_queue+0x15/0x20
[ 165.633045] [<ffffffff8137e033>] disk_release+0x93/0xd0
[ 165.633045] [<ffffffff814d27de>] device_release+0x3e/0xc0
[ 165.633045] [<ffffffff8139f8a2>] kobject_cleanup+0x82/0x1c0
[ 165.633045] [<ffffffff8139f730>] kobject_put+0x30/0x70
[ 165.633045] [<ffffffff8137c797>] put_disk+0x17/0x20
[ 165.633045] [<ffffffff812278a5>] __blkdev_put+0x125/0x1b0
[ 165.633045] [<ffffffff8122798b>] blkdev_put+0x5b/0x160
[ 165.633045] [<ffffffff81227ab5>] blkdev_close+0x25/0x30
[ 165.633045] [<ffffffff811f129d>] __fput+0xbd/0x250
[ 165.633045] [<ffffffff811f147e>] ____fput+0xe/0x10
[ 165.633045] [<ffffffff81091bc7>] task_work_run+0xa7/0xe0
[ 165.633045] [<ffffffff81014077>] do_notify_resume+0xc7/0xd0
[ 165.633045] [<ffffffff817b354f>] int_signal+0x12/0x17
[ 165.633045] Code: 00 00 8b 03 83 f8 01 0f 84 99 00 00 00 48 8b 43 10 48 8d 55 b8 4c 8d 7b 08 41 be ff ff ff ff 48 89 53 10 4c 89 7d b8 48 89 45 c0 <48> 89 10 4c 89 65 c8 eb 1f 66 90 4c 89 ef 49 c7 04 24 02 00 00
[ 165.633045] RIP [<ffffffff817b1035>] __mutex_lock_slowpath+0x75/0x100
[ 165.633045] RSP <ffff88007afc3c38>
[ 165.633045] CR2: 0000000000000000
next reply other threads:[~2015-01-09 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 14:32 Sebastian Parschauer [this message]
2015-01-10 1:20 ` blk-mq v3.18: Oops during virtio_blk hot-unplug Fam Zheng
2015-01-10 1:20 ` Fam Zheng
2015-01-12 9:30 ` Sebastian Parschauer
2015-01-12 9:30 ` Sebastian Parschauer
-- strict thread matches above, loose matches on Subject: below --
2015-01-09 14:32 Sebastian Parschauer
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=54AFE664.6010002@profitbricks.com \
--to=sebastian.riemer@profitbricks.com \
--cc=axboe@kernel.dk \
--cc=eduardo.otubo@profitbricks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.