syzbot


INFO: task hung in blk_trace_ioctl (4)

Status: upstream: reported C repro on 2023/11/30 21:17
Subsystems: block trace
[Documentation on labels]
Reported-by: syzbot+ed812ed461471ab17a0c@syzkaller.appspotmail.com
First crash: 230d, last: 10d
Cause bisection: introduced by (bisect log) :
commit 0d345996e4cb573f8cc81d49b3ee9a7fd2035bef
Author: Pengfei Xu <pengfei.xu@intel.com>
Date: Mon Jul 31 03:04:18 2023 +0000

  x86/kernel: increase kcov coverage under arch/x86/kernel folder

Crash: INFO: task hung in blk_trace_ioctl (log)
Repro: C syz .config
  
Discussions (7)
Title Replies (including bot) Last reply
[syzbot] Monthly trace report (Apr 2024) 0 (1) 2024/04/30 07:11
[syzbot] Monthly block report (Apr 2024) 0 (1) 2024/04/12 13:18
[syzbot] Monthly trace report (Feb 2024) 0 (1) 2024/02/27 09:32
[syzbot] Monthly trace report (Jan 2024) 0 (1) 2024/01/26 21:55
[syzbot] Monthly trace report (Dec 2023) 0 (1) 2023/12/27 09:18
[PATCH next] trace/blktrace: fix task hung in blk_trace_ioctl 4 (4) 2023/12/03 11:45
[syzbot] [block?] [trace?] INFO: task hung in blk_trace_ioctl (4) 1 (6) 2023/12/02 02:54
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in blk_trace_ioctl trace block 3 1989d 2069d 0/26 auto-closed as invalid on 2019/06/04 08:29
upstream INFO: task hung in blk_trace_ioctl (2) block trace 4 1589d 1699d 0/26 auto-closed as invalid on 2020/04/09 23:38
upstream INFO: task hung in blk_trace_ioctl (3) trace block 2 899d 964d 0/26 closed as invalid on 2022/02/07 19:19
linux-4.19 INFO: task hung in blk_trace_ioctl 1 653d 653d 0/1 auto-obsoleted due to no activity on 2022/12/01 07:14
Last patch testing requests (9)
Created Duration User Patch Repo Result
2024/05/07 12:08 47m retest repro linux-next report log
2024/05/07 12:08 33m retest repro upstream report log
2024/02/23 01:24 19m retest repro upstream report log
2024/01/05 23:59 17m retest repro linux-next report log
2023/12/15 01:03 18m retest repro upstream report log
2023/12/02 02:54 1h37m eadavis@qq.com patch https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git 8c9660f65153 OK log
2023/12/02 02:44 50m eadavis@qq.com patch https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git 8c9660f65153 report log
2023/12/02 02:14 17m eadavis@qq.com patch https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git 8c9660f65153 report log
2023/12/02 01:25 21m eadavis@qq.com patch https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git 8c9660f65153 report log

Sample crash report:
INFO: task syz-executor375:5188 blocked for more than 143 seconds.
      Not tainted 6.7.0-rc2-syzkaller-00242-g090472ed9c92 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor375 state:D stack:29536 pid:5188  tgid:5186  ppid:5101   flags:0x00000006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5376 [inline]
 __schedule+0xedb/0x5af0 kernel/sched/core.c:6688
 __schedule_loop kernel/sched/core.c:6763 [inline]
 schedule+0xe9/0x270 kernel/sched/core.c:6778
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6835
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0x5b9/0x9d0 kernel/locking/mutex.c:747
 blk_trace_ioctl+0xc9/0x290 kernel/trace/blktrace.c:736
 blkdev_common_ioctl+0x1575/0x1ce0 block/ioctl.c:562
 blkdev_ioctl+0x249/0x770 block/ioctl.c:627
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:871 [inline]
 __se_sys_ioctl fs/ioctl.c:857 [inline]
 __x64_sys_ioctl+0x18f/0x210 fs/ioctl.c:857
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x40/0x110 arch/x86/entry/common.c:82
 entry_SYSCALL_64_after_hwframe+0x63/0x6b
RIP: 0033:0x7f481a2ef249
RSP: 002b:00007f4819a8a238 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f481a37a418 RCX: 00007f481a2ef249
RDX: 0000000000000000 RSI: 0000000000001276 RDI: 0000000000000004
RBP: 00007f481a37a410 R08: 00007ffcfb8fb137 R09: 00007f4819a8a6c0
R10: 0000000000000000 R11: 0000000000000246 R12: 6c756e2f7665642f
R13: 000000000000006e R14: 00007ffcfb8fb050 R15: 00007ffcfb8fb138
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/29:
 #0: ffffffff8cfabce0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:301 [inline]
 #0: ffffffff8cfabce0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:747 [inline]
 #0: ffffffff8cfabce0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x75/0x340 kernel/locking/lockdep.c:6613
2 locks held by getty/4828:
 #0: ffff88802630a0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x24/0x80 drivers/tty/tty_ldisc.c:243
 #1: ffffc90002f062f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0xfc6/0x1490 drivers/tty/n_tty.c:2201
2 locks held by syz-executor375/5187:
1 lock held by syz-executor375/5188:
 #0: ffff888140fd10a0 (&q->debugfs_mutex){+.+.}-{3:3}, at: blk_trace_ioctl+0xc9/0x290 kernel/trace/blktrace.c:736
1 lock held by syz-executor375/5190:
 #0: ffff888140fd10a0 (&q->debugfs_mutex){+.+.}-{3:3}, at: blk_trace_ioctl+0xc9/0x290 kernel/trace/blktrace.c:736
1 lock held by syz-executor375/5191:
 #0: ffff888140fd10a0 (&q->debugfs_mutex){+.+.}-{3:3}, at: blk_trace_ioctl+0xc9/0x290 kernel/trace/blktrace.c:736
1 lock held by syz-executor375/5194:
 #0: ffff888140fd10a0 (&q->debugfs_mutex){+.+.}-{3:3}, at: blk_trace_ioctl+0xc9/0x290 kernel/trace/blktrace.c:736
1 lock held by syz-executor375/5197:
 #0: ffff888140fd10a0 (&q->debugfs_mutex){+.+.}-{3:3}, at: blk_trace_ioctl+0xc9/0x290 kernel/trace/blktrace.c:736
1 lock held by syz-executor375/5195:
 #0: ffff888140fd10a0 (&q->debugfs_mutex){+.+.}-{3:3}, at: blk_trace_ioctl+0xc9/0x290 kernel/trace/blktrace.c:736
1 lock held by syz-executor375/5196:
 #0: ffff888140fd10a0 (&q->debugfs_mutex){+.+.}-{3:3}, at: blk_trace_ioctl+0xc9/0x290 kernel/trace/blktrace.c:736
1 lock held by syz-executor375/5205:
 #0: ffff888140fd10a0 (&q->debugfs_mutex){+.+.}-{3:3}, at: blk_trace_ioctl+0xc9/0x290 kernel/trace/blktrace.c:736
1 lock held by syz-executor375/5206:
 #0: ffff888140fd10a0 (&q->debugfs_mutex){+.+.}-{3:3}, at: blk_trace_ioctl+0xc9/0x290 kernel/trace/blktrace.c:736
1 lock held by syz-executor375/5209:
 #0: ffff888140fd10a0 (&q->debugfs_mutex){+.+.}-{3:3}, at: blk_trace_ioctl+0xc9/0x290 kernel/trace/blktrace.c:736
1 lock held by syz-executor375/5210:
 #0: ffff888140fd10a0 (&q->debugfs_mutex){+.+.}-{3:3}, at: blk_trace_ioctl+0xc9/0x290 kernel/trace/blktrace.c:736

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

NMI backtrace for cpu 1
CPU: 1 PID: 29 Comm: khungtaskd Not tainted 6.7.0-rc2-syzkaller-00242-g090472ed9c92 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x277/0x390 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x299/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
 watchdog+0xf87/0x1210 kernel/hung_task.c:379
 kthread+0x2c6/0x3a0 kernel/kthread.c:388
 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 5187 Comm: syz-executor375 Not tainted 6.7.0-rc2-syzkaller-00242-g090472ed9c92 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
RIP: 0010:on_stack arch/x86/include/asm/stacktrace.h:58 [inline]
RIP: 0010:__unwind_start+0x536/0x880 arch/x86/kernel/unwind_orc.c:758
Code: 89 c6 49 89 cd 4d 01 e6 4d 01 e5 e9 b6 00 00 00 41 80 7d 00 00 48 8b 43 08 0f 85 cd 01 00 00 48 39 c5 4c 8b 7b 10 48 89 04 24 <72> 5f e8 23 6b 4d 00 4c 39 fd 73 55 e8 19 6b 4d 00 48 8b 04 24 48
RSP: 0018:ffffc9000477f3e8 EFLAGS: 00000206
RAX: ffffc90004778000 RBX: ffffc9000477f448 RCX: 1ffff920008efe8b
RDX: ffff88807c9d1dc0 RSI: ffffffff813a1fa7 RDI: 0000000000000005
RBP: ffffc9000477f4d8 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000001 R11: dffffc0000000000 R12: dffffc0000000000
R13: fffff520008efe8b R14: fffff520008efe8a R15: ffffc90004780000
FS:  00007f4819aab6c0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f88f12c2580 CR3: 000000004c482000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 unwind_start arch/x86/include/asm/unwind.h:64 [inline]
 arch_stack_walk+0xaf/0x170 arch/x86/kernel/stacktrace.c:24
 stack_trace_save+0x96/0xd0 kernel/stacktrace.c:122
 save_stack+0x160/0x1f0 mm/page_owner.c:128
 __set_page_owner+0x1f/0x60 mm/page_owner.c:192
 set_page_owner include/linux/page_owner.h:31 [inline]
 post_alloc_hook+0x2d0/0x350 mm/page_alloc.c:1537
 prep_new_page mm/page_alloc.c:1544 [inline]
 get_page_from_freelist+0xa25/0x36d0 mm/page_alloc.c:3312
 __alloc_pages+0x22e/0x2420 mm/page_alloc.c:4568
 alloc_pages_mpol+0x258/0x5f0 mm/mempolicy.c:2133
 relay_alloc_buf kernel/relay.c:121 [inline]
 relay_create_buf kernel/relay.c:162 [inline]
 relay_open_buf.part.0+0x27d/0xba0 kernel/relay.c:384
 relay_open_buf kernel/relay.c:536 [inline]
 relay_open+0x641/0xab0 kernel/relay.c:517
 do_blk_trace_setup+0x4a9/0xaa0 kernel/trace/blktrace.c:591
 __blk_trace_setup+0xd8/0x180 kernel/trace/blktrace.c:631
 blk_trace_ioctl+0x163/0x290 kernel/trace/blktrace.c:741
 blkdev_ioctl+0x111/0x770 block/ioctl.c:622
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:871 [inline]
 __se_sys_ioctl fs/ioctl.c:857 [inline]
 __x64_sys_ioctl+0x18f/0x210 fs/ioctl.c:857
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x40/0x110 arch/x86/entry/common.c:82
 entry_SYSCALL_64_after_hwframe+0x63/0x6b
RIP: 0033:0x7f481a2ef249
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 81 1c 00 00 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 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f4819aab238 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f481a37a408 RCX: 00007f481a2ef249
RDX: 0000000020000380 RSI: 00000000c0481273 RDI: 0000000000000004
RBP: 00007f481a37a400 R08: 00007f4819aab6c0 R09: 00007f4819aab6c0
R10: 00007f4819aab6c0 R11: 0000000000000246 R12: 6c756e2f7665642f
R13: 0000000000000016 R14: 00007ffcfb8fb050 R15: 00007ffcfb8fb138
 </TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 2.563 msecs

Crashes (26):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/11/27 00:50 upstream 090472ed9c92 5b429f39 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in blk_trace_ioctl
2023/11/26 21:05 linux-next 8c9660f65153 5b429f39 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in blk_trace_ioctl
2024/03/12 17:11 upstream 855684c7d938 c35c26ec .config strace log report syz [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in blk_trace_ioctl
2024/04/23 05:13 upstream 4d2008430ce8 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in blk_trace_ioctl
2024/04/07 23:27 upstream fe46a7dd189e ca620dd8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in blk_trace_ioctl
2024/04/01 13:22 upstream fe46a7dd189e 6baf5069 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in blk_trace_ioctl
2024/03/30 22:09 upstream 480e035fc4c7 6baf5069 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in blk_trace_ioctl
2024/03/30 22:09 upstream 480e035fc4c7 6baf5069 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in blk_trace_ioctl
2024/03/23 06:12 upstream fe46a7dd189e 0ea90952 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in blk_trace_ioctl
2024/03/10 18:16 upstream 005f6f34bd47 6ee49f2e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in blk_trace_ioctl
2024/03/05 21:26 upstream 90d35da658da f39a7eed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in blk_trace_ioctl
2024/02/24 14:01 upstream 603c04e27c3e 8d446f15 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in blk_trace_ioctl
2024/02/23 16:48 upstream ffd2cb6b718e 8d446f15 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in blk_trace_ioctl
2024/02/01 16:50 upstream 6764c317b6bb 81024119 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in blk_trace_ioctl
2024/01/31 18:47 upstream 2a6526c4f389 373b66cd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in blk_trace_ioctl
2024/01/25 10:10 upstream 443b349019f2 1e153dc8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in blk_trace_ioctl
2024/01/24 07:58 upstream 615d30064886 1e153dc8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in blk_trace_ioctl
2024/01/11 05:32 upstream acc657692aed 04815ef1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in blk_trace_ioctl
2024/01/07 07:49 upstream 52b1853b080a d0304e9c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in blk_trace_ioctl
2023/12/22 23:00 upstream 8afe6f0e0e25 fb427a07 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in blk_trace_ioctl
2023/12/16 18:34 upstream c8e97fc6b4c0 3222d10c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in blk_trace_ioctl
2023/11/30 22:49 upstream 3b47bc037bd4 f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in blk_trace_ioctl
2023/09/30 22:44 upstream 9f3ebbef746f 8e26a358 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in blk_trace_ioctl
2024/01/30 22:47 linux-next 596764183be8 7f400fcb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in blk_trace_ioctl
2024/01/16 17:21 linux-next 8d04a7e2ee3f 2a7bcc7f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in blk_trace_ioctl
2023/11/26 17:05 linux-next 8c9660f65153 5b429f39 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in blk_trace_ioctl
* Struck through repros no longer work on HEAD.