syzbot


INFO: task hung in path_openat (7)

Status: upstream: reported on 2022/10/06 10:29
Labels: nilfs (incorrect?)
Reported-by: syzbot+950a0cdaa2fdd14f5bdc@syzkaller.appspotmail.com
First crash: 472d, last: 1d14h
Discussions (5)
Title Replies (including bot) Last reply
[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
[syzbot] INFO: task hung in path_openat (7) 0 (1) 2022/10/06 10:29
Similar bugs (14)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 INFO: task hung in path_openat 2 1357d 1390d 0/1 auto-closed as invalid on 2020/01/11 07:40
upstream INFO: task hung in path_openat (4) 1 1128d 1128d 0/24 auto-closed as invalid on 2020/07/28 10:23
upstream INFO: task hung in path_openat (3) 4 1288d 1404d 0/24 auto-closed as invalid on 2020/02/19 20:16
linux-4.19 INFO: task hung in path_openat (2) 1 558d 558d 0/1 auto-closed as invalid on 2022/03/21 04:47
linux-4.14 INFO: task hung in path_openat 1 798d 798d 0/1 auto-closed as invalid on 2021/07/23 23:26
android-49 INFO: task hung in path_openat 64 1528d 1509d 0/3 auto-closed as invalid on 2019/09/22 08:41
upstream INFO: task hung in path_openat (5) 23 769d 930d 0/24 auto-closed as invalid on 2021/07/22 20:44
linux-4.19 INFO: task hung in path_openat (3) f2fs jfs 20 135d 294d 0/1 upstream: reported on 2022/08/11 13:14
upstream INFO: task hung in path_openat (6) 13 504d 654d 0/24 closed as invalid on 2022/02/07 19:19
android-414 INFO: task hung in path_openat 42 1432d 1511d 0/1 auto-closed as invalid on 2019/10/28 21:04
linux-6.1 INFO: task hung in path_openat 2 38d 58d 0/3 upstream: reported on 2023/04/04 07:33
upstream INFO: task hung in path_openat 246 1596d 1886d 0/24 closed as dup on 2018/09/08 15:37
linux-5.15 INFO: task hung in path_openat 2 35d 51d 0/3 upstream: reported on 2023/04/12 01:28
upstream INFO: task hung in path_openat (2) 1 1499d 1499d 0/24 closed as invalid on 2019/05/08 13:05

Sample crash report:
INFO: task syz-executor.2:28565 blocked for more than 143 seconds.
      Not tainted 6.4.0-rc4-syzkaller-00047-gafead42fdfca #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.2  state:D stack:27928 pid:28565 ppid:5021   flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5343 [inline]
 __schedule+0x187b/0x4900 kernel/sched/core.c:6669
 schedule+0xc3/0x180 kernel/sched/core.c:6745
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6804
 rwsem_down_write_slowpath+0xedd/0x13a0 kernel/locking/rwsem.c:1178
 __down_write_common+0x1aa/0x200 kernel/locking/rwsem.c:1306
 inode_lock include/linux/fs.h:775 [inline]
 open_last_lookups fs/namei.c:3557 [inline]
 path_openat+0x7ba/0x3170 fs/namei.c:3788
 do_filp_open+0x234/0x490 fs/namei.c:3818
 do_sys_openat2+0x13f/0x500 fs/open.c:1356
 do_sys_open fs/open.c:1372 [inline]
 __do_sys_openat fs/open.c:1388 [inline]
 __se_sys_openat fs/open.c:1383 [inline]
 __x64_sys_openat+0x247/0x290 fs/open.c:1383
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fbfb3a8c169
RSP: 002b:00007fbfb47cc168 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007fbfb3bac050 RCX: 00007fbfb3a8c169
RDX: 000000000000275a RSI: 0000000020006ac0 RDI: ffffffffffffff9c
RBP: 00007fbfb3ae7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc1d0dc15f R14: 00007fbfb47cc300 R15: 0000000000022000
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/13:
 #0: ffffffff8cf276f0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:518
1 lock held by rcu_tasks_trace/14:
 #0: ffffffff8cf27ab0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:518
1 lock held by khungtaskd/28:
 #0: ffffffff8cf27520 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by kworker/u4:5/1013:
 #0: ffff888012479138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x77e/0x10e0 kernel/workqueue.c:2378
 #1: ffffc9000478fd20 (connector_reaper_work){+.+.}-{0:0}, at: process_one_work+0x7c8/0x10e0 kernel/workqueue.c:2380
2 locks held by kworker/1:2/2122:
2 locks held by getty/4750:
 #0: ffff88814b525098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc900015a02f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6ab/0x1db0 drivers/tty/n_tty.c:2176
1 lock held by syz-executor.1/5020:
 #0: ffffffff8cf2cbf8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:325 [inline]
 #0: ffffffff8cf2cbf8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x46c/0x890 kernel/rcu/tree_exp.h:992
1 lock held by syz-executor.0/5041:
 #0: ffffffff8cf2cbf8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:293 [inline]
 #0: ffffffff8cf2cbf8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3a3/0x890 kernel/rcu/tree_exp.h:992
2 locks held by kworker/1:8/5083:
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x77e/0x10e0 kernel/workqueue.c:2378
 #1: ffffc900046afd20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7c8/0x10e0 kernel/workqueue.c:2380
2 locks held by kworker/0:7/5111:
 #0: ffff888012472538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x77e/0x10e0 kernel/workqueue.c:2378
 #1: ffffc900047afd20 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7c8/0x10e0 kernel/workqueue.c:2380
2 locks held by kworker/1:13/5585:
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x77e/0x10e0 kernel/workqueue.c:2378
 #1: ffffc9000ac9fd20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7c8/0x10e0 kernel/workqueue.c:2380
2 locks held by kworker/1:16/5968:
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x77e/0x10e0 kernel/workqueue.c:2378
 #1: ffffc90016897d20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7c8/0x10e0 kernel/workqueue.c:2380
2 locks held by kworker/1:17/6348:
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x77e/0x10e0 kernel/workqueue.c:2378
 #1: ffffc900051bfd20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7c8/0x10e0 kernel/workqueue.c:2380
2 locks held by kworker/1:19/6350:
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x77e/0x10e0 kernel/workqueue.c:2378
 #1: ffffc90005a97d20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7c8/0x10e0 kernel/workqueue.c:2380
2 locks held by kworker/1:20/6351:
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x77e/0x10e0 kernel/workqueue.c:2378
 #1: ffffc90005aa7d20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7c8/0x10e0 kernel/workqueue.c:2380
2 locks held by kworker/1:22/6353:
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x77e/0x10e0 kernel/workqueue.c:2378
 #1: ffffc90005ac7d20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7c8/0x10e0 kernel/workqueue.c:2380
2 locks held by kworker/1:23/6356:
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x77e/0x10e0 kernel/workqueue.c:2378
 #1: ffffc90005af7d20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7c8/0x10e0 kernel/workqueue.c:2380
2 locks held by kworker/1:24/6360:
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x77e/0x10e0 kernel/workqueue.c:2378
 #1: ffffc90005b37d20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7c8/0x10e0 kernel/workqueue.c:2380
2 locks held by kworker/1:26/6362:
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x77e/0x10e0 kernel/workqueue.c:2378
 #1: ffffc90005b57d20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7c8/0x10e0 kernel/workqueue.c:2380
2 locks held by kworker/1:27/6366:
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x77e/0x10e0 kernel/workqueue.c:2378
 #1: ffffc90005b97d20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7c8/0x10e0 kernel/workqueue.c:2380
2 locks held by syz-executor.2/28559:
2 locks held by syz-executor.2/28565:
 #0: ffff888025fc6460 (sb_writers#18){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:394
 #1: ffff8880389ca6c0 (&type->i_mutex_dir_key#11){++++}-{3:3}, at: inode_lock include/linux/fs.h:775 [inline]
 #1: ffff8880389ca6c0 (&type->i_mutex_dir_key#11){++++}-{3:3}, at: open_last_lookups fs/namei.c:3557 [inline]
 #1: ffff8880389ca6c0 (&type->i_mutex_dir_key#11){++++}-{3:3}, at: path_openat+0x7ba/0x3170 fs/namei.c:3788
1 lock held by syz-executor.2/31219:

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

NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 6.4.0-rc4-syzkaller-00047-gafead42fdfca #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x498/0x4d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x187/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
 watchdog+0xec2/0xf00 kernel/hung_task.c:379
 kthread+0x2b8/0x350 kernel/kthread.c:379
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4434 Comm: klogd Not tainted 6.4.0-rc4-syzkaller-00047-gafead42fdfca #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
RIP: 0010:mark_lock+0x9/0x340 kernel/locking/lockdep.c:4617
Code: 8c 73 ff ff ff 4c 89 ff e8 b4 cf 77 00 e9 66 ff ff ff e8 2a ac 43 09 66 2e 0f 1f 84 00 00 00 00 00 55 41 57 41 56 41 55 41 54 <53> 48 83 ec 10 49 89 f7 48 89 3c 24 49 bd 00 00 00 00 00 fc ff df
RSP: 0018:ffffc9000313f970 EFLAGS: 00000002
RAX: 0000000000040502 RBX: ffff88807eb44648 RCX: ffffffff91b20103
RDX: 0000000000000002 RSI: ffff88807eb44648 RDI: ffff88807eb43b80
RBP: ffffc9000313fa48 R08: dffffc0000000000 R09: fffffbfff1cab90e
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88807eb44668
R13: 0000000000000000 R14: ffff88807eb44640 R15: 1ffff1100fd688c8
FS:  00007f98653a6380(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020006ac5 CR3: 000000002c71e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 mark_held_locks kernel/locking/lockdep.c:4252 [inline]
 __trace_hardirqs_on_caller kernel/locking/lockdep.c:4270 [inline]
 lockdep_hardirqs_on_prepare+0x281/0x7a0 kernel/locking/lockdep.c:4337
 trace_hardirqs_on+0x28/0x40 kernel/trace/trace_preemptirq.c:61
 __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]
 _raw_spin_unlock_irqrestore+0x8f/0x140 kernel/locking/spinlock.c:194
 unix_dgram_sendmsg+0x1502/0x2050 net/unix/af_unix.c:2082
 sock_sendmsg_nosec net/socket.c:724 [inline]
 sock_sendmsg net/socket.c:747 [inline]
 __sys_sendto+0x475/0x630 net/socket.c:2144
 __do_sys_sendto net/socket.c:2156 [inline]
 __se_sys_sendto net/socket.c:2152 [inline]
 __x64_sys_sendto+0xde/0xf0 net/socket.c:2152
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f98655089b5
Code: 8b 44 24 08 48 83 c4 28 48 98 c3 48 98 c3 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 26 45 31 c9 45 31 c0 b8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff 76 7a 48 8b 15 44 c4 0c 00 f7 d8 64 89 02 48 83
RSP: 002b:00007ffd730fd108 EFLAGS: 00000246 ORIG_RAX: 000000000000002c
RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007f98655089b5
RDX: 0000000000000046 RSI: 00005580996a81d0 RDI: 0000000000000003
RBP: 00005580996a0910 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000004000 R11: 0000000000000246 R12: 0000000000000013
R13: 00007f9865696212 R14: 00007ffd730fd208 R15: 0000000000000000
 </TASK>

Crashes (204):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets Manager Title
2023/05/31 13:50 upstream afead42fdfca 09898419 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/05/22 19:27 upstream 44c026a73be8 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/05/18 22:54 upstream 4d6d4c7f541d 3bb7af1d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/05/14 09:38 upstream d4d58949a6ea 2b9ba477 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/05/08 08:11 upstream 17784de648be 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/05/07 22:56 upstream 17784de648be 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/05/05 11:38 upstream 3c4aa4434377 518a39a6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in path_openat
2023/05/01 18:03 upstream 58390c8ce1bd 62df2017 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/04/30 13:48 upstream 825a0714d2b3 62df2017 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/04/26 08:55 upstream 0cfd8703e7da 65320f8e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/04/25 10:06 upstream 1a0beef98b58 65320f8e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/04/24 11:37 upstream 457391b03803 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/04/22 23:23 upstream 2caeeb9d4a1b 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/04/22 13:47 upstream 8e41e0a57566 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/04/21 22:49 upstream 2af3e53a4dc0 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/04/21 05:53 upstream 6a66fdd29ea1 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/04/20 15:03 upstream cb0856346a60 a219f34e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/04/17 18:57 upstream 6a8f57ae2eb0 c6ec7083 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/04/15 14:03 upstream 7a934f4bd7d6 ec410564 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/04/14 12:16 upstream 44149752e998 3cfcaa1b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/04/13 07:53 upstream 0bcc40255504 82d5e53e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/04/12 06:42 upstream e62252bc55b6 49faf98d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/04/08 19:10 upstream aa318c48808c 71147e29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/04/08 14:40 upstream aa318c48808c 71147e29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/04/06 17:25 upstream 99ddf2254feb 08707520 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in path_openat
2023/04/06 16:16 upstream 99ddf2254feb 08707520 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/04/06 15:08 upstream 99ddf2254feb 08707520 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/04/04 18:36 upstream 148341f0a2f5 928dd177 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in path_openat
2023/04/02 09:54 upstream 00c7b5f4ddc5 f325deb0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/04/01 00:19 upstream 5a57b48fdfcb f325deb0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/03/29 14:12 upstream fcd476ea6a88 f325deb0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/03/27 04:50 upstream 18940c888c85 fbf0499a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/03/25 19:40 upstream 65aca32efdcb fbf0499a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/03/24 07:54 upstream 9fd6ba5420ba f94b4a29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/03/21 11:30 upstream 17214b70a159 7939252e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/03/21 06:41 upstream 7d31677bb7b1 7939252e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/03/18 05:03 upstream 38e04b3e4240 7939252e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/03/16 16:38 upstream 9c1bec9c0b08 18b58603 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in path_openat
2023/03/15 12:42 upstream 6015b1aca1a2 18b58603 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/03/14 04:43 upstream fc89d7fb499b 026e2200 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in path_openat
2023/03/13 07:38 upstream eeac8ede1755 5205ef30 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/03/05 13:47 upstream b01fe98d34f3 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/03/05 03:40 upstream b01fe98d34f3 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/03/02 17:07 upstream ee3f96b16468 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in path_openat
2023/01/19 19:28 upstream 7287904c8771 1b826a2f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-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
2023/04/22 05:55 linux-next d3e1ee0e67e7 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in path_openat
2023/04/08 22:02 linux-next e134c93f788f 71147e29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in path_openat
2023/04/24 04:18 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 14f8db1c0f9a 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in path_openat
2023/04/05 03:35 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 59caa87f9dfb 831373d3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in path_openat
2023/03/10 22:06 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci fe15c26ee26e 5205ef30 .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.