syzbot


INFO: task hung in filename_create (4)

Status: upstream: reported C repro on 2021/12/21 22:55
Labels: fs (incorrect?)
Reported-by: syzbot+72c5cf124089bc318016@syzkaller.appspotmail.com
First crash: 558d, last: 9d23h

Cause bisection: failed (error log, bisect log)

Fix bisection: failed (error log, bisect log)
Discussions (2)
Title Replies (including bot) Last reply
[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 (11)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 INFO: task hung in filename_create 6 1288d 1387d 0/1 auto-closed as invalid on 2020/03/17 23:03
upstream INFO: task hung in filename_create (2) 11 1271d 1376d 0/24 auto-closed as invalid on 2020/03/04 11:54
android-49 INFO: task hung in filename_create C 44 1737d 1508d 0/3 public: reported C repro on 2019/04/13 00:00
upstream INFO: task hung in filename_create (3) 16 737d 893d 0/24 auto-closed as invalid on 2021/08/20 18:08
linux-4.19 INFO: task hung in filename_create (3) 3 565d 627d 0/1 auto-closed as invalid on 2022/03/11 04:15
android-44 INFO: task hung in filename_create 1 1870d 1870d 0/2 auto-closed as invalid on 2019/02/22 14:19
linux-4.19 INFO: task hung in filename_create (2) 1 828d 828d 0/1 auto-closed as invalid on 2021/06/20 16:38
linux-4.14 INFO: task hung in filename_create 2 1261d 1265d 0/1 auto-closed as invalid on 2020/04/14 04:42
linux-4.19 INFO: task hung in filename_create (4) 2 198d 261d 0/1 auto-obsoleted due to no activity on 2023/03/13 04:19
android-44 INFO: task hung in filename_create (2) 1 1491d 1491d 0/2 auto-closed as invalid on 2019/10/25 08:49
upstream INFO: task hung in filename_create 121 1581d 1866d 0/24 closed as dup on 2018/09/08 15:39

Sample crash report:
INFO: task syz-executor149:3707 blocked for more than 143 seconds.
      Not tainted 5.16.0-rc5-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor149 state:D stack:23928 pid: 3707 ppid:  3685 flags:0x00000000
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:4972 [inline]
 context_switch kernel/sched/core.c:4972 [inline] kernel/sched/core.c:6253
 __schedule+0xa9a/0x4940 kernel/sched/core.c:6253 kernel/sched/core.c:6253
 schedule+0xd2/0x260 kernel/sched/core.c:6326 kernel/sched/core.c:6326
 rwsem_down_write_slowpath+0x634/0x1110 kernel/locking/rwsem.c:1151 kernel/locking/rwsem.c:1151
 __down_write_common kernel/locking/rwsem.c:1268 [inline]
 __down_write_common kernel/locking/rwsem.c:1265 [inline]
 __down_write kernel/locking/rwsem.c:1277 [inline]
 __down_write_common kernel/locking/rwsem.c:1268 [inline] kernel/locking/rwsem.c:1634
 __down_write_common kernel/locking/rwsem.c:1265 [inline] kernel/locking/rwsem.c:1634
 __down_write kernel/locking/rwsem.c:1277 [inline] kernel/locking/rwsem.c:1634
 down_write_nested+0x139/0x150 kernel/locking/rwsem.c:1634 kernel/locking/rwsem.c:1634
 inode_lock_nested include/linux/fs.h:818 [inline]
 inode_lock_nested include/linux/fs.h:818 [inline] fs/namei.c:3654
 filename_create+0x158/0x480 fs/namei.c:3654 fs/namei.c:3654
 do_mkdirat+0x94/0x300 fs/namei.c:3898 fs/namei.c:3898
 __do_sys_mkdir fs/namei.c:3929 [inline]
 __se_sys_mkdir fs/namei.c:3927 [inline]
 __do_sys_mkdir fs/namei.c:3929 [inline] fs/namei.c:3927
 __se_sys_mkdir fs/namei.c:3927 [inline] fs/namei.c:3927
 __x64_sys_mkdir+0xf2/0x140 fs/namei.c:3927 fs/namei.c:3927
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_x64 arch/x86/entry/common.c:50 [inline] arch/x86/entry/common.c:80
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x7f8e02ef3b47
RSP: 002b:00007f8e03098ca8 EFLAGS: 00000202 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f8e02ef3b47
RDX: 00007f8e03098cf3 RSI: 00000000000001ff RDI: 00007f8e03098ce0
RBP: 00007f8e03098ee0 R08: 0000000000000000 R09: 00007f8e03098b40
R10: 00007f8e030989f7 R11: 0000000000000202 R12: 0000000000000001
R13: 00007f8e03098ce0 R14: 00007f8e03098d20 R15: 00007f8e03098ef0
 </TASK>
INFO: task syz-executor149:3711 blocked for more than 143 seconds.
      Not tainted 5.16.0-rc5-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor149 state:D stack:23928 pid: 3711 ppid:  3681 flags:0x00000000
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:4972 [inline]
 context_switch kernel/sched/core.c:4972 [inline] kernel/sched/core.c:6253
 __schedule+0xa9a/0x4940 kernel/sched/core.c:6253 kernel/sched/core.c:6253
 schedule+0xd2/0x260 kernel/sched/core.c:6326 kernel/sched/core.c:6326
 rwsem_down_write_slowpath+0x634/0x1110 kernel/locking/rwsem.c:1151 kernel/locking/rwsem.c:1151
 __down_write_common kernel/locking/rwsem.c:1268 [inline]
 __down_write_common kernel/locking/rwsem.c:1265 [inline]
 __down_write kernel/locking/rwsem.c:1277 [inline]
 __down_write_common kernel/locking/rwsem.c:1268 [inline] kernel/locking/rwsem.c:1634
 __down_write_common kernel/locking/rwsem.c:1265 [inline] kernel/locking/rwsem.c:1634
 __down_write kernel/locking/rwsem.c:1277 [inline] kernel/locking/rwsem.c:1634
 down_write_nested+0x139/0x150 kernel/locking/rwsem.c:1634 kernel/locking/rwsem.c:1634
 inode_lock_nested include/linux/fs.h:818 [inline]
 inode_lock_nested include/linux/fs.h:818 [inline] fs/namei.c:3654
 filename_create+0x158/0x480 fs/namei.c:3654 fs/namei.c:3654
 do_mkdirat+0x94/0x300 fs/namei.c:3898 fs/namei.c:3898
 __do_sys_mkdir fs/namei.c:3929 [inline]
 __se_sys_mkdir fs/namei.c:3927 [inline]
 __do_sys_mkdir fs/namei.c:3929 [inline] fs/namei.c:3927
 __se_sys_mkdir fs/namei.c:3927 [inline] fs/namei.c:3927
 __x64_sys_mkdir+0xf2/0x140 fs/namei.c:3927 fs/namei.c:3927
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_x64 arch/x86/entry/common.c:50 [inline] arch/x86/entry/common.c:80
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x7f8e02ef3b47
RSP: 002b:00007f8e03098ca8 EFLAGS: 00000202 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f8e02ef3b47
RDX: 00007f8e03098cf3 RSI: 00000000000001ff RDI: 00007f8e03098ce0
RBP: 00007f8e03098ee0 R08: 0000000000000000 R09: 00007f8e03098b40
R10: 00007f8e030989f7 R11: 0000000000000202 R12: 0000000000000001
R13: 00007f8e03098ce0 R14: 00007f8e03098d20 R15: 00007f8e03098ef0
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/26:
 #0: ffffffff8bb83de0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x53/0x260 kernel/locking/lockdep.c:6458 kernel/locking/lockdep.c:6458
2 locks held by kworker/u4:4/995:
 #0: ffff8880b9c39a98 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2b/0x120 kernel/sched/core.c:478 kernel/sched/core.c:478
 #1: ffff8880b9c279c8 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x3a6/0x490 kernel/sched/psi.c:880 kernel/sched/psi.c:880
2 locks held by kworker/1:3/3266:
 #0: ffff888010c66538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
 #0: ffff888010c66538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: arch_atomic_long_set include/linux/atomic/atomic-long.h:41 [inline]
 #0: ffff888010c66538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:1198 [inline]
 #0: ffff888010c66538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:635 [inline]
 #0: ffff888010c66538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:662 [inline]
 #0: ffff888010c66538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline] kernel/workqueue.c:2269
 #0: ffff888010c66538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: arch_atomic_long_set include/linux/atomic/atomic-long.h:41 [inline] kernel/workqueue.c:2269
 #0: ffff888010c66538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:1198 [inline] kernel/workqueue.c:2269
 #0: ffff888010c66538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:635 [inline] kernel/workqueue.c:2269
 #0: ffff888010c66538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:662 [inline] kernel/workqueue.c:2269
 #0: ffff888010c66538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x896/0x1690 kernel/workqueue.c:2269 kernel/workqueue.c:2269
 #1: ffffc90001a6fdb0 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x8ca/0x1690 kernel/workqueue.c:2273 kernel/workqueue.c:2273
2 locks held by getty/3279:
 #0: ffff8880231c5098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:252 drivers/tty/tty_ldisc.c:252
 #1: ffffc90002b962e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0xcf0/0x1230 drivers/tty/n_tty.c:2113 drivers/tty/n_tty.c:2113
1 lock held by syz-executor149/3706:
 #0: ffffffff8bb8d168 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
 #0: ffffffff8bb8d168 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline] kernel/rcu/tree_exp.h:836
 #0: ffffffff8bb8d168 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x2d5/0x620 kernel/rcu/tree_exp.h:836 kernel/rcu/tree_exp.h:836
2 locks held by syz-executor149/3707:
 #0: ffff88801f07a460 (sb_writers#11){.+.+}-{0:0}, at: filename_create+0xf3/0x480 fs/namei.c:3649 fs/namei.c:3649
 #1: ffff88807533e9d0 (&type->i_mutex_dir_key#7/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:818 [inline]
 #1: ffff88807533e9d0 (&type->i_mutex_dir_key#7/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:818 [inline] fs/namei.c:3654
 #1: ffff88807533e9d0 (&type->i_mutex_dir_key#7/1){+.+.}-{3:3}, at: filename_create+0x158/0x480 fs/namei.c:3654 fs/namei.c:3654
1 lock held by syz-executor149/3708:
 #0: ffffffff8bb8d168 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
 #0: ffffffff8bb8d168 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline] kernel/rcu/tree_exp.h:836
 #0: ffffffff8bb8d168 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x2d5/0x620 kernel/rcu/tree_exp.h:836 kernel/rcu/tree_exp.h:836
2 locks held by syz-executor149/3709:
 #0: ffff88801f07a460 (sb_writers#11){.+.+}-{0:0}, at: filename_create+0xf3/0x480 fs/namei.c:3649 fs/namei.c:3649
 #1: ffff88807533e9d0 (&type->i_mutex_dir_key#7/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:818 [inline]
 #1: ffff88807533e9d0 (&type->i_mutex_dir_key#7/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:818 [inline] fs/namei.c:3654
 #1: ffff88807533e9d0 (&type->i_mutex_dir_key#7/1){+.+.}-{3:3}, at: filename_create+0x158/0x480 fs/namei.c:3654 fs/namei.c:3654
2 locks held by syz-executor149/3711:
 #0: ffff88801f07a460 (sb_writers#11){.+.+}-{0:0}, at: filename_create+0xf3/0x480 fs/namei.c:3649 fs/namei.c:3649
 #1: ffff88807533e9d0 (&type->i_mutex_dir_key#7/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:818 [inline]
 #1: ffff88807533e9d0 (&type->i_mutex_dir_key#7/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:818 [inline] fs/namei.c:3654
 #1: ffff88807533e9d0 (&type->i_mutex_dir_key#7/1){+.+.}-{3:3}, at: filename_create+0x158/0x480 fs/namei.c:3654 fs/namei.c:3654

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

NMI backtrace for cpu 0
CPU: 0 PID: 26 Comm: khungtaskd Not tainted 5.16.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 __dump_stack lib/dump_stack.c:88 [inline] lib/dump_stack.c:106
 dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 lib/dump_stack.c:106
 nmi_cpu_backtrace.cold+0x47/0x144 lib/nmi_backtrace.c:111 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x1b3/0x230 lib/nmi_backtrace.c:62 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:146 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
 trigger_all_cpu_backtrace include/linux/nmi.h:146 [inline] kernel/hung_task.c:295
 check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline] kernel/hung_task.c:295
 watchdog+0xc1d/0xf50 kernel/hung_task.c:295 kernel/hung_task.c:295
 kthread+0x405/0x4f0 kernel/kthread.c:327 kernel/kthread.c:327
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295 arch/x86/entry/entry_64.S:295
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 8 Comm: kworker/u4:0 Not tainted 5.16.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: bat_events batadv_nc_worker
RIP: 0010:validate_chain kernel/locking/lockdep.c:3808 [inline]
RIP: 0010:validate_chain kernel/locking/lockdep.c:3808 [inline] kernel/locking/lockdep.c:5027
RIP: 0010:__lock_acquire+0xcaa/0x54a0 kernel/locking/lockdep.c:5027 kernel/locking/lockdep.c:5027
Code: ff df 0f b6 04 02 49 89 cf 84 c0 74 08 3c 03 0f 8e 2b 34 00 00 41 8b 44 24 20 25 00 80 04 00 3d 00 00 04 00 0f 84 5e 09 00 00 <48> c7 c2 8c 6a 91 8d 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 0f
RSP: 0018:ffffc90000cd7a60 EFLAGS: 00000087
RAX: 0000000000000000 RBX: 00000000a623e6fc RCX: eeae28e815dd6c6b
RDX: 1ffff110021cec3a RSI: 000000004cd55dcb RDI: ffffffff8ff76c60
RBP: 0000000000000004 R08: 0000000000000000 R09: ffffffff8ff74a07
R10: fffffbfff1fee940 R11: 0000000000000000 R12: ffff888010e761b0
R13: ffff888010e75700 R14: 0000000000000000 R15: eeae28e815dd6c6b
FS:  0000000000000000(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555555840848 CR3: 000000000b88e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 lock_acquire kernel/locking/lockdep.c:5637 [inline]
 lock_acquire kernel/locking/lockdep.c:5637 [inline] kernel/locking/lockdep.c:5602
 lock_acquire+0x1ab/0x510 kernel/locking/lockdep.c:5602 kernel/locking/lockdep.c:5602
 rcu_lock_acquire include/linux/rcupdate.h:268 [inline]
 rcu_read_lock include/linux/rcupdate.h:688 [inline]
 batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:412 [inline]
 rcu_lock_acquire include/linux/rcupdate.h:268 [inline] net/batman-adv/network-coding.c:723
 rcu_read_lock include/linux/rcupdate.h:688 [inline] net/batman-adv/network-coding.c:723
 batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:412 [inline] net/batman-adv/network-coding.c:723
 batadv_nc_worker+0x12d/0xfa0 net/batman-adv/network-coding.c:723 net/batman-adv/network-coding.c:723
 process_one_work+0x9b2/0x1690 kernel/workqueue.c:2298 kernel/workqueue.c:2298
 worker_thread+0x658/0x11f0 kernel/workqueue.c:2445 kernel/workqueue.c:2445
 kthread+0x405/0x4f0 kernel/kthread.c:327 kernel/kthread.c:327
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295 arch/x86/entry/entry_64.S:295
 </TASK>
----------------
Code disassembly (best guess), 1 bytes skipped:
   0:	df 0f                	fisttps (%rdi)
   2:	b6 04                	mov    $0x4,%dh
   4:	02 49 89             	add    -0x77(%rcx),%cl
   7:	cf                   	iret
   8:	84 c0                	test   %al,%al
   a:	74 08                	je     0x14
   c:	3c 03                	cmp    $0x3,%al
   e:	0f 8e 2b 34 00 00    	jle    0x343f
  14:	41 8b 44 24 20       	mov    0x20(%r12),%eax
  19:	25 00 80 04 00       	and    $0x48000,%eax
  1e:	3d 00 00 04 00       	cmp    $0x40000,%eax
  23:	0f 84 5e 09 00 00    	je     0x987
* 29:	48 c7 c2 8c 6a 91 8d 	mov    $0xffffffff8d916a8c,%rdx <-- trapping instruction
  30:	48 b8 00 00 00 00 00 	movabs $0xdffffc0000000000,%rax
  37:	fc ff df
  3a:	48 c1 ea 03          	shr    $0x3,%rdx
  3e:	0f                   	.byte 0xf
----------------
Code disassembly (best guess), 1 bytes skipped:
   0:	df 0f                	fisttps (%rdi)
   2:	b6 04                	mov    $0x4,%dh
   4:	02 49 89             	add    -0x77(%rcx),%cl
   7:	cf                   	iret
   8:	84 c0                	test   %al,%al
   a:	74 08                	je     0x14
   c:	3c 03                	cmp    $0x3,%al
   e:	0f 8e 2b 34 00 00    	jle    0x343f
  14:	41 8b 44 24 20       	mov    0x20(%r12),%eax
  19:	25 00 80 04 00       	and    $0x48000,%eax
  1e:	3d 00 00 04 00       	cmp    $0x40000,%eax
  23:	0f 84 5e 09 00 00    	je     0x987
* 29:	48 c7 c2 8c 6a 91 8d 	mov    $0xffffffff8d916a8c,%rdx <-- trapping instruction
  30:	48 b8 00 00 00 00 00 	movabs $0xdffffc0000000000,%rax
  37:	fc ff df
  3a:	48 c1 ea 03          	shr    $0x3,%rdx
  3e:	0f                   	.byte 0xf

Crashes (38):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets Manager Title
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
2023/05/20 07:10 upstream cbd6ac3837cd 96689200 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2023/04/26 11:28 upstream 0cfd8703e7da 8d843721 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2023/04/24 02:40 upstream 457391b03803 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2023/04/21 19:56 upstream 2af3e53a4dc0 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2023/04/04 20:47 upstream 148341f0a2f5 928dd177 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2023/03/20 12:40 upstream e8d018dd0257 7939252e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2023/03/14 06:15 upstream fc89d7fb499b 026e2200 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2023/03/03 13:16 upstream 2eb29d59ddf0 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2023/02/26 20:01 upstream 2fcd07b7ccd5 ee50e71c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2023/02/20 05:04 upstream c9c3395d5e3d bcdf85f8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2023/01/11 19:18 upstream 7dd4b804e080 96166539 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2023/01/02 07:21 upstream 150aae354b81 ab32d508 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in filename_create
2022/12/14 08:12 upstream 02bf43c7b7f7 f6511626 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2022/12/10 20:44 upstream 3ecc37918c80 67be1ae7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2022/12/03 08:40 upstream 97ee9d1c1696 e080de16 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2022/11/10 10:17 upstream f67dd6ce0723 b2488a87 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2022/11/01 00:12 upstream b229b6ca5abb 2a71366b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2022/10/30 09:14 upstream b229b6ca5abb 2a71366b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in filename_create
2022/10/23 06:56 upstream 4da34b7d175d c0b80a55 .config console log report info [disk image] [vmlinux] ci2-upstream-fs INFO: task hung in filename_create
2022/10/17 18:52 upstream 493ffd6605b2 94744d21 .config console log report info [disk image] [vmlinux] ci2-upstream-fs INFO: task hung in filename_create
2022/10/04 11:48 upstream 4fe89d07dcc2 978d1f19 .config console log report info [disk image] [vmlinux] ci2-upstream-fs INFO: task hung in filename_create
2022/09/20 00:09 upstream 521a547ced64 dd9a85ff .config console log report info ci-upstream-kasan-gce-selinux-root INFO: task hung in filename_create
2022/07/30 14:14 upstream e65c6a46df94 fef302b1 .config console log report info ci-upstream-kasan-gce-selinux-root INFO: task hung in filename_create
2022/07/26 14:18 upstream e0dccc3b76fb 34795c51 .config console log report info ci-upstream-kasan-gce-smack-root INFO: task hung in filename_create
2022/03/08 13:36 upstream ea4424be1688 7bdd8b2c .config console log report info ci-upstream-kasan-gce-selinux-root INFO: task hung in filename_create
2022/02/17 05:04 upstream 359303076163 2bea8a27 .config console log report info ci-upstream-kasan-gce-root INFO: task hung in filename_create
2022/02/16 06:30 upstream 705d84a366cf 8b9ca619 .config console log report info ci-upstream-kasan-gce-smack-root INFO: task hung in filename_create
2022/02/16 05:45 upstream 705d84a366cf 8b9ca619 .config console log report info ci-upstream-kasan-gce-selinux-root INFO: task hung in filename_create
2022/02/16 04:20 upstream 705d84a366cf 8b9ca619 .config console log report info ci-upstream-kasan-gce-root INFO: task hung in filename_create
2022/01/15 00:39 upstream fb3b0673b7d5 53e00b45 .config console log report info 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
2022/08/05 11:28 linux-next cb71b93c2dc3 1c9013ac .config console log report info ci-upstream-linux-next-kasan-gce-root INFO: task hung in filename_create
2022/08/01 12:44 linux-next cb71b93c2dc3 fef302b1 .config console log report info ci-upstream-linux-next-kasan-gce-root INFO: task hung in filename_create
2022/07/31 17:53 linux-next cb71b93c2dc3 fef302b1 .config console log report info ci-upstream-linux-next-kasan-gce-root INFO: task hung in filename_create
2022/11/05 17:30 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci bbed346d5a96 6d752409 .config console log report info [disk image] [vmlinux] ci-upstream-gce-arm64 INFO: task hung in filename_create
2022/10/18 13:39 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci bbed346d5a96 754863b4 .config console log report info [disk image] [vmlinux] ci-upstream-gce-arm64 INFO: task hung in filename_create
* Struck through repros no longer work on HEAD.