syzbot


INFO: task hung in jfs_commit_inode (2)

Status: upstream: reported C repro on 2023/08/29 19:55
Subsystems: jfs
[Documentation on labels]
Reported-by: syzbot+9157524e62303fd7b21c@syzkaller.appspotmail.com
First crash: 231d, last: 8d07h
Cause bisection: the issue happens on the oldest tested release (bisect log)
Crash: INFO: task hung in jfs_commit_inode (log)
Repro: C syz .config
  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [jfs?] INFO: task hung in jfs_commit_inode (2) 0 (1) 2023/08/29 19:55
Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 INFO: task hung in jfs_commit_inode (2) 1 78d 78d 0/3 upstream: reported on 2023/12/16 06:52
linux-6.1 INFO: task hung in jfs_commit_inode 1 230d 230d 0/3 auto-obsoleted due to no activity on 2023/10/25 03:25
upstream INFO: task hung in jfs_commit_inode jfs 3 472d 503d 0/26 auto-obsoleted due to no activity on 2023/02/27 21:28
Last patch testing requests (7)
Created Duration User Patch Repo Result
2024/02/21 19:23 20m retest repro upstream OK log
2024/02/07 17:39 20m retest repro linux-next report log
2024/01/06 15:03 19m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci report log
2023/12/19 09:21 17m retest repro upstream report log
2023/12/05 06:17 15m retest repro upstream report log
2023/10/23 05:06 26m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci report log
2023/09/10 19:12 12m retest repro upstream report log

Sample crash report:
INFO: task kworker/u4:8:1265 blocked for more than 143 seconds.
      Not tainted 6.7.0-rc2-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:8    state:D stack:23696 pid:1265  tgid:1265  ppid:2      flags:0x00004000
Workqueue: writeback wb_workfn (flush-7:0)
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
 jfs_commit_inode+0x22f/0x570 fs/jfs/inode.c:102
 jfs_write_inode+0xfc/0x240 fs/jfs/inode.c:132
 write_inode fs/fs-writeback.c:1473 [inline]
 __writeback_single_inode+0xa91/0xe90 fs/fs-writeback.c:1690
 writeback_sb_inodes+0x599/0x1080 fs/fs-writeback.c:1916
 __writeback_inodes_wb+0xff/0x2d0 fs/fs-writeback.c:1987
 wb_writeback+0x7f8/0xaa0 fs/fs-writeback.c:2094
 wb_check_background_flush fs/fs-writeback.c:2164 [inline]
 wb_do_writeback fs/fs-writeback.c:2252 [inline]
 wb_workfn+0x87c/0xfe0 fs/fs-writeback.c:2279
 process_one_work+0x886/0x15d0 kernel/workqueue.c:2630
 process_scheduled_works kernel/workqueue.c:2703 [inline]
 worker_thread+0x8b9/0x1290 kernel/workqueue.c:2784
 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>

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
4 locks held by kworker/u4:8/1265:
 #0: ffff888140054d38 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x789/0x15d0 kernel/workqueue.c:2605
 #1: ffffc90004c6fd80 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7eb/0x15d0 kernel/workqueue.c:2606
 #2: ffff8880193140e0 (&type->s_umount_key#45){++++}-{3:3}, at: super_trylock_shared+0x1e/0xf0 fs/super.c:610
 #3: ffff8880762c3008 (&jfs_ip->commit_mutex){+.+.}-{3:3}, at: jfs_commit_inode+0x22f/0x570 fs/jfs/inode.c:102
2 locks held by getty/4823:
 #0: ffff88814ba2c0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x24/0x80 drivers/tty/tty_ldisc.c:243
 #1: ffffc90002efe2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0xfc6/0x1490 drivers/tty/n_tty.c:2201
4 locks held by syz-executor388/5071:

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

NMI backtrace for cpu 0
CPU: 0 PID: 29 Comm: khungtaskd Not tainted 6.7.0-rc2-syzkaller #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 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 5071 Comm: syz-executor388 Not tainted 6.7.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
RIP: 0010:dtSplitRoot+0x9b1/0x1760 fs/jfs/jfs_dtree.c:1972
Code: 8d fe 4d 63 e4 49 81 fc 80 00 00 00 0f 87 e2 09 00 00 4c 89 e7 48 c1 e7 05 48 01 df 48 89 f8 48 c1 e8 03 42 0f b6 04 38 84 c0 <74> 06 0f 8e ab 09 00 00 49 c1 e4 05 bf ff ff ff ff 4e 8d 2c 23 45
RSP: 0018:ffffc9000436f5a0 EFLAGS: 00000246
RAX: 0000000000000000 RBX: ffff88807f9ed000 RCX: ffffffff82fa5e83
RDX: ffff88801aad3b80 RSI: ffffffff82fa5e39 RDI: ffff88807f9ed0c0
RBP: ffff8880762c3270 R08: 0000000000000005 R09: 00000000ffffffff
R10: 0000000000000006 R11: 0000000000000000 R12: 0000000000000006
R13: ffff88807f9ed0c0 R14: 0000000000000080 R15: dffffc0000000000
FS:  00005555574d1380(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000557711dcabc0 CR3: 0000000074c49000 CR4: 0000000000350ef0
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 dtSplitUp+0x1298/0x5850 fs/jfs/jfs_dtree.c:985
 dtInsert+0x872/0xb00 fs/jfs/jfs_dtree.c:863
 jfs_mkdir+0x665/0xb30 fs/jfs/namei.c:270
 vfs_mkdir+0x577/0x820 fs/namei.c:4106
 do_mkdirat+0x2fd/0x3a0 fs/namei.c:4129
 __do_sys_mkdir fs/namei.c:4149 [inline]
 __se_sys_mkdir fs/namei.c:4147 [inline]
 __x64_sys_mkdir+0xf2/0x140 fs/namei.c:4147
 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:0x7f072be99a97
Code: ff ff 77 07 31 c0 c3 0f 1f 40 00 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff c3 66 0f 1f 44 00 00 b8 53 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffed5af27a8 EFLAGS: 00000286 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00000000ffffffff RCX: 00007f072be99a97
RDX: 0000000000000000 RSI: 00000000000001ff RDI: 0000000020000500
RBP: 00007ffed5af2840 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000286 R12: 0000000020000500
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
 </TASK>

Crashes (11):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/11/21 05:47 upstream 98b1cc82c4af cb976f63 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in jfs_commit_inode
2024/01/24 16:56 linux-next 8bf1262c53f5 1e153dc8 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root INFO: task hung in jfs_commit_inode
2023/10/09 04:18 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 19af4a4ed414 5e837c76 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 INFO: task hung in jfs_commit_inode
2023/08/25 19:43 upstream 4f9e7fabf864 03d9c195 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2023/12/23 13:23 upstream 5254c0cbc92d fb427a07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2023/11/09 12:36 upstream 6bc986ab839c 4862372a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2023/10/08 16:06 upstream b9ddbb0cde2a 5e837c76 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2023/08/25 18:07 upstream 4f9e7fabf864 03d9c195 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2023/07/16 08:42 upstream 831fe284d827 35d9ecc5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/02/24 03:17 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 9abbc24128bc 8d446f15 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in jfs_commit_inode
2023/08/27 17:15 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci fe4469582053 03d9c195 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in jfs_commit_inode
* Struck through repros no longer work on HEAD.