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: 493d, last: 8h42m
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
  
Fix bisection: fixed by (bisect log) :
commit 6f861765464f43a71462d52026fbddfc858239a5
Author: Jan Kara <jack@suse.cz>
Date: Wed Nov 1 17:43:10 2023 +0000

  fs: Block writes to mounted block devices

  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [jfs?] INFO: task hung in jfs_commit_inode (2) 1 (3) 2024/04/18 08:40
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 340d 340d 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 493d 493d 0/3 auto-obsoleted due to no activity on 2023/10/25 03:25
upstream INFO: task hung in jfs_commit_inode jfs 3 735d 766d 0/28 auto-obsoleted due to no activity on 2023/02/27 21:28
linux-6.1 INFO: task hung in jfs_commit_inode (3) 62 29d 213d 0/3 upstream: reported on 2024/04/21 18:11
linux-5.15 INFO: task hung in jfs_commit_inode origin:upstream C error 49 11d 249d 0/3 upstream: reported C repro on 2024/03/16 23:34
Last patch testing requests (10)
Created Duration User Patch Repo Result
2024/04/18 17:50 8h52m retest repro linux-next report log
2024/04/07 16:57 4h53m retest repro upstream error
2024/04/07 16:57 7h51m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci OK log
2024/03/09 09:43 3h34m retest repro upstream OK log
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

Sample crash report:
INFO: task kworker/u8:6:1134 blocked for more than 143 seconds.
      Not tainted 6.12.0-syzkaller-00171-g23acd177540d #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u8:6    state:D stack:22768 pid:1134  tgid:1134  ppid:2      flags:0x00004000
Workqueue: writeback wb_workfn (flush-7:0)
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5328 [inline]
 __schedule+0x17fa/0x4bd0 kernel/sched/core.c:6693
 __schedule_loop kernel/sched/core.c:6770 [inline]
 schedule+0x14b/0x320 kernel/sched/core.c:6785
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6842
 __mutex_lock_common kernel/locking/mutex.c:684 [inline]
 __mutex_lock+0x6a7/0xd70 kernel/locking/mutex.c:752
 jfs_commit_inode+0x24a/0x590 fs/jfs/inode.c:102
 jfs_write_inode+0x143/0x220 fs/jfs/inode.c:132
 write_inode fs/fs-writeback.c:1525 [inline]
 __writeback_single_inode+0x711/0x10d0 fs/fs-writeback.c:1745
 writeback_sb_inodes+0x80c/0x1370 fs/fs-writeback.c:1976
 __writeback_inodes_wb+0x11b/0x260 fs/fs-writeback.c:2047
 wb_writeback+0x42f/0xbd0 fs/fs-writeback.c:2158
 wb_check_background_flush fs/fs-writeback.c:2228 [inline]
 wb_do_writeback fs/fs-writeback.c:2316 [inline]
 wb_workfn+0xc58/0x1090 fs/fs-writeback.c:2343
 process_one_work kernel/workqueue.c:3229 [inline]
 process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310
 worker_thread+0x870/0xd30 kernel/workqueue.c:3391
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/30:
 #0: ffffffff8e939f20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:337 [inline]
 #0: ffffffff8e939f20 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline]
 #0: ffffffff8e939f20 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x2a0 kernel/locking/lockdep.c:6720
4 locks held by kworker/u8:6/1134:
 #0: ffff8880202bb148 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3204 [inline]
 #0: ffff8880202bb148 ((wq_completion)writeback){+.+.}-{0:0}, at: process_scheduled_works+0x93b/0x1850 kernel/workqueue.c:3310
 #1: ffffc90004267d00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3205 [inline]
 #1: ffffc90004267d00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x976/0x1850 kernel/workqueue.c:3310
 #2: ffff888035f9e0e0 (&type->s_umount_key#44){.+.+}-{3:3}, at: super_trylock_shared+0x22/0xf0 fs/super.c:562
 #3: ffff88807b3e1d70 (&jfs_ip->commit_mutex){+.+.}-{3:3}, at: jfs_commit_inode+0x24a/0x590 fs/jfs/inode.c:102
2 locks held by getty/5588:
 #0: ffff8880317cd0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc90002f062f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6a6/0x1e00 drivers/tty/n_tty.c:2211
4 locks held by syz-executor356/5839:

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 30 Comm: khungtaskd Not tainted 6.12.0-syzkaller-00171-g23acd177540d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x49c/0x4d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x198/0x320 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:162 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:223 [inline]
 watchdog+0xff4/0x1040 kernel/hung_task.c:379
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 5839 Comm: syz-executor356 Not tainted 6.12.0-syzkaller-00171-g23acd177540d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
RIP: 0010:dtSplitRoot+0x8c0/0x1930 fs/jfs/jfs_dtree.c:1979
Code: 0f 85 09 0f 00 00 44 88 3b 49 0f be df 0f b6 f3 bf ff 00 00 00 e8 90 2e 69 fe 84 db 78 44 e8 87 2b 69 fe 48 c1 e3 05 4c 01 e3 <49> 89 dc 49 c1 ec 03 43 0f b6 04 2c 84 c0 75 15 44 0f b6 3b 45 84
RSP: 0018:ffffc90003c774a0 EFLAGS: 00000286
RAX: ffffffff832bc489 RBX: ffff888079522000 RCX: ffff88807e90bc00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00000000000000ff
RBP: ffffc90003c77690 R08: ffffffff832bc480 R09: 0000000000000000
R10: 00300065006c0069 R11: 006605ff00000020 R12: ffff888079522000
R13: dffffc0000000000 R14: ffff88807b3e1fd8 R15: 0000000000000000
FS:  0000555588e4f380(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055b361612600 CR3: 0000000079548000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 dtSplitUp fs/jfs/jfs_dtree.c:992 [inline]
 dtInsert+0x12cd/0x6c10 fs/jfs/jfs_dtree.c:870
 jfs_create+0x7ba/0xbb0 fs/jfs/namei.c:137
 vfs_create+0x23c/0x3d0 fs/namei.c:3335
 do_mknodat+0x447/0x5b0 fs/namei.c:4226
 __do_sys_mknod fs/namei.c:4259 [inline]
 __se_sys_mknod fs/namei.c:4257 [inline]
 __x64_sys_mknod+0x8c/0xa0 fs/namei.c:4257
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f2254d1ea59
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 17 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe32ae47f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000085
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f2254d1ea59
RDX: 0000000000000701 RSI: 0000000000000000 RDI: 0000000020000000
RBP: 00007f2254d985f0 R08: 0000000000006152 R09: 0000555588e504c0
R10: 00007ffe32ae46c0 R11: 0000000000000246 R12: 00007ffe32ae4820
R13: 00007ffe32ae4a48 R14: 431bde82d7b634db R15: 00007f2254d6703b
 </TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.285 msecs

Crashes (792):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/11/19 10:45 upstream 23acd177540d 571351cb .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/18 18:37 upstream adc218676eef e7bb5d6e .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/17 23:44 upstream 4a5df3796467 cfe3a04a .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/17 13:39 upstream 4a5df3796467 cfe3a04a .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/05 20:54 upstream 2e1b3cc9d7f7 da38b4c9 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/10/30 10:26 upstream c1e939a21eb1 66aeb999 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/10/07 06:41 upstream 8cf0b93919e1 d7906eff .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/09/05 12:50 upstream c763c4339688 464ac2ed .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/06/17 15:13 upstream 2ccbdf43d5e7 f429ab00 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-smack-root INFO: task hung in jfs_commit_inode
2024/03/15 10:46 upstream fe46a7dd189e d615901c .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-smack-root INFO: task hung in jfs_commit_inode
2024/10/07 04:00 upstream 2a130b7e1fcd d7906eff .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-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/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
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/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
2024/11/20 21:42 upstream 8f7c8b88bda4 4fca1650 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/20 03:00 upstream 158f238aa69d 7d02db5a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/19 03:57 upstream 23acd177540d 571351cb .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/19 02:02 upstream 23acd177540d 571351cb .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/18 18:12 upstream adc218676eef e7bb5d6e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/17 16:32 upstream 4a5df3796467 cfe3a04a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/17 14:41 upstream 4a5df3796467 cfe3a04a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/17 03:27 upstream b5a24181e461 cfe3a04a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/17 02:06 upstream b5a24181e461 cfe3a04a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/16 15:02 upstream e8bdb3c8be08 cfe3a04a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/16 07:56 upstream f868cd251776 cfe3a04a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/15 23:50 upstream f868cd251776 cfe3a04a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/15 12:01 upstream cfaaa7d010d1 f6ede3a3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/15 02:47 upstream cfaaa7d010d1 a8c99394 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/14 23:49 upstream cfaaa7d010d1 a8c99394 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/14 05:57 upstream 0a9b9d17f3a7 bb3f8425 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/13 19:53 upstream f1b785f4c787 bb3f8425 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/13 15:41 upstream f1b785f4c787 bb3f8425 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/12 11:40 upstream 2d5404caa8c7 75bb1b32 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/12 09:07 upstream 2d5404caa8c7 75bb1b32 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/11 06:58 upstream a9cda7c0ffed 6b856513 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jfs_commit_inode
2024/11/10 19:52 upstream a9cda7c0ffed 6b856513 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/10 13:42 upstream de2f378f2b77 6b856513 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/10 09:37 upstream de2f378f2b77 6b856513 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/10 08:18 upstream de2f378f2b77 6b856513 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/10 00:04 upstream da4373fbcf00 6b856513 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jfs_commit_inode
2024/11/09 20:19 upstream da4373fbcf00 6b856513 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/09 15:04 upstream da4373fbcf00 6b856513 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/08 14:30 upstream 906bd684e4b1 179b040e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/08 13:23 upstream 906bd684e4b1 179b040e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/07 08:34 upstream 7758b206117d df3dc63b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jfs_commit_inode
2024/11/07 05:44 upstream 7758b206117d df3dc63b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/06 18:31 upstream 2e1b3cc9d7f7 df3dc63b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/06 12:13 upstream 2e1b3cc9d7f7 3a465482 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/06 11:08 upstream 2e1b3cc9d7f7 3a465482 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/06 04:18 upstream 2e1b3cc9d7f7 3a465482 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/04 12:05 upstream 59b723cd2adb f00eed24 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/03 04:46 upstream 3e5e6c9900c3 f00eed24 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/02 18:40 upstream 11066801dd4b f00eed24 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/01 22:20 upstream 6c52d4da1c74 f00eed24 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/11/01 08:08 upstream 6c52d4da1c74 96eb609f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/10/31 19:02 upstream 0fc810ae3ae1 96eb609f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/10/30 22:16 upstream 4236f913808c fb888278 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_commit_inode
2024/06/24 07:29 upstream 7c16f0a4ed1c edc5149a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in jfs_commit_inode
2024/06/23 09:54 upstream 5f583a3162ff edc5149a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root 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/10/13 15:12 linux-next d61a00525464 084d8178 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in jfs_commit_inode
2024/11/08 21:06 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci eb17c12d043d 179b040e .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.