syzbot


INFO: task hung in filename_create (4)

Status: upstream: reported C repro on 2021/12/21 22:55
Subsystems: fs
[Documentation on labels]
Reported-by: syzbot+72c5cf124089bc318016@syzkaller.appspotmail.com
First crash: 1504d, last: 18h49m
Cause bisection: failed (error log, bisect log)
  
Fix bisection: failed (error log, bisect log)
  
Discussions (11)
Title Replies (including bot) Last reply
[syzbot] Monthly fs report (Dec 2025) 0 (1) 2025/12/01 12:38
[syzbot] Monthly fs report (Sep 2025) 0 (1) 2025/09/30 07:56
[syzbot] Monthly fs report (Aug 2025) 0 (1) 2025/08/29 12:52
[syzbot] Monthly fs report (Jul 2024) 0 (1) 2024/07/18 07:59
[syzbot] Monthly fs report (Mar 2024) 0 (1) 2024/03/16 12:09
[syzbot] Monthly fs report (Feb 2024) 0 (1) 2024/02/12 21:31
[syzbot] Monthly fs report (Dec 2023) 0 (1) 2023/12/12 22:02
[syzbot] Monthly fs report (Nov 2023) 0 (1) 2023/11/11 01:08
[syzbot] Monthly fs report (Oct 2023) 0 (1) 2023/10/10 13:22
[syzbot] Monthly fs report (May 2023) 0 (1) 2023/05/06 14:02
[syzbot] INFO: task hung in filename_create (4) 0 (1) 2021/12/21 22:55
Similar bugs (15)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 INFO: task hung in filename_create 1 6 2234d 2334d 0/1 auto-closed as invalid on 2020/03/17 23:03
upstream INFO: task hung in filename_create (2) fs 1 11 2218d 2322d 0/29 auto-closed as invalid on 2020/03/04 11:54
android-49 INFO: task hung in filename_create 1 C 44 2683d 2454d 0/3 public: reported C repro on 2019/04/13 00:00
upstream INFO: task hung in filename_create (3) fs 1 16 1683d 1839d 0/29 auto-closed as invalid on 2021/08/20 18:08
linux-6.1 INFO: task hung in filename_create (2) origin:upstream missing-backport 1 C inconclusive 12 5d21h 400d 0/3 upstream: reported C repro on 2024/11/26 07:48
linux-4.19 INFO: task hung in filename_create (3) 1 3 1511d 1574d 0/1 auto-closed as invalid on 2022/03/11 04:15
android-44 INFO: task hung in filename_create 1 1 2816d 2816d 0/2 auto-closed as invalid on 2019/02/22 14:19
linux-4.19 INFO: task hung in filename_create (2) 1 1 1775d 1775d 0/1 auto-closed as invalid on 2021/06/20 16:38
linux-6.6 INFO: task hung in filename_create 1 1 7d14h 7d14h 0/2 upstream: reported on 2025/12/24 02:32
linux-4.14 INFO: task hung in filename_create 1 2 2207d 2211d 0/1 auto-closed as invalid on 2020/04/14 04:42
linux-4.19 INFO: task hung in filename_create (4) 1 2 1144d 1208d 0/1 auto-obsoleted due to no activity on 2023/03/13 04:19
linux-5.15 INFO: task hung in filename_create missing-backport origin:upstream 1 C unreliable 51 19d 625d 0/3 upstream: reported C repro on 2024/04/15 05:31
android-44 INFO: task hung in filename_create (2) 1 1 2437d 2437d 0/2 auto-closed as invalid on 2019/10/25 08:49
linux-6.1 INFO: task hung in filename_create 1 6 595d 620d 0/3 auto-obsoleted due to no activity on 2024/08/23 04:31
upstream INFO: task hung in filename_create fs 1 121 2527d 2812d 0/29 closed as dup on 2018/09/08 15:39
Last patch testing requests (8)
Created Duration User Patch Repo Result
2024/03/08 06:27 1h47m retest repro upstream report log
2024/03/08 06:15 20m retest repro upstream OK log
2024/01/07 11:45 22m retest repro upstream report log
2023/12/11 16:44 31m retest repro upstream report log
2023/10/22 10:09 21m retest repro upstream report log
2023/08/30 03:43 15m retest repro upstream report log
2023/08/27 15:26 28m retest repro upstream OK log
2023/08/27 15:26 52m retest repro upstream OK log

Sample crash report:
INFO: task syz-executor140:5096 blocked for more than 143 seconds.
      Not tainted 6.8.0-syzkaller-08951-gfe46a7dd189e #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor140 state:D stack:26832 pid:5096  tgid:5095  ppid:5094   flags:0x00000006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5409 [inline]
 __schedule+0xf15/0x5c70 kernel/sched/core.c:6736
 __schedule_loop kernel/sched/core.c:6813 [inline]
 schedule+0xe7/0x350 kernel/sched/core.c:6828
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6885
 rwsem_down_write_slowpath kernel/locking/rwsem.c:1178 [inline]
 __down_write_common+0x950/0x13f0 kernel/locking/rwsem.c:1306
 inode_lock_nested include/linux/fs.h:828 [inline]
 filename_create+0x1c2/0x530 fs/namei.c:3892
 do_mkdirat+0xab/0x3a0 fs/namei.c:4141
 __do_sys_mkdir fs/namei.c:4169 [inline]
 __se_sys_mkdir fs/namei.c:4167 [inline]
 __x64_sys_mkdir+0xf1/0x140 fs/namei.c:4167
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xd2/0x260 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x6d/0x75
RIP: 0033:0x7f09cb287a99
RSP: 002b:00007f09cb23e218 EFLAGS: 00000246 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007f09cb3106c8 RCX: 00007f09cb287a99
RDX: 00007f09cb287a99 RSI: 0000000000000000 RDI: 0000000020000000
RBP: 00007f09cb3106c0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f09cb3106cc
R13: 00007f09cb2dc0c0 R14: 0000000020004ac0 R15: 0030656c69662f2e
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/29:
 #0: ffffffff8d7b08e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:298 [inline]
 #0: ffffffff8d7b08e0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:750 [inline]
 #0: ffffffff8d7b08e0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x75/0x340 kernel/locking/lockdep.c:6614
2 locks held by kworker/u8:2/41:
 #0: ffff8880b953e698 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x29/0x130 kernel/sched/core.c:559
 #1: ffff8880b9528a08 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x2d9/0x900 kernel/sched/psi.c:988
2 locks held by getty/4811:
 #0: ffff88802e60a0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x24/0x80 drivers/tty/tty_ldisc.c:243
 #1: ffffc900015e02f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0xfc8/0x1490 drivers/tty/n_tty.c:2201
2 locks held by syz-executor140/5096:
 #0: ffff88802ab6c420 (sb_writers#10){.+.+}-{0:0}, at: filename_create+0x10d/0x530 fs/namei.c:3885
 #1: ffff8880771f82b8 (&sb->s_type->i_mutex_key#15/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:828 [inline]
 #1: ffff8880771f82b8 (&sb->s_type->i_mutex_key#15/1){+.+.}-{3:3}, at: filename_create+0x1c2/0x530 fs/namei.c:3892
3 locks held by syz-executor140/5098:

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

NMI backtrace for cpu 1
CPU: 1 PID: 29 Comm: khungtaskd Not tainted 6.8.0-syzkaller-08951-gfe46a7dd189e #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+0x116/0x1f0 lib/dump_stack.c:114
 nmi_cpu_backtrace+0x27b/0x390 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x29c/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+0xf86/0x1210 kernel/hung_task.c:379
 kthread+0x2c1/0x3a0 kernel/kthread.c:388
 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:243
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 5098 Comm: syz-executor140 Not tainted 6.8.0-syzkaller-08951-gfe46a7dd189e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:lockdep_hardirqs_on_prepare+0x5d/0x420 kernel/locking/lockdep.c:4322
Code: 00 44 8b 0d dd a4 33 0e 45 85 c9 0f 84 4f 01 00 00 65 8b 05 5d d5 98 7e a9 00 00 f0 00 0f 85 3d 01 00 00 65 8b 05 cb 8c 97 7e <85> c0 0f 85 2e 01 00 00 65 8b 05 d0 89 97 7e 85 c0 0f 85 1f 01 00
RSP: 0018:ffffc9000335f688 EFLAGS: 00000046
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 1ffffffff1f3d467
RDX: 0000000000000000 RSI: ffffffff8b6e8820 RDI: ffffffff8d233b20
RBP: ffff888077167cb0 R08: 0000000000000000 R09: 0000000000000001
R10: ffffffff8f9e6f97 R11: 0000000000000003 R12: 0000000000000000
R13: ffff888077167cb0 R14: 00000000000392c0 R15: fffffffffffffff8
FS:  00007f09cb21d6c0(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055e26dcf8400 CR3: 0000000025d4e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 trace_hardirqs_on+0x36/0x40 kernel/trace/trace_preemptirq.c:61
 lookup_bh_lru fs/buffer.c:1385 [inline]
 __find_get_block+0x4af/0xc70 fs/buffer.c:1397
 bdev_getblk+0x2c/0xc0 fs/buffer.c:1423
 __bread_gfp+0xa9/0x370 fs/buffer.c:1474
 sb_bread include/linux/buffer_head.h:321 [inline]
 __exfat_ent_get fs/exfat/fatent.c:48 [inline]
 exfat_ent_get+0x1ce/0x480 fs/exfat/fatent.c:97
 exfat_readdir+0x11f8/0x1520 fs/exfat/dir.c:187
 exfat_iterate+0x3c2/0xad0 fs/exfat/dir.c:261
 wrap_directory_iterator+0xa5/0xe0 fs/readdir.c:67
 iterate_dir+0x292/0x9e0 fs/readdir.c:110
 __do_sys_getdents64 fs/readdir.c:409 [inline]
 __se_sys_getdents64 fs/readdir.c:394 [inline]
 __x64_sys_getdents64+0x14f/0x2e0 fs/readdir.c:394
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xd2/0x260 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x6d/0x75
RIP: 0033:0x7f09cb287a99
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 b1 18 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:00007f09cb21d218 EFLAGS: 00000246 ORIG_RAX: 00000000000000d9
RAX: ffffffffffffffda RBX: 00007f09cb3106d8 RCX: 00007f09cb287a99
RDX: 0000000000000098 RSI: 0000000020000080 RDI: 0000000000000004
RBP: 00007f09cb3106d0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f09cb3106dc
R13: 00007f09cb2dc0c0 R14: 0000000020004ac0 R15: 0030656c69662f2e
 </TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.488 msecs

Crashes (2390):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/14 19:35 upstream fe46a7dd189e c8349e48 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-selinux-root INFO: task hung in filename_create
2024/01/26 20:35 upstream ecb1b8288dc7 cc4a4020 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-smack-root INFO: task hung in filename_create
2023/10/08 06:46 upstream 59f3fd30af35 5e837c76 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in filename_create
2025/04/20 17:09 upstream 6fea5fabd332 2a20f901 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in filename_create
2023/07/25 03:03 upstream 20ea1e7d13c1 b03242d7 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in filename_create
2021/12/18 03:25 upstream 6441998e2e37 44068e19 .config console log report syz C ci-upstream-kasan-gce INFO: task hung in filename_create
2021/12/17 22:42 upstream 6441998e2e37 44068e19 .config console log report syz C ci-upstream-kasan-gce-selinux-root INFO: task hung in filename_create
2025/12/30 22:07 upstream dbf8fe85a16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/12/29 12:12 upstream 7839932417dd d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/12/23 09:03 upstream b927546677c8 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/12/21 19:49 upstream 9094662f6707 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/12/20 18:20 upstream dd9b004b7ff3 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/12/19 06:31 upstream 516471569089 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/12/18 21:09 upstream ea1013c15392 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/12/18 05:20 upstream ea1013c15392 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/12/17 18:03 upstream ea1013c15392 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in filename_create
2025/12/17 14:31 upstream ea1013c15392 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/12/15 00:54 upstream 8f0b4cce4481 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/12/11 20:50 upstream d358e5254674 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/12/08 19:34 upstream c2f2b01b74be d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/12/08 11:43 upstream ba65a4e7120a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/12/04 23:12 upstream 559e608c4655 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/12/04 19:33 upstream 559e608c4655 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/12/04 17:01 upstream 8f7aa3d3c732 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/12/04 02:50 upstream 3f9f0252130e d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/12/03 07:14 upstream d61f1cc5db79 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/12/02 19:59 upstream 4a26e7032d7d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/12/01 19:42 upstream 7d0a66e4bb90 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/11/29 20:46 upstream 19eef1d98eed d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/11/27 15:28 upstream 765e56e41a5a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/11/24 11:23 upstream ac3fd01e4c1e 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in filename_create
2025/11/23 01:29 upstream 89edd36fd801 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/11/21 13:46 upstream fd95357fd8c6 280ea308 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/11/21 02:22 upstream 8e621c9a3375 2cc4c24a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/11/13 01:50 upstream 24172e0d7990 07e030de .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/11/12 23:07 upstream 24172e0d7990 07e030de .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/11/12 19:12 upstream 24172e0d7990 07e030de .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/11/12 12:53 upstream 24172e0d7990 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/11/12 02:48 upstream 24172e0d7990 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/11/11 13:01 upstream 4427259cc7f7 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/11/11 01:46 upstream 4ea7c1717f3f 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/11/10 12:33 upstream e9a6fb0bcdd7 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/11/10 09:03 upstream e9a6fb0bcdd7 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2025/03/18 20:13 upstream 76b6905c11fd 22a6c2b1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in filename_create
2021/11/18 03:33 upstream ee1703cda8dc cafff8b6 .config console log report info ci-upstream-kasan-gce-selinux-root INFO: task hung in filename_create
2024/10/26 23:55 net-next 6d858708d465 65e8686b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in filename_create
2025/12/30 18:54 linux-next cc3aa43b44bd d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in filename_create
2025/12/27 02:09 linux-next cc3aa43b44bd d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in filename_create
2025/12/14 13:03 linux-next d9771d0dbe18 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in filename_create
2025/11/27 02:26 linux-next 663d0d1af3fa d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in filename_create
2025/11/25 06:09 linux-next 422f3140bbcb 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in filename_create
2025/11/25 05:37 linux-next 422f3140bbcb 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in filename_create
2025/11/24 19:29 linux-next 422f3140bbcb bf6fe8fe .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in filename_create
2025/11/24 08:27 linux-next d724c6f85e80 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in filename_create
2025/11/24 07:01 linux-next d724c6f85e80 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in filename_create
2025/11/24 02:35 linux-next d724c6f85e80 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in filename_create
2025/11/22 04:55 linux-next d724c6f85e80 c31c1b0b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in filename_create
2025/11/22 02:51 linux-next d724c6f85e80 c31c1b0b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in filename_create
2025/11/22 01:48 linux-next d724c6f85e80 c31c1b0b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in filename_create
2025/11/20 00:02 linux-next fe4d0dea039f 26ee5237 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in filename_create
2025/11/19 17:43 linux-next fe4d0dea039f 26ee5237 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in filename_create
2025/11/11 19:39 linux-next 2666975a8905 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in filename_create
2025/07/12 17:01 linux-next a62b7a37e6fc 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce INFO: task hung in filename_create
2025/07/13 05:44 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci ec4801305969 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in filename_create
* Struck through repros no longer work on HEAD.