From: Sasha Levin <levinsasha928@gmail.com>
To: michaelc@cs.wisc.edu, JBottomley@parallels.com
Cc: Dave Jones <davej@redhat.com>,
open-iscsi@googlegroups.com, linux-scsi@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [BUG] Hang (deadlock?) inside iscsi_if_rx
Date: Tue, 24 Jan 2012 09:30:47 -0500 [thread overview]
Message-ID: <1327415447.15015.0.camel@lappy> (raw)
Hi all,
I got the following hang when running trinity under KVM tool:
[ 2520.824250] INFO: task trinity:31986 blocked for more than 120 seconds.
[ 2520.825513] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 2520.826983] trinity D 0000000000000000 5504 31986 2767 0x00000004
[ 2520.828416] ffff88000a21ba98 0000000000000086 ffff88000a3f8000 ffff88000a3f8000
[ 2520.829892] 00000000001d4340 ffff88000a21bfd8 ffff88000a21a000 00000000001d4340
[ 2520.831380] 00000000001d4340 00000000001d4340 ffff88000a21bfd8 00000000001d4340
[ 2520.832838] Call Trace:
[ 2520.837089] [<ffffffff8265297a>] schedule+0x3a/0x50
[ 2520.837983] [<ffffffff82651049>] __mutex_lock_common+0x209/0x5b0
[ 2520.839181] [<ffffffff81af64f3>] ? iscsi_if_rx+0x23/0xa00
[ 2520.840232] [<ffffffff81053943>] ? sched_clock+0x13/0x20
[ 2520.841242] [<ffffffff81af64f3>] ? iscsi_if_rx+0x23/0xa00
[ 2520.842271] [<ffffffff82651430>] mutex_lock_nested+0x40/0x50
[ 2520.843353] [<ffffffff81af64f3>] iscsi_if_rx+0x23/0xa00
[ 2520.844461] [<ffffffff810dfffd>] ? sub_preempt_count+0x9d/0xd0
[ 2520.845576] [<ffffffff82654130>] ? _raw_read_unlock+0x30/0x60
[ 2520.846705] [<ffffffff8221632e>] netlink_unicast+0x1ae/0x1f0
[ 2520.847790] [<ffffffff82216ae7>] netlink_sendmsg+0x227/0x350
[ 2520.848884] [<ffffffff821a490d>] ? sock_update_netprioidx+0xdd/0x1b0
[ 2520.850105] [<ffffffff821a4882>] ? sock_update_netprioidx+0x52/0x1b0
[ 2520.851282] [<ffffffff8219e376>] sock_aio_write+0x166/0x180
[ 2520.852317] [<ffffffff810dfe51>] ? get_parent_ip+0x11/0x50
[ 2520.853342] [<ffffffff811d0b1a>] do_sync_write+0xda/0x120
[ 2520.854347] [<ffffffff81109c42>] ? lock_release_holdtime+0xb2/0x160
[ 2520.855533] [<ffffffff810dfe51>] ? get_parent_ip+0x11/0x50
[ 2520.856569] [<ffffffff817914e7>] ? security_file_permission+0x27/0xb0
[ 2520.857756] [<ffffffff811d0ccc>] vfs_write+0x16c/0x180
[ 2520.858713] [<ffffffff811d0dcf>] sys_write+0x4f/0xa0
[ 2520.859680] [<ffffffff826553f9>] system_call_fastpath+0x16/0x1b
[ 2520.873039] 1 lock held by trinity/31986:
[ 2520.873801] #0: (rx_queue_mutex){+.+...}, at: [<ffffffff81af64f3>] iscsi_if_rx+0x23/0xa00
[ 2520.875587] Kernel panic - not syncing: hung_task: blocked tasks
>From looking at the logs, there were two instances of the fuzzer blocked on a write() to a netlink socket. There are no iSCSI targets anywhere on the network.
Thanks.
--
Sasha.
next reply other threads:[~2012-01-24 14:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 14:30 Sasha Levin [this message]
2012-01-24 16:29 ` [BUG] Hang (deadlock?) inside iscsi_if_rx Mike Christie
2012-01-24 16:32 ` Mike Christie
2012-01-24 16:51 ` Sasha Levin
2012-01-26 2:17 ` Mike Christie
2012-01-26 2:20 ` Mike Christie
2012-01-26 3:18 ` Sasha Levin
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=1327415447.15015.0.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=JBottomley@parallels.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=open-iscsi@googlegroups.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