syzbot


INFO: task hung in jfs_commit_inode

Status: upstream: reported C repro on 2024/03/16 23:34
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+30b3e48dc48dd2ad45b6@syzkaller.appspotmail.com
First crash: 824d, last: 11d
Fix commit to backport (bisect log) :
tree: upstream
commit ce6dede912f064a855acf6f04a04cbb2c25b8c8c
Author: Edward Adam Davis <eadavis@qq.com>
Date: Thu Apr 11 12:05:28 2024 +0000

  jfs: fix null ptr deref in dtInsertEntry

[report pending]
  
Fix bisection: failed (error log, bisect log)
  
Discussions (2)
Title Replies (including bot) Last reply
Test: [v5.15] INFO: task hung in jfs_commit_inode 1 (2) 2025/07/03 05:38
[PATCH 5.15.y] jfs: fix null ptr deref in dtInsertEntry 1 (1) 2025/07/02 18:59
Bug presence (1)
Date Name Commit Repro Result
2025/09/24 upstream (ToT) cec1e6e5d1ab C [report] INFO: task hung in jfs_commit_inode
Similar bugs (6)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 INFO: task hung in jfs_commit_inode (2) 1 1 916d 916d 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 1 1068d 1068d 0/3 auto-obsoleted due to no activity on 2023/10/25 03:25
upstream INFO: task hung in jfs_commit_inode (2) jfs prio:high 1 C inconclusive done 2397 1d12h 1024d 0/29 upstream: reported C repro on 2023/08/29 19:55
upstream INFO: task hung in jfs_commit_inode jfs 1 3 1311d 1341d 0/29 auto-obsoleted due to no activity on 2023/02/27 21:28
linux-6.6 INFO: task hung in jfs_commit_inode origin:upstream missing-backport 1 C error 26 12d 283d 0/2 upstream: reported C repro on 2025/09/09 14:26
linux-6.1 INFO: task hung in jfs_commit_inode (3) origin:upstream 1 C error 75 11d 789d 0/3 upstream: reported C repro on 2024/04/21 18:11
Last patch testing requests (12)
Created Duration User Patch Repo Result
2026/05/26 02:45 21m retest repro linux-5.15.y report log
2026/05/08 18:48 13m retest repro linux-5.15.y error
2026/04/15 15:40 12m retest repro linux-5.15.y report log
2026/04/01 00:31 45m retest repro linux-5.15.y report log
2026/03/17 13:08 12m retest repro linux-5.15.y report log
2026/03/03 10:59 12m retest repro linux-5.15.y report log
2026/02/12 23:43 16m retest repro linux-5.15.y report log
2026/01/29 19:33 13m retest repro linux-5.15.y report log
2026/01/06 10:53 13m retest repro linux-5.15.y report log
2026/01/06 10:53 13m retest repro linux-5.15.y report log
2025/07/02 18:24 1h54m duttaditya18@gmail.com patch git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git linux-5.15.y OK log
2025/05/11 12:47 14m kevinpaul468@gmail.com patch linux-5.15.y report log
Fix bisection attempts (2)
Created Duration User Patch Repo Result
2025/02/12 11:26 6h25m fix candidate upstream OK (1) job log
2024/04/19 12:58 0m bisect fix linux-5.15.y error job log

Sample crash report:
INFO: task kworker/u4:2:154 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:2    state:D stack:24920 pid:  154 ppid:     2 flags:0x00004000
Workqueue: writeback wb_workfn (flush-7:0)
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5049 [inline]
 __schedule+0x11ef/0x43c0 kernel/sched/core.c:6395
 schedule+0x11b/0x1e0 kernel/sched/core.c:6478
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6537
 __mutex_lock_common+0xcfc/0x2400 kernel/locking/mutex.c:669
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
 jfs_commit_inode+0x1c7/0x520 fs/jfs/inode.c:108
 jfs_write_inode+0x141/0x220 fs/jfs/inode.c:138
 write_inode fs/fs-writeback.c:1505 [inline]
 __writeback_single_inode+0x6c3/0xda0 fs/fs-writeback.c:1715
 writeback_sb_inodes+0xa4e/0x1680 fs/fs-writeback.c:1940
 __writeback_inodes_wb+0x12a/0x3f0 fs/fs-writeback.c:2011
 wb_writeback+0x46f/0xbe0 fs/fs-writeback.c:2116
 wb_check_background_flush fs/fs-writeback.c:2182 [inline]
 wb_do_writeback fs/fs-writeback.c:2270 [inline]
 wb_workfn+0xbd6/0xf20 fs/fs-writeback.c:2298
 process_one_work+0x85f/0x1010 kernel/workqueue.c:2310
 worker_thread+0xaa6/0x1290 kernel/workqueue.c:2457
 kthread+0x436/0x520 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>

Showing all locks held in the system:
4 locks held by kworker/u4:0/9:
 #0: ffff888019f8a138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x761/0x1010 kernel/workqueue.c:-1
 #1: ffffc90000ce7d00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x79f/0x1010 kernel/workqueue.c:2285
 #2: ffff888079b420e0 (&type->s_umount_key#54){.+.+}-{3:3}, at: trylock_super+0x1c/0xf0 fs/super.c:418
 #3: ffff88804e07cbc8 (&jfs_ip->commit_mutex){+.+.}-{3:3}, at: jfs_commit_inode+0x1c7/0x520 fs/jfs/inode.c:108
1 lock held by khungtaskd/27:
 #0: ffffffff8c31f320 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
4 locks held by kworker/u4:1/144:
 #0: ffff888019f8a138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x761/0x1010 kernel/workqueue.c:-1
 #1: ffffc9000168fd00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x79f/0x1010 kernel/workqueue.c:2285
 #2: ffff8880249e60e0 (&type->s_umount_key#54){.+.+}-{3:3}, at: trylock_super+0x1c/0xf0 fs/super.c:418
 #3: ffff8880603ab008 (&jfs_ip->commit_mutex){+.+.}-{3:3}, at: jfs_commit_inode+0x1c7/0x520 fs/jfs/inode.c:108
4 locks held by kworker/u4:2/154:
 #0: ffff888019f8a138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x761/0x1010 kernel/workqueue.c:-1
 #1: ffffc90001fa7d00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x79f/0x1010 kernel/workqueue.c:2285
 #2: ffff8880254f00e0 (&type->s_umount_key#54){.+.+}-{3:3}, at: trylock_super+0x1c/0xf0 fs/super.c:418
 #3: ffff8880602e3008 (&jfs_ip->commit_mutex){+.+.}-{3:3}, at: jfs_commit_inode+0x1c7/0x520 fs/jfs/inode.c:108
4 locks held by kworker/u4:3/1167:
 #0: ffff888019f8a138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x761/0x1010 kernel/workqueue.c:-1
 #1: ffffc9000474fd00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x79f/0x1010 kernel/workqueue.c:2285
 #2: ffff888071cee0e0 (&type->s_umount_key#54){.+.+}-{3:3}, at: trylock_super+0x1c/0xf0 fs/super.c:418
 #3: ffff8880741d3948 (&jfs_ip->commit_mutex){+.+.}-{3:3}, at: jfs_commit_inode+0x1c7/0x520 fs/jfs/inode.c:108
4 locks held by kworker/u4:5/1269:
 #0: ffff888019f8a138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x761/0x1010 kernel/workqueue.c:-1
 #1: ffffc90004db7d00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x79f/0x1010 kernel/workqueue.c:2285
 #2: ffff88807d2140e0 (&type->s_umount_key#54){.+.+}-{3:3}, at: trylock_super+0x1c/0xf0 fs/super.c:418
 #3: ffff8880603af0c8 (&jfs_ip->commit_mutex){+.+.}-{3:3}, at: jfs_commit_inode+0x1c7/0x520 fs/jfs/inode.c:108
2 locks held by getty/3948:
 #0: ffff88802ba69098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc900021ce2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5df/0x1a70 drivers/tty/n_tty.c:2158
4 locks held by syz.0.17/4403:
4 locks held by syz.1.18/4497:
4 locks held by syz.2.19/4511:
4 locks held by kworker/u4:7/4533:
 #0: ffff888019f8a138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x761/0x1010 kernel/workqueue.c:-1
 #1: ffffc9000419fd00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x79f/0x1010 kernel/workqueue.c:2285
 #2: ffff88807741c0e0 (&type->s_umount_key#54){.+.+}-{3:3}, at: trylock_super+0x1c/0xf0 fs/super.c:418
 #3: ffff88804e078b08 (&jfs_ip->commit_mutex){+.+.}-{3:3}, at: jfs_commit_inode+0x1c7/0x520 fs/jfs/inode.c:108
4 locks held by syz.3.20/4534:
4 locks held by kworker/u4:8/4544:
 #0: ffff888019f8a138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x761/0x1010 kernel/workqueue.c:-1
 #1: ffffc900041efd00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x79f/0x1010 kernel/workqueue.c:2285
 #2: ffff88802594e0e0 (&type->s_umount_key#54){.+.+}-{3:3}, at: trylock_super+0x1c/0xf0 fs/super.c:418
 #3: ffff8880600681c8 (&jfs_ip->commit_mutex){+.+.}-{3:3}, at: jfs_commit_inode+0x1c7/0x520 fs/jfs/inode.c:108
4 locks held by kworker/u4:9/4556:
 #0: ffff888019f8a138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x761/0x1010 kernel/workqueue.c:-1
 #1: ffffc9000420fd00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x79f/0x1010 kernel/workqueue.c:2285
 #2: ffff888029f040e0 (&type->s_umount_key#54){.+.+}-{3:3}, at: trylock_super+0x1c/0xf0 fs/super.c:418
 #3: ffff88806006c288 (&jfs_ip->commit_mutex){+.+.}-{3:3}, at: jfs_commit_inode+0x1c7/0x520 fs/jfs/inode.c:108
4 locks held by syz.4.21/4557:
4 locks held by syz.5.22/4579:
4 locks held by syz.6.23/4608:
2 locks held by kworker/u4:11/4619:
6 locks held by syz.7.24/4632:

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

NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x3a2/0x3d0 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
 watchdog+0xe0f/0xe50 kernel/hung_task.c:369
 kthread+0x436/0x520 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4632 Comm: syz.7.24 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
RIP: 0010:get_current arch/x86/include/asm/current.h:15 [inline]
RIP: 0010:__sanitizer_cov_trace_pc+0x4/0x60 kernel/kcov.c:205
Code: 84 00 00 00 00 00 53 48 89 fb e8 17 00 00 00 48 8b 3d 50 c4 10 0c 48 89 de 5b e9 27 55 44 00 00 00 cc cc 00 00 cc 48 8b 04 24 <65> 48 8b 0d a4 39 89 7e 65 8b 15 a5 39 89 7e 81 e2 00 01 ff 00 74
RSP: 0018:ffffc9000478f718 EFLAGS: 00000246
RAX: ffffffff82d0b775 RBX: ffff88807d148000 RCX: ffff88802104bb80
RDX: 0000000000000000 RSI: 0000000000000006 RDI: 00000000000000ff
RBP: 0000000000000000 R08: ffff88807d14811f R09: 1ffff1100fa29023
R10: dffffc0000000000 R11: ffffed100fa29024 R12: 1ffff1100fa29002
R13: dffffc0000000000 R14: 000000000000000d R15: 1ffff1100fa29000
FS:  000055556157c500(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055556157c4e8 CR3: 0000000078738000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 dtSplitRoot+0x715/0x1510 fs/jfs/jfs_dtree.c:1981
 dtSplitUp fs/jfs/jfs_dtree.c:993 [inline]
 dtInsert+0xe67/0x5830 fs/jfs/jfs_dtree.c:871
 jfs_mkdir+0x758/0xad0 fs/jfs/namei.c:270
 vfs_mkdir+0x387/0x570 fs/namei.c:4073
 do_mkdirat+0x1df/0x5b0 fs/namei.c:4098
 __do_sys_mkdir fs/namei.c:4118 [inline]
 __se_sys_mkdir fs/namei.c:4116 [inline]
 __x64_sys_mkdir+0x6a/0x80 fs/namei.c:4116
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7ffbd3383e59
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffdf9c49248 EFLAGS: 00000246 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007ffbd35fcfa0 RCX: 00007ffbd3383e59
RDX: 0000000000000000 RSI: 0000000000000010 RDI: 0000200000000d40
RBP: 00007ffbd3419d6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffbd35fcfac R14: 00007ffbd35fcfa0 R15: 00007ffbd35fcfa0
 </TASK>

Crashes (82):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/05/30 11:06 linux-5.15.y 241d66fa280c 6b4a8443 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2025/12/09 05:32 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2025/10/26 10:38 linux-5.15.y ac56c046adf4 c0460fcd .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2025/04/21 05:32 linux-5.15.y f7347f400572 2a20f901 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2025/06/25 17:10 linux-5.15.y 1c700860e8bc 26d77996 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan-arm64 INFO: task hung in jfs_commit_inode
2024/03/16 23:33 linux-5.15.y b95c01af2113 d615901c .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 INFO: task hung in jfs_commit_inode
2026/06/08 03:17 linux-5.15.y dc027a595035 cc095639 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2026/05/30 08:50 linux-5.15.y 241d66fa280c 6b4a8443 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2026/02/16 06:43 linux-5.15.y e45d5d41c134 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2026/01/15 17:57 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2025/10/26 06:59 linux-5.15.y ac56c046adf4 c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2025/08/27 16:13 linux-5.15.y c79648372d02 e12e5ba4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2025/06/20 13:29 linux-5.15.y 1c700860e8bc 804b3919 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2025/06/15 18:45 linux-5.15.y 1c700860e8bc 5f4b362d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2025/06/12 17:37 linux-5.15.y 1c700860e8bc 98683f8f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2025/06/08 13:10 linux-5.15.y 1c700860e8bc 4826c28e .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2025/05/13 09:37 linux-5.15.y 3b8db0e4f263 f6671af7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2025/05/11 07:20 linux-5.15.y 3b8db0e4f263 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2025/04/21 13:42 linux-5.15.y f7347f400572 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2025/04/21 01:55 linux-5.15.y f7347f400572 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2025/03/08 15:13 linux-5.15.y c16c81c81336 7e3bd60d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2025/03/04 04:56 linux-5.15.y c16c81c81336 c3901742 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2025/01/07 14:44 linux-5.15.y 91786f140358 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2025/01/03 00:04 linux-5.15.y 91786f140358 d3ccff63 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2024/12/29 09:58 linux-5.15.y 91786f140358 d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2024/10/14 10:08 linux-5.15.y 3a5928702e71 084d8178 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2024/10/06 21:15 linux-5.15.y 3a5928702e71 d7906eff .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2024/09/08 09:31 linux-5.15.y 14e468424d3e 9750182a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2024/09/05 06:33 linux-5.15.y 14e468424d3e dfbe2ed4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2024/08/18 17:29 linux-5.15.y 7e89efd3ae1c dbc93b08 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2024/08/12 09:34 linux-5.15.y 7e89efd3ae1c 6f4edef4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2024/08/05 01:47 linux-5.15.y 7e89efd3ae1c 1786a2a8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2024/05/13 01:56 linux-5.15.y 284087d4f7d5 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2024/05/13 01:53 linux-5.15.y 284087d4f7d5 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2024/05/13 01:52 linux-5.15.y 284087d4f7d5 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2024/05/11 05:34 linux-5.15.y 284087d4f7d5 f7c35481 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2024/05/11 05:34 linux-5.15.y 284087d4f7d5 f7c35481 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2024/05/11 05:33 linux-5.15.y 284087d4f7d5 f7c35481 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2024/05/11 05:32 linux-5.15.y 284087d4f7d5 f7c35481 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2024/05/11 05:32 linux-5.15.y 284087d4f7d5 f7c35481 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2024/04/27 12:04 linux-5.15.y c52b9710c83d 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in jfs_commit_inode
2025/06/24 10:06 linux-5.15.y 1c700860e8bc e2f27c35 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in jfs_commit_inode
2025/06/03 18:03 linux-5.15.y 98f47d0e9b8c a30356b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in jfs_commit_inode
2025/04/05 17:46 linux-5.15.y 0c935c049b5c c53ea9c9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in jfs_commit_inode
2025/04/02 11:40 linux-5.15.y 0c935c049b5c c799dfdd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in jfs_commit_inode
2025/04/01 01:07 linux-5.15.y 0c935c049b5c d3999433 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in jfs_commit_inode
2025/03/14 08:50 linux-5.15.y 0c935c049b5c e2826670 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in jfs_commit_inode
2025/01/25 12:56 linux-5.15.y 003148680b79 9fbd772e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in jfs_commit_inode
2024/12/18 09:20 linux-5.15.y 963e654022cc a0626d3a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in jfs_commit_inode
2024/11/23 15:23 linux-5.15.y 0a51d2d4527b 68da6d95 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in jfs_commit_inode
2024/11/09 16:54 linux-5.15.y 3c17fc483905 6b856513 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in jfs_commit_inode
2024/11/07 06:22 linux-5.15.y 72244eab0dad df3dc63b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in jfs_commit_inode
2024/10/27 01:03 linux-5.15.y 74cdd62cb470 65e8686b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in jfs_commit_inode
2024/10/07 15:09 linux-5.15.y 3a5928702e71 d7906eff .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in jfs_commit_inode
2024/10/05 08:47 linux-5.15.y 3a5928702e71 d7906eff .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in jfs_commit_inode
2024/09/03 18:57 linux-5.15.y fa93fa65db6e 326f9c5a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in jfs_commit_inode
2024/09/02 16:44 linux-5.15.y fa93fa65db6e 1eda0d14 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in jfs_commit_inode
2024/08/18 08:43 linux-5.15.y 7e89efd3ae1c dbc93b08 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in jfs_commit_inode
2024/08/07 09:30 linux-5.15.y 7e89efd3ae1c 1ef9fe42 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in jfs_commit_inode
2024/08/05 18:30 linux-5.15.y 7e89efd3ae1c e35c337f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in jfs_commit_inode
2024/04/27 12:05 linux-5.15.y c52b9710c83d 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in jfs_commit_inode
* Struck through repros no longer work on HEAD.