syzbot


INFO: task hung in nilfs_sufile_set_alloc_range

Status: auto-obsoleted due to no activity on 2023/04/24 13:34
Subsystems: nilfs
[Documentation on labels]
First crash: 757d, last: 744d

Sample crash report:
INFO: task syz-executor.5:31620 blocked for more than 143 seconds.
      Not tainted 6.2.0-rc3-syzkaller-00376-g7c6984405241 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5  state:D stack:19624 pid:31620 ppid:23827  flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5293 [inline]
 __schedule+0x995/0xe20 kernel/sched/core.c:6606
 schedule+0xcb/0x190 kernel/sched/core.c:6682
 rwsem_down_write_slowpath+0xfc1/0x1480 kernel/locking/rwsem.c:1190
 __down_write_common kernel/locking/rwsem.c:1305 [inline]
 __down_write kernel/locking/rwsem.c:1314 [inline]
 down_write+0x231/0x270 kernel/locking/rwsem.c:1563
 nilfs_sufile_set_alloc_range+0x53/0x190 fs/nilfs2/sufile.c:272
 nilfs_resize_fs+0xad8/0xc80 fs/nilfs2/super.c:459
 nilfs_ioctl_resize fs/nilfs2/ioctl.c:1033 [inline]
 nilfs_ioctl+0x1130/0x20f0 fs/nilfs2/ioctl.c:1301
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:870 [inline]
 __se_sys_ioctl+0xfb/0x170 fs/ioctl.c:856
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f295448c0c9
RSP: 002b:00007f295518a168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f29545abf80 RCX: 00007f295448c0c9
RDX: 0000000020000140 RSI: 0000000040086e8b RDI: 0000000000000004
RBP: 00007f29544e7ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd2c4eeacf R14: 00007f295518a300 R15: 0000000000022000
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
 #0: ffffffff8d326fd0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x30/0xd00 kernel/rcu/tasks.h:507
1 lock held by rcu_tasks_trace/13:
 #0: ffffffff8d3277d0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x30/0xd00 kernel/rcu/tasks.h:507
1 lock held by khungtaskd/28:
 #0: ffffffff8d326e00 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/4742:
 #0: ffff88814a313098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
 #1: ffffc900015b02f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x53b/0x1650 drivers/tty/n_tty.c:2177
2 locks held by syz-fuzzer/5060:
2 locks held by syz-executor.5/31620:
 #0: ffff88801ede2460 (sb_writers#25){.+.+}-{0:0}, at: mnt_want_write_file+0x5a/0x1f0 fs/namespace.c:552
 #1: ffff88802a118a70 (&mi->mi_sem){++++}-{3:3}, at: nilfs_sufile_set_alloc_range+0x53/0x190 fs/nilfs2/sufile.c:272
3 locks held by syz-executor.5/31626:
2 locks held by syz-executor.1/32265:
 #0: ffff88807b09e460 (sb_writers#25){.+.+}-{0:0}, at: mnt_want_write_file+0x5a/0x1f0 fs/namespace.c:552
 #1: ffff88808cb63870 (&mi->mi_sem){++++}-{3:3}, at: nilfs_sufile_set_alloc_range+0x53/0x190 fs/nilfs2/sufile.c:272
3 locks held by syz-executor.1/32267:

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

NMI backtrace for cpu 1
CPU: 1 PID: 28 Comm: khungtaskd Not tainted 6.2.0-rc3-syzkaller-00376-g7c6984405241 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1b1/0x290 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x46f/0x4f0 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x1ba/0x420 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
 watchdog+0xcd5/0xd20 kernel/hung_task.c:377
 kthread+0x266/0x300 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 5255 Comm: syz-fuzzer Not tainted 6.2.0-rc3-syzkaller-00376-g7c6984405241 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0033:0x413c22
Code: 00 48 01 c2 48 c1 ea 1a 48 81 fa 00 00 40 00 72 04 31 d2 eb 2e 48 8b 35 24 0d b6 01 84 06 48 8b 14 d6 48 85 d2 74 1a 48 89 c6 <48> c1 e8 0d 48 25 ff 1f 00 00 48 8b 94 c2 00 00 20 00 48 89 f0 eb
RSP: 002b:000000c002c1be48 EFLAGS: 00000206
RAX: 000000c000079170 RBX: 000000c00003c640 RCX: 0000000000000008
RDX: 00007f78b9d22000 RSI: 000000c000079170 RDI: 0000000000c0d748
RBP: 000000c002c1be70 R08: 0000000000000001 R09: 00007f78b9d23e32
R10: 000000000003cb30 R11: 00007f78b9f21fff R12: 000000c00003c640
R13: 000000c000079170 R14: 000000c0008c9040 R15: 00007f78b8160a9c
FS:  000000c014a53890 GS:  0000000000000000

Crashes (7):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/01/15 19:01 upstream 7c6984405241 a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_sufile_set_alloc_range
2023/01/05 15:46 upstream 41c03ba9beea 1dac8c7a .config console log report info ci-upstream-kasan-gce-selinux-root INFO: task hung in nilfs_sufile_set_alloc_range
2023/01/05 01:43 upstream 512dee0c00ad 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in nilfs_sufile_set_alloc_range
2023/01/04 18:18 upstream 69b41ac87e4a 1dac8c7a .config console log report info ci-upstream-kasan-gce-selinux-root INFO: task hung in nilfs_sufile_set_alloc_range
2023/01/04 16:51 upstream 69b41ac87e4a 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_sufile_set_alloc_range
2023/01/04 11:20 upstream 69b41ac87e4a 1dac8c7a .config console log report info ci-upstream-kasan-gce-selinux-root INFO: task hung in nilfs_sufile_set_alloc_range
2023/01/02 12:27 upstream 88603b6dc419 ab32d508 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_sufile_set_alloc_range
* Struck through repros no longer work on HEAD.