INFO: task hung in mon_bin_ioctl

4 views
Skip to first unread message

syzbot

unread,
Sep 10, 2018, 3:31:05 AM9/10/18
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 9a5682765a2e Merge branch 'x86-urgent-for-linus' of git://..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=154db571400000
kernel config: https://syzkaller.appspot.com/x/.config?x=8f59875069d721b6
dashboard link: https://syzkaller.appspot.com/bug?extid=b2379ebbc4b8ea43fd6f
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [ar...@arndb.de gre...@linuxfoundation.org
jrdr....@gmail.com kees...@chromium.org linux-...@vger.kernel.org
linu...@vger.kernel.org pombr...@nexb.com tg...@linutronix.de
vi...@zeniv.linux.org.uk zai...@redhat.com]

Unfortunately, I don't have any reproducer for this crash yet.

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+b2379e...@syzkaller.appspotmail.com

INFO: task syz-executor2:16206 blocked for more than 140 seconds.
Not tainted 4.19.0-rc2+ #230
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor2 D25632 16206 5359 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2825 [inline]
__schedule+0x86c/0x1ed0 kernel/sched/core.c:3473
irq bypass consumer (token 0000000096e69149) registration fails: -16
schedule+0xfe/0x460 kernel/sched/core.c:3517
irq bypass consumer (token 00000000fdbaf828) registration fails: -16
schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:3575
__mutex_lock_common kernel/locking/mutex.c:1003 [inline]
__mutex_lock+0xbfb/0x1710 kernel/locking/mutex.c:1073
mutex_lock_nested+0x16/0x20 kernel/locking/mutex.c:1088
mon_bin_ioctl+0xa98/0xe30 drivers/usb/mon/mon_bin.c:1007
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0x1de/0x1720 fs/ioctl.c:685
ksys_ioctl+0xa9/0xd0 fs/ioctl.c:702
__do_sys_ioctl fs/ioctl.c:709 [inline]
__se_sys_ioctl fs/ioctl.c:707 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:707
do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x457099
Code: fd b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7
48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff
ff 0f 83 cb b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f7c81988c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f7c819896d4 RCX: 0000000000457099
RDX: 0000000000000000 RSI: 0000000000009205 RDI: 0000000000000007
RBP: 0000000000930140 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 00000000004cf910 R14: 00000000004c5b6e R15: 0000000000000001

Showing all locks held in the system:
1 lock held by khungtaskd/985:
#0: 0000000088586870 (rcu_read_lock){....}, at:
debug_show_all_locks+0xd0/0x424 kernel/locking/lockdep.c:4436
2 locks held by getty/5308:
#0: 00000000406058b2 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x32/0x40 drivers/tty/tty_ldsem.c:353
#1: 000000000c85d5ea (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/5309:
#0: 00000000d229d1b4 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x32/0x40 drivers/tty/tty_ldsem.c:353
#1: 0000000000c03c3a (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/5310:
#0: 000000002f422120 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x32/0x40 drivers/tty/tty_ldsem.c:353
#1: 0000000098dd8281 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/5311:
#0: 000000005ddbdfe0 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x32/0x40 drivers/tty/tty_ldsem.c:353
#1: 000000009812e7ae (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/5312:
#0: 00000000b406d98d (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x32/0x40 drivers/tty/tty_ldsem.c:353
#1: 00000000454cf461 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/5313:
#0: 00000000a488b372 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x32/0x40 drivers/tty/tty_ldsem.c:353
#1: 000000000b7a3802 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/5314:
#0: 0000000087a97f64 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x32/0x40 drivers/tty/tty_ldsem.c:353
#1: 00000000cfa6534e (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
1 lock held by syz-executor0/5360:
#0: 00000000889f157f (&rq->lock){-.-.}, at: rq_lock
kernel/sched/sched.h:1821 [inline]
#0: 00000000889f157f (&rq->lock){-.-.}, at: __schedule+0x236/0x1ed0
kernel/sched/core.c:3411
1 lock held by syz-executor2/16198:
#0: 000000009b0ac50c (&rp->fetch_lock){+.+.}, at: mon_bin_read+0x60/0x640
drivers/usb/mon/mon_bin.c:813
1 lock held by syz-executor2/16206:
#0: 000000009b0ac50c (&rp->fetch_lock){+.+.}, at:
mon_bin_ioctl+0xa98/0xe30 drivers/usb/mon/mon_bin.c:1007
1 lock held by syz-executor2/16873:
#0: 00000000d4eeedf8 (&rp->fetch_lock){+.+.}, at: mon_bin_read+0x60/0x640
drivers/usb/mon/mon_bin.c:813
1 lock held by syz-executor1/17734:
#0: 00000000a4c4043e (&rp->fetch_lock){+.+.}, at: mon_bin_read+0x60/0x640
drivers/usb/mon/mon_bin.c:813
1 lock held by syz-executor1/17796:
#0: 0000000037636999 (&rp->fetch_lock){+.+.}, at: mon_bin_read+0x60/0x640
drivers/usb/mon/mon_bin.c:813
1 lock held by syz-executor1/17801:
#0: 0000000037636999 (&rp->fetch_lock){+.+.}, at:
mon_bin_ioctl+0xa98/0xe30 drivers/usb/mon/mon_bin.c:1007
1 lock held by syz-executor2/18063:
#0: 0000000079a041c7 (&rp->fetch_lock){+.+.}, at: mon_bin_read+0x60/0x640
drivers/usb/mon/mon_bin.c:813
1 lock held by syz-executor2/18113:
#0: 0000000079a041c7 (&rp->fetch_lock){+.+.}, at: mon_bin_read+0x60/0x640
drivers/usb/mon/mon_bin.c:813
1 lock held by syz-executor2/18768:
#0: 0000000064b53fd1 (&rp->fetch_lock){+.+.}, at: mon_bin_read+0x60/0x640
drivers/usb/mon/mon_bin.c:813
1 lock held by syz-executor1/19154:
#0: 00000000f0bba767 (&rp->fetch_lock){+.+.}, at: mon_bin_read+0x60/0x640
drivers/usb/mon/mon_bin.c:813
1 lock held by syz-executor2/19300:
#0: 000000002fdab185 (&rp->fetch_lock){+.+.}, at: mon_bin_read+0x60/0x640
drivers/usb/mon/mon_bin.c:813
1 lock held by syz-executor2/21313:
#0: 00000000ed9a1364 (&rp->fetch_lock){+.+.}, at: mon_bin_read+0x60/0x640
drivers/usb/mon/mon_bin.c:813
1 lock held by syz-executor0/21371:
#0: 00000000fbb43a59 (&sb->s_type->i_mutex_key#12){+.+.}, at: inode_lock
include/linux/fs.h:738 [inline]
#0: 00000000fbb43a59 (&sb->s_type->i_mutex_key#12){+.+.}, at:
__sock_release+0x8b/0x250 net/socket.c:578
1 lock held by syz-executor2/21381:
#0: 00000000e883e439 (&rp->fetch_lock){+.+.}, at: mon_bin_read+0x60/0x640
drivers/usb/mon/mon_bin.c:813

=============================================

NMI backtrace for cpu 0
CPU: 0 PID: 985 Comm: khungtaskd Not tainted 4.19.0-rc2+ #230
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1c4/0x2b4 lib/dump_stack.c:113
nmi_cpu_backtrace.cold.3+0x63/0xa2 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x1b3/0x1ed lib/nmi_backtrace.c:62
arch_trigger_cpumask_backtrace+0x14/0x20 arch/x86/kernel/apic/hw_nmi.c:38
trigger_all_cpu_backtrace include/linux/nmi.h:144 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:204 [inline]
watchdog+0xb3e/0x1050 kernel/hung_task.c:265
kthread+0x35a/0x420 kernel/kthread.c:246
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:413
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt+0x6/0x10
arch/x86/include/asm/irqflags.h:57


---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.

syzbot

unread,
Mar 8, 2019, 6:11:05 PM3/8/19
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages