From: Vegard Nossum <vegard.nossum@oracle.com>
To: Eric Van Hensbergen <ericvh@gmail.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
v9fs-developer@lists.sourceforge.net,
LKML <linux-kernel@vger.kernel.org>
Subject: Hang in 9p/virtio
Date: Sat, 30 Jul 2016 23:42:18 +0200 [thread overview]
Message-ID: <579D1F3A.7020806@oracle.com> (raw)
Hi,
With fault injection triggering an allocation failure for the
alloc_indirect() call in virtqueue_add() I'm seeing a hang in
p9_virtio_zc_request() -- it seems to be waiting here indefinitely
(i.e. at least 120 seconds):
err = wait_event_interruptible(*req->wq,
req->status >= REQ_STATUS_RCVD);
Maybe somebody who is already familiar with the could would have a look?
Stack trace for the memory allocation failure:
CPU: 2 PID: 3877 Comm: trinity-c2 Not tainted 4.7.0+ #70
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
Ubuntu-1.8.2-1ubuntu1 04/01/2014
ffffffff84354a78 ffff88010594f2e8 ffffffff81d72f91 ffffffff84354a60
1ffff10020b29e62 ffff88010594f398 ffffffff81e07df7 00007faad2003fff
0000000000000064 ffffffffffffffff 0000000041b58ab3 ffffffff840a481c
Call Trace:
[...]
[<ffffffff81473886>] __kmalloc+0x66/0x2e0
[<ffffffff81f7c6b4>] alloc_indirect.isra.8+0x24/0xa0
[<ffffffff81f7d37f>] virtqueue_add_sgs+0x41f/0xc90
[<ffffffff836eb281>] p9_virtio_zc_request+0x531/0xdb0
[<ffffffff836d6ecf>] p9_client_zc_rpc.constprop.14+0x23f/0xe80
[<ffffffff836db77c>] p9_client_read+0x4bc/0x8d0
[<ffffffff8193f0a3>] v9fs_file_read_iter+0xd3/0x190
[<ffffffff814b4b62>] do_iter_readv_writev+0x212/0x490
[<ffffffff814b6be9>] do_readv_writev+0x359/0x660
[<ffffffff814babc7>] vfs_readv+0x67/0xa0
[<ffffffff814bacd8>] do_readv+0xd8/0x270
Stack trace for the stuck call:
NMI backtrace for cpu 2
CPU: 2 PID: 3877 Comm: trinity-c2 Not tainted 4.7.0+ #70
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
Ubuntu-1.8.2-1ubuntu1 04/01/2014
task: ffff8801174f5b00 task.stack: ffff880105948000
RIP: 0010:[<ffffffff810b02a0>] [<ffffffff810b02a0>]
__default_send_IPI_dest_field+0xe0/0x130
Call Trace:
[...]
[<ffffffff811d584e>] prepare_to_wait_event+0x19e/0x410
[<ffffffff836eb790>] p9_virtio_zc_request+0xa40/0xdb0
[<ffffffff836d6ecf>] p9_client_zc_rpc.constprop.14+0x23f/0xe80
[<ffffffff836db77c>] p9_client_read+0x4bc/0x8d0
[<ffffffff8193f0a3>] v9fs_file_read_iter+0xd3/0x190
[<ffffffff814b4b62>] do_iter_readv_writev+0x212/0x490
[<ffffffff814b6be9>] do_readv_writev+0x359/0x660
[<ffffffff814babc7>] vfs_readv+0x67/0xa0
[<ffffffff814bacd8>] do_readv+0xd8/0x270
Vegard
next reply other threads:[~2016-07-30 21:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 21:42 Vegard Nossum [this message]
2016-08-02 9:03 ` Hang in 9p/virtio Cornelia Huck
2016-08-02 9:13 ` Vegard Nossum
2016-08-02 13:35 ` Vegard Nossum
2016-08-02 16:35 ` Cornelia Huck
2016-08-02 16:49 ` Michael S. Tsirkin
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=579D1F3A.7020806@oracle.com \
--to=vegard.nossum@oracle.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=ericvh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=v9fs-developer@lists.sourceforge.net \
/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