syzbot


INFO: task hung in jfs_commit_inode (3)

Status: upstream: reported on 2024/04/21 18:11
Reported-by: syzbot+104fe61acb54333c79ff@syzkaller.appspotmail.com
First crash: 17d, last: 2d11h
Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 INFO: task hung in jfs_commit_inode (2) 1 144d 144d 0/3 auto-obsoleted due to no activity on 2024/03/25 06:52
linux-6.1 INFO: task hung in jfs_commit_inode 1 297d 297d 0/3 auto-obsoleted due to no activity on 2023/10/25 03:25
upstream INFO: task hung in jfs_commit_inode (2) jfs C inconclusive done 127 6h43m 253d 0/26 upstream: reported C repro on 2023/08/29 19:55
upstream INFO: task hung in jfs_commit_inode jfs 3 539d 570d 0/26 auto-obsoleted due to no activity on 2023/02/27 21:28
linux-5.15 INFO: task hung in jfs_commit_inode origin:upstream C error 3 11d 53d 0/3 upstream: reported C repro on 2024/03/16 23:34

Sample crash report:
INFO: task kworker/u4:7:3725 blocked for more than 143 seconds.
      Not tainted 6.1.90-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:7    state:D stack:23384 pid:3725  ppid:2      flags:0x00004000
Workqueue: writeback wb_workfn (flush-7:2)
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5245 [inline]
 __schedule+0x142d/0x4550 kernel/sched/core.c:6558
 schedule+0xbf/0x180 kernel/sched/core.c:6634
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6693
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0x6b9/0xd80 kernel/locking/mutex.c:747
 jfs_commit_inode+0x242/0x580 fs/jfs/inode.c:102
 jfs_write_inode+0x13f/0x210 fs/jfs/inode.c:132
 write_inode fs/fs-writeback.c:1460 [inline]
 __writeback_single_inode+0x67d/0x11e0 fs/fs-writeback.c:1677
 writeback_sb_inodes+0xc2b/0x1b20 fs/fs-writeback.c:1903
 __writeback_inodes_wb+0x114/0x400 fs/fs-writeback.c:1974
 wb_writeback+0x4b1/0xe10 fs/fs-writeback.c:2079
 wb_check_old_data_flush fs/fs-writeback.c:2179 [inline]
 wb_do_writeback fs/fs-writeback.c:2232 [inline]
 wb_workfn+0xbec/0x1020 fs/fs-writeback.c:2260
 process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292
 worker_thread+0xa47/0x1200 kernel/workqueue.c:2439
 kthread+0x28d/0x320 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
 #0: ffffffff8d12ae50 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:516
1 lock held by rcu_tasks_trace/13:
 #0: ffffffff8d12b650 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:516
1 lock held by khungtaskd/28:
 #0: ffffffff8d12ac80 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
 #0: ffffffff8d12ac80 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
 #0: ffffffff8d12ac80 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6494
4 locks held by kworker/u4:3/51:
 #0: ffff8880162fe938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
 #1: ffffc90000bc7d20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
 #2: ffff88805cbaa0e0 (&type->s_umount_key#65){++++}-{3:3}, at: trylock_super+0x1b/0xf0 fs/super.c:415
 #3: ffff888052ab26c8 (&jfs_ip->commit_mutex){+.+.}-{3:3}, at: jfs_commit_inode+0x242/0x580 fs/jfs/inode.c:102
2 locks held by getty/3302:
 #0: ffff88802961b098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
 #1: ffffc900031262f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6a7/0x1db0 drivers/tty/n_tty.c:2188
3 locks held by kworker/1:3/3604:
 #0: ffff888012470938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
 #1: ffffc9000554fd20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
 #2: ffffffff8d130278 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:291 [inline]
 #2: ffffffff8d130278 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x4f0/0x930 kernel/rcu/tree_exp.h:962
4 locks held by kworker/u4:7/3725:
 #0: ffff8880162fe938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
 #1: ffffc90005a9fd20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
 #2: ffff88807565a0e0 (&type->s_umount_key#65){++++}-{3:3}, at: trylock_super+0x1b/0xf0 fs/super.c:415
 #3: ffff888058809448 (&jfs_ip->commit_mutex){+.+.}-{3:3}, at: jfs_commit_inode+0x242/0x580 fs/jfs/inode.c:102
2 locks held by kworker/1:12/3738:
 #0: ffff888012472138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
 #1: ffffc90005b1fd20 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
3 locks held by kworker/u4:8/3939:
4 locks held by kworker/u4:19/4437:
 #0: ffff8880162fe938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
 #1: ffffc90013d07d20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
 #2: ffff88807f08e0e0 (&type->s_umount_key#65){++++}-{3:3}, at: trylock_super+0x1b/0xf0 fs/super.c:415
 #3: ffff888058809d88 (&jfs_ip->commit_mutex){+.+.}-{3:3}, at: jfs_commit_inode+0x242/0x580 fs/jfs/inode.c:102
4 locks held by syz-executor.2/6734:
4 locks held by syz-executor.0/7092:
4 locks held by syz-executor.4/7800:
2 locks held by syz-executor.1/8371:
 #0: ffff8880243820e0 (&type->s_umount_key#69){++++}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:362
 #1: ffffffff8d130278 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
 #1: ffffffff8d130278 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x360/0x930 kernel/rcu/tree_exp.h:962
2 locks held by syz-executor.4/8733:
 #0: ffff88802a06a0e0 (&type->s_umount_key#92){+.+.}-{3:3}, at: grab_super+0x59/0x1a0 fs/super.c:386
 #1: ffffffff8d1534a8 (cgroup_mutex){+.+.}-{3:3}, at: cgroup_lock include/linux/cgroup.h:442 [inline]
 #1: ffffffff8d1534a8 (cgroup_mutex){+.+.}-{3:3}, at: cgroup_do_get_tree+0x199/0x380 kernel/cgroup/cgroup.c:2179
3 locks held by kvm-nx-lpage-re/8758:
 #0: ffffffff8d1534a8 (cgroup_mutex){+.+.}-{3:3}, at: cgroup_lock include/linux/cgroup.h:442 [inline]
 #0: ffffffff8d1534a8 (cgroup_mutex){+.+.}-{3:3}, at: cgroup_attach_task_all+0x23/0xe0 kernel/cgroup/cgroup-v1.c:61
 #1: ffffffff8cfc8070 (cpu_hotplug_lock){++++}-{0:0}, at: cgroup_attach_lock+0xd/0x30 kernel/cgroup/cgroup.c:2444
 #2: ffffffff8d153690 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: cgroup_attach_task_all+0x2d/0xe0 kernel/cgroup/cgroup-v1.c:62
1 lock held by syz-executor.0/8759:
 #0: ffffffff8d1716e8 (tracepoints_mutex){+.+.}-{3:3}, at: tracepoint_probe_unregister+0x2e/0x980 kernel/tracepoint.c:548
1 lock held by syz-executor.0/8760:
1 lock held by syz-executor.2/8769:
 #0: ffffffff8d1716e8 (tracepoints_mutex){+.+.}-{3:3}, at: tracepoint_probe_register_prio_may_exist+0xb7/0x190 kernel/tracepoint.c:478

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

NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 6.1.90-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 nmi_cpu_backtrace+0x4e1/0x560 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x1b0/0x3f0 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+0xf88/0xfd0 kernel/hung_task.c:377
 kthread+0x28d/0x320 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 6734 Comm: syz-executor.2 Not tainted 6.1.90-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:__sanitizer_cov_trace_pc+0x41/0x60 kernel/kcov.c:212
Code: ff 00 74 11 f7 c2 00 01 00 00 74 35 83 b9 1c 16 00 00 00 74 2c 8b 91 f8 15 00 00 83 fa 02 75 21 48 8b 91 00 16 00 00 48 8b 32 <48> 8d 7e 01 8b 89 fc 15 00 00 48 39 cf 73 08 48 89 3a 48 89 44 f2
RSP: 0018:ffffc9000cf47018 EFLAGS: 00000246
RAX: ffffffff83075d1a RBX: ffff888021306000 RCX: ffff88805970bb80
RDX: ffffc90003dd2000 RSI: 000000000003ffff RDI: 0000000000040000
RBP: ffffc9000cf47210 R08: ffffffff83075cec R09: ffffed1004260c24
R10: 0000000000000004 R11: dffffc0000000001 R12: 1ffff11004260c00
R13: dffffc0000000000 R14: ffff8880588096b0 R15: 0000000000000000
FS:  00007f67463ef6c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd37bdb4d58 CR3: 0000000061ac3000 CR4: 00000000003526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 dtSplitRoot+0x8da/0x1920 fs/jfs/jfs_dtree.c:1978
 dtSplitUp fs/jfs/jfs_dtree.c:990 [inline]
 dtInsert+0x12f6/0x6b00 fs/jfs/jfs_dtree.c:868
 jfs_create+0x7b2/0xbb0 fs/jfs/namei.c:137
 lookup_open fs/namei.c:3484 [inline]
 open_last_lookups fs/namei.c:3552 [inline]
 path_openat+0x12f1/0x2e60 fs/namei.c:3782
 do_filp_open+0x230/0x480 fs/namei.c:3812
 do_sys_openat2+0x13b/0x500 fs/open.c:1318
 do_sys_open fs/open.c:1334 [inline]
 __do_sys_openat fs/open.c:1350 [inline]
 __se_sys_openat fs/open.c:1345 [inline]
 __x64_sys_openat+0x243/0x290 fs/open.c:1345
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f674567dca9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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:00007f67463ef0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f67457abf80 RCX: 00007f674567dca9
RDX: 000000000000275a RSI: 0000000020000140 RDI: ffffffffffffff9c
RBP: 00007f67456c947e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f67457abf80 R15: 00007ffdabc2ada8
 </TASK>

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/05/06 07:24 linux-6.1.y 909ba1f1b414 610f2a54 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in jfs_commit_inode
2024/04/23 23:19 linux-6.1.y 6741e066ec76 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in jfs_commit_inode
2024/04/21 18:10 linux-6.1.y 6741e066ec76 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in jfs_commit_inode
2024/05/06 17:15 linux-6.1.y 909ba1f1b414 d884b519 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in jfs_commit_inode
* Struck through repros no longer work on HEAD.