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: 1579d, last: 4h45m
Cause bisection: failed (error log, bisect log)
  
Fix bisection: failed (error log, bisect log)
  
Discussions (12)
Title Replies (including bot) Last reply
[syzbot] Monthly fs report (Mar 2026) 0 (1) 2026/03/06 11:53
[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 2309d 2409d 0/1 auto-closed as invalid on 2020/03/17 23:03
upstream INFO: task hung in filename_create (2) fs 1 11 2293d 2398d 0/29 auto-closed as invalid on 2020/03/04 11:54
android-49 INFO: task hung in filename_create 1 C 44 2758d 2529d 0/3 public: reported C repro on 2019/04/13 00:00
upstream INFO: task hung in filename_create (3) fs 1 16 1759d 1914d 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 81d 475d 0/3 upstream: reported C repro on 2024/11/26 07:48
linux-4.19 INFO: task hung in filename_create (3) 1 3 1586d 1649d 0/1 auto-closed as invalid on 2022/03/11 04:15
android-44 INFO: task hung in filename_create 1 1 2892d 2891d 0/2 auto-closed as invalid on 2019/02/22 14:19
linux-4.19 INFO: task hung in filename_create (2) 1 1 1850d 1850d 0/1 auto-closed as invalid on 2021/06/20 16:38
linux-6.6 INFO: task hung in filename_create 1 2 62d 82d 0/2 upstream: reported on 2025/12/24 02:32
linux-4.14 INFO: task hung in filename_create 1 2 2282d 2286d 0/1 auto-closed as invalid on 2020/04/14 04:42
linux-4.19 INFO: task hung in filename_create (4) 1 2 1219d 1283d 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 24d 700d 0/3 upstream: reported C repro on 2024/04/15 05:31
android-44 INFO: task hung in filename_create (2) 1 1 2512d 2512d 0/2 auto-closed as invalid on 2019/10/25 08:49
linux-6.1 INFO: task hung in filename_create 1 6 670d 696d 0/3 auto-obsoleted due to no activity on 2024/08/23 04:31
upstream INFO: task hung in filename_create fs 1 121 2602d 2888d 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.0.17:6098 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.17        state:D stack:25952 pid:6098  tgid:6088  ppid:5995   task_flags:0x400040 flags:0x00080002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5295 [inline]
 __schedule+0x14de/0x5210 kernel/sched/core.c:6907
 __schedule_loop kernel/sched/core.c:6989 [inline]
 rt_mutex_schedule+0x76/0xf0 kernel/sched/core.c:7285
 rt_mutex_slowlock_block kernel/locking/rtmutex.c:1647 [inline]
 __rt_mutex_slowlock kernel/locking/rtmutex.c:1721 [inline]
 __rt_mutex_slowlock_locked+0x1f8f/0x25c0 kernel/locking/rtmutex.c:1760
 rt_mutex_slowlock+0xbd/0x170 kernel/locking/rtmutex.c:1800
 __rt_mutex_lock kernel/locking/rtmutex.c:1815 [inline]
 rwbase_write_lock+0x14d/0x730 kernel/locking/rwbase_rt.c:244
 inode_lock_nested include/linux/fs.h:1073 [inline]
 __start_dirop fs/namei.c:2923 [inline]
 start_dirop fs/namei.c:2934 [inline]
 filename_create+0x200/0x370 fs/namei.c:4922
 filename_mkdirat+0xd2/0x520 fs/namei.c:5259
 __do_sys_mkdirat fs/namei.c:5287 [inline]
 __se_sys_mkdirat+0x35/0x150 fs/namei.c:5284
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f6c2a76bf79
RSP: 002b:00007f6c29dad028 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007f6c2a9e6090 RCX: 00007f6c2a76bf79
RDX: 0000000000000000 RSI: 00002000000000c0 RDI: ffffffffffffff9c
RBP: 00007f6c2a8027e0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f6c2a9e6128 R14: 00007f6c2a9e6090 R15: 00007ffeff7ae108
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/37:
 #0: ffffffff8dbcd480 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:312 [inline]
 #0: ffffffff8dbcd480 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:850 [inline]
 #0: ffffffff8dbcd480 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6775
2 locks held by getty/5552:
 #0: ffff88803722f0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc90003e8b2e0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x462/0x13c0 drivers/tty/n_tty.c:2211
7 locks held by syz.0.17/6089:
2 locks held by syz.0.17/6098:
 #0: ffff88803b3de480 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493
 #1: ffff88805bd5a868 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1073 [inline]
 #1: ffff88805bd5a868 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: __start_dirop fs/namei.c:2923 [inline]
 #1: ffff88805bd5a868 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: start_dirop fs/namei.c:2934 [inline]
 #1: ffff88805bd5a868 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: filename_create+0x200/0x370 fs/namei.c:4922
8 locks held by syz.1.18/6167:
2 locks held by syz.1.18/6171:
 #0: ffff8880241a0480 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493
 #1: ffff888044672868 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1073 [inline]
 #1: ffff888044672868 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: __start_dirop fs/namei.c:2923 [inline]
 #1: ffff888044672868 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: start_dirop fs/namei.c:2934 [inline]
 #1: ffff888044672868 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: filename_create+0x200/0x370 fs/namei.c:4922
5 locks held by syz.2.19/6193:
2 locks held by syz.2.19/6197:
 #0: ffff88803938e480 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493
 #1: ffff88805bc5c038 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1073 [inline]
 #1: ffff88805bc5c038 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: __start_dirop fs/namei.c:2923 [inline]
 #1: ffff88805bc5c038 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: start_dirop fs/namei.c:2934 [inline]
 #1: ffff88805bc5c038 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: filename_create+0x200/0x370 fs/namei.c:4922
6 locks held by syz.3.20/6220:
2 locks held by syz.3.20/6224:
 #0: ffff88805c5b6480 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493
 #1: ffff88805bd5c038 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1073 [inline]
 #1: ffff88805bd5c038 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: __start_dirop fs/namei.c:2923 [inline]
 #1: ffff88805bd5c038 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: start_dirop fs/namei.c:2934 [inline]
 #1: ffff88805bd5c038 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: filename_create+0x200/0x370 fs/namei.c:4922
2 locks held by syz.4.21/6260:
 #0: ffff88805c57e480 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493
 #1: ffff888044659098 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1073 [inline]
 #1: ffff888044659098 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: __start_dirop fs/namei.c:2923 [inline]
 #1: ffff888044659098 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: start_dirop fs/namei.c:2934 [inline]
 #1: ffff888044659098 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: filename_create+0x200/0x370 fs/namei.c:4922
6 locks held by syz.4.21/6265:
6 locks held by syz.5.22/6297:
2 locks held by syz.5.22/6301:
 #0: ffff88803af58480 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493
 #1: ffff8880445c3450 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1073 [inline]
 #1: ffff8880445c3450 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: __start_dirop fs/namei.c:2923 [inline]
 #1: ffff8880445c3450 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: start_dirop fs/namei.c:2934 [inline]
 #1: ffff8880445c3450 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: filename_create+0x200/0x370 fs/namei.c:4922
6 locks held by syz.6.23/6335:
2 locks held by syz.6.23/6336:
 #0: ffff88805a2c0480 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493
 #1: ffff888044462868 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1073 [inline]
 #1: ffff888044462868 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: __start_dirop fs/namei.c:2923 [inline]
 #1: ffff888044462868 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: start_dirop fs/namei.c:2934 [inline]
 #1: ffff888044462868 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: filename_create+0x200/0x370 fs/namei.c:4922
2 locks held by kworker/u8:2/6372:
2 locks held by syz.7.24/6376:
 #0: ffff8880114a0480 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493
 #1: ffff88805bfc84b0 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1073 [inline]
 #1: ffff88805bfc84b0 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: __start_dirop fs/namei.c:2923 [inline]
 #1: ffff88805bfc84b0 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: start_dirop fs/namei.c:2934 [inline]
 #1: ffff88805bfc84b0 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: filename_create+0x200/0x370 fs/namei.c:4922
7 locks held by syz.7.24/6381:

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 37 Comm: khungtaskd Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x274/0x2d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x17a/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:161 [inline]
 __sys_info lib/sys_info.c:157 [inline]
 sys_info+0x135/0x170 lib/sys_info.c:165
 check_hung_uninterruptible_tasks kernel/hung_task.c:346 [inline]
 watchdog+0xf90/0xfe0 kernel/hung_task.c:515
 kthread+0x388/0x470 kernel/kthread.c:467
 ret_from_fork+0x51e/0xb90 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 6372 Comm: kworker/u8:2 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
Workqueue: bat_events batadv_tt_purge
RIP: 0010:__lock_acquire+0x9/0x2cf0 kernel/locking/lockdep.c:5081
Code: 0a 00 00 00 5b e9 a7 55 00 00 5b e9 01 01 77 09 cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 55 41 57 41 56 41 55 41 54 <53> 48 81 ec e8 00 00 00 65 48 8b 05 17 a0 89 10 48 89 84 24 e0 00
RSP: 0018:ffffc90004e478b0 EFLAGS: 00000046
RAX: 0000000000000000 RBX: ffffc90004e4795c RCX: 0000000000000002
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff8dbcd480
RBP: 00000000ffffffff R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: fffffbfff1e9250f R12: 0000000000000003
R13: 0000000000000003 R14: ffff88802c1faa04 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff888126695000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000561f066c3c40 CR3: 0000000043446000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 reacquire_held_locks+0x104/0x190 kernel/locking/lockdep.c:5385
 __lock_release kernel/locking/lockdep.c:5574 [inline]
 lock_release+0x199/0x3a0 kernel/locking/lockdep.c:5889
 __local_bh_enable_ip+0x98/0x2b0 kernel/softirq.c:268
 local_bh_enable include/linux/bottom_half.h:33 [inline]
 spin_unlock_bh include/linux/spinlock_rt.h:116 [inline]
 batadv_tt_local_purge+0x2fc/0x380 net/batman-adv/translation-table.c:1315
 batadv_tt_purge+0x35/0xa10 net/batman-adv/translation-table.c:3509
 process_one_work kernel/workqueue.c:3275 [inline]
 process_scheduled_works+0xaec/0x17a0 kernel/workqueue.c:3358
 worker_thread+0xa50/0xfc0 kernel/workqueue.c:3439
 kthread+0x388/0x470 kernel/kthread.c:467
 ret_from_fork+0x51e/0xb90 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>

Crashes (2595):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/02/16 23:48 upstream c22e26bd0906 5d52cba5 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs INFO: task hung in filename_create
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
2026/03/16 14:21 upstream f338e7738378 64e21424 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/16 12:51 upstream f338e7738378 64e21424 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/16 10:59 upstream f338e7738378 64e21424 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/16 04:31 upstream 4f3df2e5ea69 ee8d34d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/15 18:02 upstream 267594792a71 ee8d34d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/15 15:00 upstream 267594792a71 ee8d34d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/15 11:12 upstream 267594792a71 ee8d34d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/15 10:11 upstream 267594792a71 ee8d34d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/15 06:59 upstream 69237f8c1f69 ee8d34d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/15 02:30 upstream 69237f8c1f69 ee8d34d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/15 01:16 upstream 69237f8c1f69 ee8d34d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/14 16:37 upstream 1c9982b49613 ee8d34d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/14 15:35 upstream 1c9982b49613 ee8d34d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/14 06:38 upstream 1c9982b49613 ee8d34d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/13 21:46 upstream b36eb6e3f5d8 351cb5cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/13 16:03 upstream 0257f64bdac7 351cb5cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/13 13:31 upstream 0257f64bdac7 2f7f359d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/13 02:04 upstream 0257f64bdac7 2f7f359d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/13 00:43 upstream 0257f64bdac7 2f7f359d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/12 20:27 upstream 80234b5ab240 4efadf07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/12 16:34 upstream 80234b5ab240 4efadf07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/12 14:03 upstream 80234b5ab240 4efadf07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/12 00:11 upstream b29fb8829bff 2d88ab01 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/11 22:19 upstream b29fb8829bff 2d88ab01 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/11 18:40 upstream b29fb8829bff 2d88ab01 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/11 05:14 upstream b4f0dd314b39 86914af9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/10 19:15 upstream 1f318b96cc84 4683d576 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/10 12:27 upstream 1f318b96cc84 6972f302 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/10 03:25 upstream 1f318b96cc84 6972f302 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/09 19:23 upstream 1f318b96cc84 176bead5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/09 11:44 upstream 1f318b96cc84 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/08 13:20 upstream c23719abc330 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/08 10:12 upstream c23719abc330 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/08 08:07 upstream c23719abc330 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/08 06:03 upstream c23719abc330 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/08 00:36 upstream 4ae12d8bd9a8 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/07 12:56 upstream 651690480a96 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/07 08:00 upstream 651690480a96 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/07 05:00 upstream 651690480a96 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/07 02:37 upstream 651690480a96 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/06 14:30 upstream 5ee8dbf54602 41d8037d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/06 09:30 upstream 5ee8dbf54602 31e9c887 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/06 04:07 upstream 5ee8dbf54602 31e9c887 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2026/03/06 03:02 upstream 5ee8dbf54602 31e9c887 .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/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
2026/03/15 22:35 linux-next b84a0ebe421c ee8d34d6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in filename_create
2026/03/15 05:23 linux-next b84a0ebe421c ee8d34d6 .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.