syzbot


INFO: task hung in nbd_ioctl

Status: upstream: reported C repro on 2019/10/12 13:11
Reported-by: syzbot+15643e4cfffac60a87ed@syzkaller.appspotmail.com
First crash: 1031d, last: 35d

Fix bisection: failed (bisect log)
similar bugs (7):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.14 INFO: task hung in nbd_ioctl C done 18 956d 1030d 1/1 fixed on 2019/12/28 10:32
linux-4.14 INFO: task hung in nbd_ioctl (2) C done 16 703d 948d 1/1 fixed on 2020/10/21 11:01
upstream INFO: task hung in nbd_ioctl (2) 37 710d 763d 17/23 fixed on 2020/09/25 01:17
upstream INFO: task hung in nbd_ioctl C done 71 1008d 1043d 14/23 fixed on 2019/11/06 12:39
upstream INFO: task hung in nbd_ioctl (3) C done unreliable 21 13h26m 680d 0/23 upstream: reported C repro on 2020/09/28 07:17
linux-4.14 INFO: task hung in nbd_ioctl (3) C inconclusive 12 82d 634d 0/1 upstream: reported C repro on 2020/11/13 07:37
upstream INFO: task can't die in nbd_ioctl C done 7 168d 673d 0/23 upstream: reported C repro on 2020/10/05 07:20

Sample crash report:
block nbd0: shutting down sockets
INFO: task syz-executor869:8141 blocked for more than 140 seconds.
      Not tainted 4.19.171-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor869 D27544  8141   8140 0x00000004
Call Trace:
 context_switch kernel/sched/core.c:2828 [inline]
 __schedule+0x887/0x2040 kernel/sched/core.c:3517
 schedule+0x8d/0x1b0 kernel/sched/core.c:3561
 schedule_timeout+0x92d/0xfe0 kernel/time/timer.c:1794
 do_wait_for_common kernel/sched/completion.c:83 [inline]
 __wait_for_common kernel/sched/completion.c:104 [inline]
 wait_for_common+0x29c/0x470 kernel/sched/completion.c:115
 flush_workqueue+0x40b/0x13e0 kernel/workqueue.c:2715
 nbd_start_device_ioctl drivers/block/nbd.c:1268 [inline]
 __nbd_ioctl drivers/block/nbd.c:1339 [inline]
 nbd_ioctl+0x75b/0xbe0 drivers/block/nbd.c:1379
 __blkdev_driver_ioctl block/ioctl.c:303 [inline]
 blkdev_ioctl+0x5cb/0x1a80 block/ioctl.c:601
 block_ioctl+0xe9/0x130 fs/block_dev.c:1906
 vfs_ioctl fs/ioctl.c:46 [inline]
 file_ioctl fs/ioctl.c:501 [inline]
 do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688
 ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705
 __do_sys_ioctl fs/ioctl.c:712 [inline]
 __se_sys_ioctl fs/ioctl.c:710 [inline]
 __x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710
 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x444fc9
Code: Bad RIP value.
RSP: 002b:00007ffd997800e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000000000444fc9
RDX: 00000000ffffffff RSI: 000000000000ab03 RDI: 0000000000000005
RBP: 00000000006cf018 R08: 00000000004002e0 R09: 00000000004002e0
R10: 00000000004002e0 R11: 0000000000000246 R12: 0000000000402190
R13: 0000000000402220 R14: 0000000000000000 R15: 0000000000000000

Showing all locks held in the system:
1 lock held by khungtaskd/1567:
 #0: 00000000020e6db6 (rcu_read_lock){....}, at: debug_show_all_locks+0x53/0x265 kernel/locking/lockdep.c:4440
2 locks held by kworker/u5:0/1713:
 #0: 0000000078638dba ((wq_completion)"knbd%d-recv"nbd->index){+.+.}, at: process_one_work+0x767/0x1570 kernel/workqueue.c:2126
 #1: 000000006f64415f ((work_completion)(&args->work)){+.+.}, at: process_one_work+0x79c/0x1570 kernel/workqueue.c:2130

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

NMI backtrace for cpu 0
CPU: 0 PID: 1567 Comm: khungtaskd Not tainted 4.19.171-syzkaller #0
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+0x1fc/0x2ef lib/dump_stack.c:118
 nmi_cpu_backtrace.cold+0x63/0xa2 lib/nmi_backtrace.c:101
 nmi_trigger_cpumask_backtrace+0x1a6/0x1f0 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:146 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:203 [inline]
 watchdog+0x991/0xe60 kernel/hung_task.c:287
 kthread+0x33f/0x460 kernel/kthread.c:259
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4691 Comm: systemd-journal Not tainted 4.19.171-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__bpf_prog_run32+0x14/0xd0 kernel/bpf/core.c:1436
Code: 75 0c 48 81 c4 20 01 00 00 5b 5d 41 5c c3 e8 a3 35 cb ff 0f 1f 00 48 b8 00 00 00 00 00 fc ff df 41 54 49 89 fc 55 48 89 f5 53 <48> 81 ec 00 01 00 00 48 89 e3 48 c7 04 24 b3 8a b5 41 48 c7 44 24
RSP: 0018:ffff8880a0d9fba0 EFLAGS: 00000246
RAX: dffffc0000000000 RBX: ffff8880a25b4a40 RCX: ffffffff81628dd7
RDX: 0000000000000000 RSI: ffffc900019d3038 RDI: ffff8880a0d9fe70
RBP: ffffc900019d3038 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000007 R11: 0000000000000000 R12: ffff8880a0d9fe70
R13: 000000007fff0000 R14: 0000000000000000 R15: 000000007fff0000
FS:  00007f361b7068c0(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3618adc000 CR3: 00000000a109e000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 seccomp_run_filters+0x124/0x590 kernel/seccomp.c:211
 __seccomp_filter+0x93/0xca0 kernel/seccomp.c:667
 __secure_computing+0xfc/0x360 kernel/seccomp.c:794
 syscall_trace_enter+0x563/0xd60 arch/x86/entry/common.c:121
 do_syscall_64+0x486/0x620 arch/x86/entry/common.c:283
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f361a9c29c7
Code: 83 c4 08 48 3d 01 f0 ff ff 73 01 c3 48 8b 0d c8 d4 2b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 b8 15 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d a1 d4 2b 00 f7 d8 64 89 01 48
RSP: 002b:00007ffc85fe4158 EFLAGS: 00000246 ORIG_RAX: 0000000000000015
RAX: ffffffffffffffda RBX: 00007ffc85fe7180 RCX: 00007f361a9c29c7
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00005622f4c3a9a3
RBP: 00007ffc85fe42a0 R08: 00005622f4c303e5 R09: 0000000000000018
R10: 0000000000000069 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00005622f5b208a0 R15: 00007ffc85fe4790

Crashes (74):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci2-linux-4-19 2021/01/27 23:37 linux-4.19.y c4ff839de17f a57db36f .config log report syz C INFO: task hung in nbd_ioctl
ci2-linux-4-19 2020/02/15 20:44 linux-4.19.y 9b15f7fae677 5d7b90f1 .config log report syz C
ci2-linux-4-19 2020/09/20 23:38 linux-4.19.y 015e94d0e37b 9564d2e9 .config log report syz
ci2-linux-4-19 2022/07/05 06:55 linux-4.19.y 3f8a27f9e27b bff65f44 .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2022/07/04 21:57 linux-4.19.y 3f8a27f9e27b bff65f44 .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2022/07/02 09:43 linux-4.19.y 3f8a27f9e27b 1434eec0 .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2022/06/27 16:33 linux-4.19.y 3f8a27f9e27b a371c43c .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2022/06/27 13:07 linux-4.19.y 3f8a27f9e27b a371c43c .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2022/06/27 00:25 linux-4.19.y 3f8a27f9e27b a371c43c .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2022/06/26 11:35 linux-4.19.y 3f8a27f9e27b a371c43c .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2022/06/05 00:59 linux-4.19.y 3f8a27f9e27b c8857892 .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2022/04/17 19:42 linux-4.19.y 3f8a27f9e27b 8bcc32a6 .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2022/04/17 03:46 linux-4.19.y 3f8a27f9e27b 8bcc32a6 .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2022/04/13 09:38 linux-4.19.y 3f8a27f9e27b faabdb86 .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2022/02/23 04:28 linux-4.19.y 3f8a27f9e27b 6e821dbf .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2022/02/19 16:27 linux-4.19.y 3f8a27f9e27b 3cd800e4 .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2022/01/31 19:26 linux-4.19.y 3f8a27f9e27b a491ad2d .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2022/01/18 07:35 linux-4.19.y 3f8a27f9e27b 731a2d23 .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2021/12/06 13:37 linux-4.19.y 3f8a27f9e27b 579a8754 .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2021/11/25 22:46 linux-4.19.y 3f8a27f9e27b 63eeac02 .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2021/11/23 09:38 linux-4.19.y 3f8a27f9e27b 545ab074 .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2021/09/29 00:09 linux-4.19.y c2276d585654 d82cb927 .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2021/09/25 06:26 linux-4.19.y 2950c9c5e0df 8cac236e .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2021/09/24 03:18 linux-4.19.y 2950c9c5e0df 8cac236e .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2021/08/25 20:24 linux-4.19.y 59456c9cc40c b599f2fc .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2021/07/06 12:44 linux-4.19.y 9f84340f012e 6c4484eb .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2021/07/05 00:09 linux-4.19.y 9f84340f012e 55aa55c2 .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2021/07/01 09:59 linux-4.19.y 9f84340f012e 658ebc66 .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2021/06/12 20:25 linux-4.19.y 9a2dc0e6c531 1ba81399 .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2021/05/28 13:22 linux-4.19.y 6b7b0056defc 858ea628 .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2021/05/27 09:42 linux-4.19.y 6b7b0056defc 858ea628 .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2021/05/19 02:29 linux-4.19.y 3c8c23092588 a343ba6b .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2021/05/15 18:55 linux-4.19.y 3c8c23092588 93f844de .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2021/04/10 00:02 linux-4.19.y b4454811f122 6a81331a .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2021/03/12 09:16 linux-4.19.y 030194a5b292 429d8a6b .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2021/02/28 09:03 linux-4.19.y 2d19be4653f5 4c37c133 .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2021/02/26 13:04 linux-4.19.y 2d19be4653f5 4c37c133 .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2021/02/18 01:20 linux-4.19.y 811218eceeaa 14052202 .config log report info INFO: task hung in nbd_ioctl
ci2-linux-4-19 2020/09/08 08:11 linux-4.19.y c37da90efff5 abf9ba4f .config log report
ci2-linux-4-19 2020/09/07 19:43 linux-4.19.y c37da90efff5 abf9ba4f .config log report
ci2-linux-4-19 2020/07/27 12:36 linux-4.19.y 20b3a3dfdf6c cb93dc6a .config log report
ci2-linux-4-19 2020/07/03 08:23 linux-4.19.y 399849e4654e f30c14bf .config log report
ci2-linux-4-19 2020/06/27 08:23 linux-4.19.y a39e75458e1c ffec44b5 .config log report
ci2-linux-4-19 2020/06/03 16:03 linux-4.19.y 4707d8e57273 a5ce5de0 .config log report
ci2-linux-4-19 2020/05/11 16:36 linux-4.19.y 033c4ea49a4b f8f57555 .config log report
ci2-linux-4-19 2020/04/02 02:03 linux-4.19.y 54b4fa6d3955 a34e2c33 .config log report
ci2-linux-4-19 2020/04/01 03:52 linux-4.19.y 54b4fa6d3955 a34e2c33 .config log report
ci2-linux-4-19 2020/03/31 09:45 linux-4.19.y 54b4fa6d3955 c8d1cc20 .config log report
ci2-linux-4-19 2020/03/03 02:21 linux-4.19.y a083db76118d 4a4e0509 .config log report
ci2-linux-4-19 2020/03/03 00:07 linux-4.19.y a083db76118d 4a4e0509 .config log report
ci2-linux-4-19 2020/02/16 05:26 linux-4.19.y 9b15f7fae677 5d7b90f1 .config log report
ci2-linux-4-19 2020/02/15 18:34 linux-4.19.y 9b15f7fae677 5d7b90f1 .config log report
ci2-linux-4-19 2020/02/10 23:09 linux-4.19.y b499cf4b3a90 d9e55b05 .config log report
ci2-linux-4-19 2019/12/24 18:55 linux-4.19.y 672481c2deff be5c2c81 .config log report
ci2-linux-4-19 2019/12/17 09:57 linux-4.19.y 312017a460d5 d13d7958 .config log report
ci2-linux-4-19 2019/11/05 08:33 linux-4.19.y ef244c308885 76630fc9 .config log report
ci2-linux-4-19 2019/11/02 19:25 linux-4.19.y ef244c308885 997ccc67 .config log report
ci2-linux-4-19 2019/11/02 18:50 linux-4.19.y ef244c308885 997ccc67 .config log report
ci2-linux-4-19 2019/10/31 12:08 linux-4.19.y ef244c308885 a41ca8fa .config log report
ci2-linux-4-19 2019/10/30 17:57 linux-4.19.y ef244c308885 5ea87a66 .config log report
ci2-linux-4-19 2019/10/30 17:33 linux-4.19.y ef244c308885 5ea87a66 .config log report
ci2-linux-4-19 2019/10/30 11:26 linux-4.19.y ef244c308885 5ea87a66 .config log report
ci2-linux-4-19 2019/10/27 07:14 linux-4.19.y c3038e718a19 25bb509e .config log report
ci2-linux-4-19 2019/10/24 23:24 linux-4.19.y c3038e718a19 d01bb02a .config log report
ci2-linux-4-19 2019/10/22 08:10 linux-4.19.y c3038e718a19 c59a7cd8 .config log report
ci2-linux-4-19 2019/10/20 08:54 linux-4.19.y c3038e718a19 8c88c9c1 .config log report
ci2-linux-4-19 2019/10/20 03:01 linux-4.19.y c3038e718a19 8c88c9c1 .config log report
ci2-linux-4-19 2019/10/19 20:28 linux-4.19.y c3038e718a19 8c88c9c1 .config log report
ci2-linux-4-19 2019/10/19 09:58 linux-4.19.y c3038e718a19 8c88c9c1 .config log report
ci2-linux-4-19 2019/10/19 06:39 linux-4.19.y c3038e718a19 8c88c9c1 .config log report
ci2-linux-4-19 2019/10/18 02:55 linux-4.19.y c3038e718a19 8c88c9c1 .config log report
ci2-linux-4-19 2019/10/12 21:01 linux-4.19.y dafd634415a7 426631dd .config log report
ci2-linux-4-19 2019/10/12 17:24 linux-4.19.y dafd634415a7 426631dd .config log report
ci2-linux-4-19 2019/10/12 12:10 linux-4.19.y dafd634415a7 426631dd .config log report