syzbot


INFO: task hung in path_openat (7)

Status: upstream: reported C repro on 2022/10/06 10:29
Subsystems: fs
[Documentation on labels]
Reported-by: syzbot+950a0cdaa2fdd14f5bdc@syzkaller.appspotmail.com
First crash: 1187d, last: now
Cause bisection: introduced by (bisect log) [merge commit]:
commit 4223a5be80b8998d717c6b0e1000070e0e336bf3
Author: Jens Axboe <axboe@kernel.dk>
Date: Thu Dec 10 14:08:22 2020 +0000

  Merge branch 'md-fixes' of https://git.kernel.org/pub/scm/linux/kernel/git/song/md into block-5.10

Crash: BUG: scheduling while atomic in corrupted (log)
Repro: C syz .config
  
Discussions (14)
Title Replies (including bot) Last reply
[syzbot] INFO: task hung in path_openat (7) 0 (2) 2024/09/06 21:56
[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 exfat report (Nov 2023) 2 (3) 2023/11/29 15:48
[syzbot] Monthly kernfs report (Nov 2023) 0 (1) 2023/11/29 13:03
[syzbot] Monthly nilfs report (Oct 2023) 0 (1) 2023/11/01 10:11
[syzbot] Monthly nilfs report (Sep 2023) 0 (1) 2023/10/02 09:42
[syzbot] Monthly exfat report (Aug 2023) 0 (1) 2023/08/09 12:33
[syzbot] Monthly ext4 report (Jul 2023) 0 (1) 2023/07/06 14:18
[syzbot] Monthly nilfs report (May 2023) 0 (1) 2023/05/29 08:50
[syzbot] Monthly nilfs report (Apr 2023) 0 (1) 2023/04/27 10:39
[syzbot] Monthly nilfs report 0 (1) 2023/03/27 11:03
[syzbot] [ext4] Monthly Report 0 (1) 2023/03/24 15:59
Similar bugs (18)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 INFO: task hung in path_openat 2 2072d 2105d 0/1 auto-closed as invalid on 2020/01/11 07:40
linux-6.1 INFO: task hung in path_openat (4) origin:upstream missing-backport C 20 12d 193d 0/3 upstream: reported C repro on 2024/11/04 05:51
upstream INFO: task hung in path_openat (4) fuse 1 1843d 1843d 0/28 auto-closed as invalid on 2020/07/28 10:23
upstream INFO: task hung in path_openat (3) fs 4 2003d 2119d 0/28 auto-closed as invalid on 2020/02/19 20:16
linux-6.1 INFO: task hung in path_openat (2) 1 503d 503d 0/3 auto-obsoleted due to no activity on 2024/04/08 11:39
linux-5.15 INFO: task hung in path_openat (2) origin:upstream missing-backport C 110 3d01h 398d 0/3 upstream: reported C repro on 2024/04/14 03:45
linux-4.19 INFO: task hung in path_openat (2) 1 1273d 1273d 0/1 auto-closed as invalid on 2022/03/21 04:47
linux-4.14 INFO: task hung in path_openat 1 1513d 1513d 0/1 auto-closed as invalid on 2021/07/23 23:26
android-49 INFO: task hung in path_openat 64 2243d 2224d 0/3 auto-closed as invalid on 2019/09/22 08:41
upstream INFO: task hung in path_openat (5) fs 23 1484d 1645d 0/28 auto-closed as invalid on 2021/07/22 20:44
linux-4.19 INFO: task hung in path_openat (3) f2fs jfs 20 850d 1009d 0/1 upstream: reported on 2022/08/11 13:14
upstream INFO: task hung in path_openat (6) fs 13 1219d 1370d 0/28 closed as invalid on 2022/02/07 19:19
android-414 INFO: task hung in path_openat 42 2147d 2226d 0/1 auto-closed as invalid on 2019/10/28 21:04
linux-6.1 INFO: task hung in path_openat 3 671d 773d 0/3 auto-obsoleted due to no activity on 2023/10/23 12:08
linux-6.1 INFO: task hung in path_openat (3) 28 273d 397d 0/3 auto-obsoleted due to no activity on 2024/10/25 20:43
upstream INFO: task hung in path_openat exfat 246 2311d 2601d 0/28 closed as dup on 2018/09/08 15:37
linux-5.15 INFO: task hung in path_openat C error 3 654d 766d 0/3 auto-obsoleted due to no activity on 2023/11/09 20:56
upstream INFO: task hung in path_openat (2) fs 1 2214d 2214d 0/28 closed as invalid on 2019/05/08 13:05

Sample crash report:
INFO: task syz-executor144:5829 blocked for more than 143 seconds.
      Not tainted 6.15.0-rc6-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor144 state:D stack:28024 pid:5829  tgid:5824  ppid:5822   task_flags:0x400040 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5382 [inline]
 __schedule+0x168f/0x4c70 kernel/sched/core.c:6767
 __schedule_loop kernel/sched/core.c:6845 [inline]
 schedule+0x165/0x360 kernel/sched/core.c:6860
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6917
 rwsem_down_write_slowpath+0xbec/0x1030 kernel/locking/rwsem.c:1176
 __down_write_common kernel/locking/rwsem.c:1304 [inline]
 __down_write kernel/locking/rwsem.c:1313 [inline]
 down_write+0x1ab/0x1f0 kernel/locking/rwsem.c:1578
 inode_lock include/linux/fs.h:867 [inline]
 open_last_lookups fs/namei.c:3797 [inline]
 path_openat+0x8da/0x3830 fs/namei.c:4036
 do_filp_open+0x1fa/0x410 fs/namei.c:4066
 do_sys_openat2+0x121/0x1c0 fs/open.c:1429
 do_sys_open fs/open.c:1444 [inline]
 __do_sys_creat fs/open.c:1522 [inline]
 __se_sys_creat fs/open.c:1516 [inline]
 __x64_sys_creat+0x8f/0xc0 fs/open.c:1516
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f4148283349
RSP: 002b:00007f4148216168 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 00007f414830a6b8 RCX: 00007f4148283349
RDX: ffffffffffffffb0 RSI: 0000000000000109 RDI: 0000200000000080
RBP: 00007f414830a6b0 R08: 00007f41482166c0 R09: 0000000000000000
R10: 00007ffd44bf0d47 R11: 0000000000000246 R12: 00007f414830a6bc
R13: 000000000000006e R14: 00007ffd44bf0c60 R15: 00007ffd44bf0d48
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/31:
 #0: ffffffff8df3d860 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #0: ffffffff8df3d860 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline]
 #0: ffffffff8df3d860 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6764
2 locks held by getty/5582:
 #0: ffff888030fdb0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc9000333b2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x43e/0x1400 drivers/tty/n_tty.c:2222
3 locks held by syz-executor144/5825:
2 locks held by syz-executor144/5829:
 #0: ffff888030c72420 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:556
 #1: ffff888075c88e20 (&type->i_mutex_dir_key#3){++++}-{4:4}, at: inode_lock include/linux/fs.h:867 [inline]
 #1: ffff888075c88e20 (&type->i_mutex_dir_key#3){++++}-{4:4}, at: open_last_lookups fs/namei.c:3797 [inline]
 #1: ffff888075c88e20 (&type->i_mutex_dir_key#3){++++}-{4:4}, at: path_openat+0x8da/0x3830 fs/namei.c:4036

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 31 Comm: khungtaskd Not tainted 6.15.0-rc6-syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x39e/0x3d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x17a/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:158 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:274 [inline]
 watchdog+0xfee/0x1030 kernel/hung_task.c:437
 kthread+0x70e/0x8a0 kernel/kthread.c:464
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:153
 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: 5825 Comm: syz-executor144 Not tainted 6.15.0-rc6-syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:native_save_fl arch/x86/include/asm/irqflags.h:26 [inline]
RIP: 0010:arch_local_save_flags arch/x86/include/asm/irqflags.h:109 [inline]
RIP: 0010:arch_irqs_disabled arch/x86/include/asm/irqflags.h:151 [inline]
RIP: 0010:lock_is_held_type+0x118/0x190 kernel/locking/lockdep.c:5940
Code: 01 00 00 00 48 c7 c7 f6 19 92 8d e8 92 17 00 00 b8 ff ff ff ff 65 0f c1 05 d5 80 23 07 83 f8 01 75 44 48 c7 04 24 00 00 00 00 <9c> 8f 04 24 f7 04 24 00 02 00 00 75 4c 41 f7 c4 00 02 00 00 74 01
RSP: 0018:ffffc9000403ef98 EFLAGS: 00000046
RAX: 0000000000000001 RBX: 0000000000000000 RCX: 7a94456ac6f02c00
RDX: 0000000000000000 RSI: ffffffff8d9219f6 RDI: ffffffff8bc0ffa0
RBP: 00000000ffffffff R08: ffff888030c70387 R09: 1ffff1100618e070
R10: dffffc0000000000 R11: ffffed100618e071 R12: 0000000000000246
R13: ffff888045d91e00 R14: ffffffff8df3d920 R15: 0000000000000003
FS:  00007f41482376c0(0000) GS:ffff8881261fb000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000558855da53f0 CR3: 000000007dc58000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 lock_is_held include/linux/lockdep.h:249 [inline]
 __might_resched+0xf5/0x610 kernel/sched/core.c:8780
 __ext4_mark_inode_dirty+0x90/0x700 fs/ext4/inode.c:6064
 ext4_dirty_inode+0xd0/0x110 fs/ext4/inode.c:6103
 __mark_inode_dirty+0x2ce/0xdf0 fs/fs-writeback.c:2527
 mark_inode_dirty_sync include/linux/fs.h:2550 [inline]
 dquot_free_space include/linux/quotaops.h:380 [inline]
 dquot_free_block include/linux/quotaops.h:390 [inline]
 ext4_xattr_block_set+0x148e/0x2ac0 fs/ext4/xattr.c:2073
 ext4_xattr_set_handle+0xdfb/0x1590 fs/ext4/xattr.c:2447
 ext4_initxattrs+0x9f/0x110 fs/ext4/xattr_security.c:44
 security_inode_init_security+0x29d/0x3f0 security/security.c:1852
 __ext4_new_inode+0x3257/0x3bd0 fs/ext4/ialloc.c:1326
 ext4_create+0x22d/0x460 fs/ext4/namei.c:2824
 lookup_open fs/namei.c:3701 [inline]
 open_last_lookups fs/namei.c:3800 [inline]
 path_openat+0x14f1/0x3830 fs/namei.c:4036
 do_filp_open+0x1fa/0x410 fs/namei.c:4066
 do_sys_openat2+0x121/0x1c0 fs/open.c:1429
 do_sys_open fs/open.c:1444 [inline]
 __do_sys_openat fs/open.c:1460 [inline]
 __se_sys_openat fs/open.c:1455 [inline]
 __x64_sys_openat+0x138/0x170 fs/open.c:1455
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f4148283349
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 81 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:00007f4148237168 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f414830a6a8 RCX: 00007f4148283349
RDX: 000000000000275a RSI: 0000200000000840 RDI: 00000000ffffff9c
RBP: 00007f414830a6a0 R08: 00007f41482376c0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f414830a6ac
R13: 0000000000000006 R14: 00007ffd44bf0c60 R15: 00007ffd44bf0d48
 </TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.235 msecs

Crashes (4392):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/05/12 14:42 upstream 82f2b0b97b36 77908e5f .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs INFO: task hung in path_openat
2025/02/25 22:30 upstream 2a1944bff549 d34966d1 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in path_openat
2024/12/16 16:39 upstream 78d4f34e2115 eec85da6 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in path_openat
2024/11/11 13:49 upstream 2d5404caa8c7 0c4b1325 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in path_openat
2024/10/13 19:14 upstream 36c254515dc6 084d8178 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in path_openat
2024/09/16 08:44 upstream 98f7e32f20d2 08d8a733 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in path_openat
2024/09/09 22:48 upstream da3ea35007d0 073f8be2 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in path_openat
2024/09/06 21:56 upstream b831f83e40a2 9750182a .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in path_openat
2024/10/14 08:58 upstream 6485cf5ea253 084d8178 .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 path_openat
2024/09/19 02:07 upstream 4a39ac5b7d62 c673ca06 .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 path_openat
2025/05/17 02:09 upstream 3c21441eeffc f41472b0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/14 23:07 upstream 1a80a098c606 a4fa04ef .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/14 09:57 upstream 9f35e33144ae 7344edeb .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/13 22:40 upstream e9565e23cd89 7344edeb .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/13 16:02 upstream e9565e23cd89 7344edeb .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/13 14:01 upstream e9565e23cd89 f6671af7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/13 01:05 upstream 627277ba7c23 f6671af7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/12 06:03 upstream cd802e7e5f1e 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/12 03:14 upstream cd802e7e5f1e 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/11 19:27 upstream 3ce9925823c7 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/11 12:01 upstream 3ce9925823c7 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/11 05:24 upstream bec6f00f120e 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/11 04:22 upstream bec6f00f120e 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/10 21:53 upstream bec6f00f120e 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/10 20:16 upstream bec6f00f120e 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/10 16:52 upstream 0e1329d4045c 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/10 13:44 upstream 0e1329d4045c 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/10 00:45 upstream 9c69f8884904 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/09 21:25 upstream 9c69f8884904 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/09 19:52 upstream 9c69f8884904 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/09 18:39 upstream 9c69f8884904 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/09 07:12 upstream 2c89c1b655c0 bb813bcc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/08 22:02 upstream 2c89c1b655c0 dbf35fa1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/08 16:44 upstream d76bb1ebb558 dbf35fa1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/07 22:42 upstream 707df3375124 dbf35fa1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/07 22:25 upstream 707df3375124 dbf35fa1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/07 14:28 upstream 0d8d44db295c 350f4ffc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/07 05:13 upstream 0d8d44db295c 350f4ffc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/06 21:53 upstream 0d8d44db295c 350f4ffc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/06 16:02 upstream 01f95500a162 ae98e6b9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/06 13:27 upstream 01f95500a162 ae98e6b9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/06 11:51 upstream 01f95500a162 ae98e6b9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/06 06:20 upstream 01f95500a162 ae98e6b9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/06 04:54 upstream 01f95500a162 ae98e6b9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/06 03:10 upstream 01f95500a162 ae98e6b9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/06 01:31 upstream 92a09c47464d 6ca47dd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/05 18:01 upstream 92a09c47464d 6ca47dd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/05 11:09 upstream 14c55b7bb0a8 b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/05 09:37 upstream 14c55b7bb0a8 b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/05 02:42 upstream 14c55b7bb0a8 b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/05/05 01:15 upstream 14c55b7bb0a8 b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2025/04/23 01:08 upstream bc3372351d0c 53a8b9bd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in path_openat
2025/03/19 00:09 upstream fc444ada1310 22a6c2b1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in path_openat
2024/10/07 02:00 upstream 8cf0b93919e1 d7906eff .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in path_openat
2022/10/06 05:03 upstream 2bca25eaeba6 2c6543ad .config console log report info [disk image] [vmlinux] ci2-upstream-fs INFO: task hung in path_openat
2022/10/01 15:49 upstream ffb4d94b4314 feb56351 .config console log report info [disk image] [vmlinux] ci2-upstream-fs INFO: task hung in path_openat
2022/02/14 18:00 upstream 754e0b0e3560 8b9ca619 .config console log report info ci-upstream-kasan-gce-root INFO: task hung in path_openat
2025/02/10 00:27 linux-next ed58d103e6da ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in path_openat
2025/05/17 05:17 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a82e92598ab1 f41472b0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in path_openat
2025/05/12 08:02 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci c32f8dc5aaf9 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in path_openat
2025/05/10 05:29 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci c32f8dc5aaf9 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in path_openat
* Struck through repros no longer work on HEAD.