syzbot


INFO: task hung in filename_create

Status: upstream: reported on 2024/04/15 05:31
Reported-by: syzbot+bf2e1952f5c999646687@syzkaller.appspotmail.com
First crash: 15d, last: 5d03h
Similar bugs (13)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 INFO: task hung in filename_create 6 1625d 1724d 0/1 auto-closed as invalid on 2020/03/17 23:03
upstream INFO: task hung in filename_create (2) fs 11 1608d 1713d 0/26 auto-closed as invalid on 2020/03/04 11:54
android-49 INFO: task hung in filename_create C 44 2074d 1845d 0/3 public: reported C repro on 2019/04/13 00:00
upstream INFO: task hung in filename_create (3) fs 16 1074d 1230d 0/26 auto-closed as invalid on 2021/08/20 18:08
linux-4.19 INFO: task hung in filename_create (3) 3 901d 964d 0/1 auto-closed as invalid on 2022/03/11 04:15
android-44 INFO: task hung in filename_create 1 2207d 2207d 0/2 auto-closed as invalid on 2019/02/22 14:19
linux-4.19 INFO: task hung in filename_create (2) 1 1165d 1165d 0/1 auto-closed as invalid on 2021/06/20 16:38
linux-4.14 INFO: task hung in filename_create 2 1597d 1601d 0/1 auto-closed as invalid on 2020/04/14 04:42
linux-4.19 INFO: task hung in filename_create (4) 2 534d 598d 0/1 auto-obsoleted due to no activity on 2023/03/13 04:19
android-44 INFO: task hung in filename_create (2) 1 1828d 1828d 0/2 auto-closed as invalid on 2019/10/25 08:49
upstream INFO: task hung in filename_create (4) fs C error error 450 6h03m 861d 0/26 upstream: reported C repro on 2021/12/21 22:55
linux-6.1 INFO: task hung in filename_create 3 8d18h 11d 0/3 upstream: reported on 2024/04/19 18:22
upstream INFO: task hung in filename_create fs 121 1918d 2203d 0/26 closed as dup on 2018/09/08 15:39

Sample crash report:
INFO: task syz-executor.4:5333 blocked for more than 143 seconds.
      Not tainted 5.15.156-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4  state:D stack:25368 pid: 5333 ppid:  3519 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5030 [inline]
 __schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
 schedule+0x11b/0x1f0 kernel/sched/core.c:6459
 rwsem_down_write_slowpath+0xf0c/0x16a0 kernel/locking/rwsem.c:1165
 inode_lock_nested include/linux/fs.h:824 [inline]
 filename_create+0x25c/0x530 fs/namei.c:3835
 do_mkdirat+0xb3/0x520 fs/namei.c:4080
 __do_sys_mkdirat fs/namei.c:4105 [inline]
 __se_sys_mkdirat fs/namei.c:4103 [inline]
 __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4103
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f32cfb9d9a7
RSP: 002b:00007f32ce110ef8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007f32ce110f80 RCX: 00007f32cfb9d9a7
RDX: 00000000000001ff RSI: 0000000020000100 RDI: 00000000ffffff9c
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000020000100
R13: 00007f32ce110f40 R14: 0000000000000000 R15: 0000000000000000
 </TASK>
INFO: task syz-executor.4:5335 blocked for more than 143 seconds.
      Not tainted 5.15.156-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4  state:D stack:25440 pid: 5335 ppid:  3519 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5030 [inline]
 __schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
 schedule+0x11b/0x1f0 kernel/sched/core.c:6459
 rwsem_down_write_slowpath+0xf0c/0x16a0 kernel/locking/rwsem.c:1165
 inode_lock_nested include/linux/fs.h:824 [inline]
 filename_create+0x25c/0x530 fs/namei.c:3835
 do_mkdirat+0xb3/0x520 fs/namei.c:4080
 __do_sys_mkdirat fs/namei.c:4105 [inline]
 __se_sys_mkdirat fs/namei.c:4103 [inline]
 __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4103
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f32cfb9eea9
RSP: 002b:00007f32ce0f00c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007f32cfccd050 RCX: 00007f32cfb9eea9
RDX: 0000000000000000 RSI: 0000000020000000 RDI: ffffffffffffff9c
RBP: 00007f32cfbeb4a4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f32cfccd050 R15: 00007ffccd854ae8
 </TASK>
INFO: task syz-executor.4:5336 blocked for more than 144 seconds.
      Not tainted 5.15.156-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4  state:D stack:23040 pid: 5336 ppid:  3519 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5030 [inline]
 __schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
 schedule+0x11b/0x1f0 kernel/sched/core.c:6459
 xlog_grant_head_wait+0x381/0x900 fs/xfs/xfs_log.c:256
 xlog_grant_head_check+0x295/0x480
 xfs_log_reserve+0x3b8/0xb10 fs/xfs/xfs_log.c:464
 xfs_trans_reserve+0x23d/0x690 fs/xfs/xfs_trans.c:197
 xfs_trans_alloc+0x420/0x7f0 fs/xfs/xfs_trans.c:288
 xfs_trans_alloc_inode+0x129/0x450 fs/xfs/xfs_trans.c:1047
 xfs_attr_set+0x848/0x1460 fs/xfs/libxfs/xfs_attr.c:772
 xfs_xattr_set+0x227/0x3a0 fs/xfs/xfs_xattr.c:59
 __vfs_setxattr+0x3e7/0x420 fs/xattr.c:182
 __vfs_setxattr_noperm+0x12a/0x5e0 fs/xattr.c:216
 vfs_setxattr+0x21d/0x420 fs/xattr.c:303
 do_setxattr fs/xattr.c:588 [inline]
 setxattr+0x27e/0x2e0 fs/xattr.c:611
 path_setxattr+0x1bc/0x2a0 fs/xattr.c:630
 __do_sys_setxattr fs/xattr.c:646 [inline]
 __se_sys_setxattr fs/xattr.c:642 [inline]
 __x64_sys_setxattr+0xb7/0xd0 fs/xattr.c:642
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f32cfb9eea9
RSP: 002b:00007f32ce0cf0c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007f32cfccd120 RCX: 00007f32cfb9eea9
RDX: 0000000020000280 RSI: 0000000020000100 RDI: 00000000200000c0
RBP: 00007f32cfbeb4a4 R08: 0000000000000000 R09: 0000000000000000
R10: 000000000000feeb R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f32cfccd120 R15: 00007ffccd854ae8
 </TASK>
INFO: task syz-executor.4:5387 blocked for more than 144 seconds.
      Not tainted 5.15.156-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4  state:D stack:26304 pid: 5387 ppid:  3519 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5030 [inline]
 __schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
 schedule+0x11b/0x1f0 kernel/sched/core.c:6459
 xlog_grant_head_wait+0x381/0x900 fs/xfs/xfs_log.c:256
 xlog_grant_head_check+0x295/0x480
 xfs_log_reserve+0x3b8/0xb10 fs/xfs/xfs_log.c:464
 xfs_trans_reserve+0x23d/0x690 fs/xfs/xfs_trans.c:197
 xfs_trans_alloc+0x420/0x7f0 fs/xfs/xfs_trans.c:288
 xfs_trans_alloc_icreate+0xc5/0x2b0 fs/xfs/xfs_trans.c:1102
 xfs_create+0x745/0x1370 fs/xfs/xfs_inode.c:1018
 xfs_generic_create+0x426/0xd00 fs/xfs/xfs_iops.c:197
 lookup_open fs/namei.c:3462 [inline]
 open_last_lookups fs/namei.c:3532 [inline]
 path_openat+0x130a/0x2f20 fs/namei.c:3739
 do_filp_open+0x21c/0x460 fs/namei.c:3769
 do_sys_openat2+0x13b/0x500 fs/open.c:1253
 do_sys_open fs/open.c:1269 [inline]
 __do_sys_openat fs/open.c:1285 [inline]
 __se_sys_openat fs/open.c:1280 [inline]
 __x64_sys_openat+0x243/0x290 fs/open.c:1280
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f32cfb9eea9
RSP: 002b:00007f32ce0ae0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f32cfccd1f0 RCX: 00007f32cfb9eea9
RDX: 000000000000275a RSI: 0000000020000200 RDI: ffffffffffffff9c
RBP: 00007f32cfbeb4a4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f32cfccd1f0 R15: 00007ffccd854ae8
 </TASK>
INFO: task syz-executor.4:5388 blocked for more than 145 seconds.
      Not tainted 5.15.156-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4  state:D stack:28696 pid: 5388 ppid:  3519 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5030 [inline]
 __schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
 schedule+0x11b/0x1f0 kernel/sched/core.c:6459
 rwsem_down_write_slowpath+0xf0c/0x16a0 kernel/locking/rwsem.c:1165
 do_renameat2+0x67e/0x1700 fs/namei.c:4924
 __do_sys_rename fs/namei.c:5031 [inline]
 __se_sys_rename fs/namei.c:5029 [inline]
 __x64_sys_rename+0x82/0x90 fs/namei.c:5029
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f32cfb9eea9
RSP: 002b:00007f32ce08d0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007f32cfccd2c0 RCX: 00007f32cfb9eea9
RDX: 0000000000000000 RSI: 00000000200003c0 RDI: 0000000020000380
RBP: 00007f32cfbeb4a4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f32cfccd2c0 R15: 00007ffccd854ae8
 </TASK>
INFO: task syz-executor.4:5407 blocked for more than 146 seconds.
      Not tainted 5.15.156-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4  state:D stack:29016 pid: 5407 ppid:  3519 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5030 [inline]
 __schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
 schedule+0x11b/0x1f0 kernel/sched/core.c:6459
 rwsem_down_write_slowpath+0xf0c/0x16a0 kernel/locking/rwsem.c:1165
 do_renameat2+0x67e/0x1700 fs/namei.c:4924
 __do_sys_rename fs/namei.c:5031 [inline]
 __se_sys_rename fs/namei.c:5029 [inline]
 __x64_sys_rename+0x82/0x90 fs/namei.c:5029
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f32cfb9eea9
RSP: 002b:00007f32ce06c0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007f32cfccd390 RCX: 00007f32cfb9eea9
RDX: 0000000000000000 RSI: 00000000200002c0 RDI: 0000000020000280
RBP: 00007f32cfbeb4a4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f32cfccd390 R15: 00007ffccd854ae8
 </TASK>

Showing all locks held in the system:
2 locks held by kworker/1:0/21:
1 lock held by khungtaskd/27:
 #0: ffffffff8c91fb20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by kworker/u4:4/1218:
2 locks held by getty/3267:
 #0: ffff88814b434098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc9000209b2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1db0 drivers/tty/n_tty.c:2158
3 locks held by kworker/0:4/3556:
 #0: ffff888011c70938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
 #1: ffffc900032d7d20 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
 #2: ffff8880b9a27e78 (krc.lock){..-.}-{2:2}, at: kfree_rcu_monitor+0x29/0x6c0 kernel/rcu/tree.c:3378
3 locks held by kworker/0:7/3562:
 #0: ffff888011c70938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
 #1: ffffc9000455fd20 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
 #2: ffffffff8d9e7688 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xa/0x50 net/core/link_watch.c:251
2 locks held by kworker/0:14/5126:
 #0: ffff888011c72138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
 #1: ffffc900037f7d20 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
2 locks held by kworker/0:16/5128:
 #0: ffff8880613e8138 ((wq_completion)xfs-sync/loop3){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
 #1: ffffc90003817d20 ((work_completion)(&(&log->l_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
2 locks held by syz-executor.4/5333:
 #0: ffff888078830460 (sb_writers#25){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377
 #1: ffff88805b163000 (&inode->i_sb->s_type->i_mutex_dir_key/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:824 [inline]
 #1: ffff88805b163000 (&inode->i_sb->s_type->i_mutex_dir_key/1){+.+.}-{3:3}, at: filename_create+0x25c/0x530 fs/namei.c:3835
2 locks held by syz-executor.4/5335:
 #0: ffff888078830460 (sb_writers#25){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377
 #1: ffff88805b163000 (&inode->i_sb->s_type->i_mutex_dir_key/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:824 [inline]
 #1: ffff88805b163000 (&inode->i_sb->s_type->i_mutex_dir_key/1){+.+.}-{3:3}, at: filename_create+0x25c/0x530 fs/namei.c:3835
3 locks held by syz-executor.4/5336:
 #0: ffff888078830460 (sb_writers#25){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377
 #1: ffff8880600a0a80 (&inode->i_sb->s_type->i_mutex_dir_key){++++}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
 #1: ffff8880600a0a80 (&inode->i_sb->s_type->i_mutex_dir_key){++++}-{3:3}, at: vfs_setxattr+0x1dd/0x420 fs/xattr.c:302
 #2: ffff888078830650 (sb_internal#3){.+.+}-{0:0}, at: xfs_trans_alloc_inode+0x129/0x450 fs/xfs/xfs_trans.c:1047
3 locks held by syz-executor.4/5387:
 #0: ffff888078830460 (sb_writers#25){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377
 #1: ffff88805b163000 (&inode->i_sb->s_type->i_mutex_dir_key){++++}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
 #1: ffff88805b163000 (&inode->i_sb->s_type->i_mutex_dir_key){++++}-{3:3}, at: open_last_lookups fs/namei.c:3529 [inline]
 #1: ffff88805b163000 (&inode->i_sb->s_type->i_mutex_dir_key){++++}-{3:3}, at: path_openat+0x824/0x2f20 fs/namei.c:3739
 #2: ffff888078830650 (sb_internal#3){.+.+}-{0:0}, at: xfs_trans_alloc_icreate+0xc5/0x2b0 fs/xfs/xfs_trans.c:1102
2 locks held by syz-executor.4/5388:
 #0: ffff888078830460 (sb_writers#25){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377
 #1: ffff88805b163000 (&inode->i_sb->s_type->i_mutex_dir_key/1){+.+.}-{3:3}, at: do_renameat2+0x67e/0x1700 fs/namei.c:4924
2 locks held by syz-executor.4/5407:
 #0: ffff888078830460 (sb_writers#25){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377
 #1: ffff88805b163000 (&inode->i_sb->s_type->i_mutex_dir_key/1){+.+.}-{3:3}, at: do_renameat2+0x67e/0x1700 fs/namei.c:4924
2 locks held by syz-executor.3/5585:
 #0: ffff888019d64460 (sb_writers#25){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377
 #1: ffff88805b161200 (&inode->i_sb->s_type->i_mutex_dir_key/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:824 [inline]
 #1: ffff88805b161200 (&inode->i_sb->s_type->i_mutex_dir_key/1){+.+.}-{3:3}, at: filename_create+0x25c/0x530 fs/namei.c:3835
3 locks held by syz-executor.3/5591:
 #0: ffff888019d64460 (sb_writers#25){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377
 #1: ffff88805b163780 (&inode->i_sb->s_type->i_mutex_dir_key){++++}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
 #1: ffff88805b163780 (&inode->i_sb->s_type->i_mutex_dir_key){++++}-{3:3}, at: vfs_setxattr+0x1dd/0x420 fs/xattr.c:302
 #2: ffff888019d64650 (sb_internal#3){.+.+}-{0:0}, at: xfs_trans_alloc_inode+0x129/0x450 fs/xfs/xfs_trans.c:1047
3 locks held by syz-executor.3/5625:
 #0: ffff888019d64460 (sb_writers#25){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377
 #1: ffff88805b161200 (&inode->i_sb->s_type->i_mutex_dir_key){++++}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
 #1: ffff88805b161200 (&inode->i_sb->s_type->i_mutex_dir_key){++++}-{3:3}, at: open_last_lookups fs/namei.c:3529 [inline]
 #1: ffff88805b161200 (&inode->i_sb->s_type->i_mutex_dir_key){++++}-{3:3}, at: path_openat+0x824/0x2f20 fs/namei.c:3739
 #2: ffff888019d64650 (sb_internal#3){.+.+}-{0:0}, at: xfs_trans_alloc_icreate+0xc5/0x2b0 fs/xfs/xfs_trans.c:1102
2 locks held by syz-executor.3/5626:
 #0: ffff888019d64460 (sb_writers#25){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377
 #1: ffff88805b161200 (&inode->i_sb->s_type->i_mutex_dir_key/1){+.+.}-{3:3}, at: do_renameat2+0x67e/0x1700 fs/namei.c:4924
2 locks held by syz-executor.3/5663:
 #0: ffff888019d64460 (sb_writers#25){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377
 #1: ffff88805b161200 (&inode->i_sb->s_type->i_mutex_dir_key/1){+.+.}-{3:3}, at: do_renameat2+0x67e/0x1700 fs/namei.c:4924
3 locks held by kworker/0:17/5713:
 #0: ffff8881425f6938 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
 #1: ffffc90004737d20 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
 #2: ffff888147e65220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
 #2: ffff888147e65220 (&dev->mutex){....}-{3:3}, at: hub_event+0x208/0x54c0 drivers/usb/core/hub.c:5768
6 locks held by kworker/1:10/5792:
 #0: ffff8881425f6938 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
 #1: ffffc90003087d20 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
 #2: ffff888147edd220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
 #2: ffff888147edd220 (&dev->mutex){....}-{3:3}, at: hub_event+0x208/0x54c0 drivers/usb/core/hub.c:5768
 #3: ffff88801d414220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
 #3: ffff88801d414220 (&dev->mutex){....}-{3:3}, at: __device_attach+0x8a/0x570 drivers/base/dd.c:954
 #4: ffff88805d8201a8 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
 #4: ffff88805d8201a8 (&dev->mutex){....}-{3:3}, at: __device_attach+0x8a/0x570 drivers/base/dd.c:954
 #5: ffff88801eaf6568 (hcd->bandwidth_mutex){+.+.}-{3:3}, at: usb_set_interface+0x35a/0x1390 drivers/usb/core/message.c:1559
2 locks held by kworker/1:14/5800:
 #0: 
ffff888060e1e938 ((wq_completion)xfs-sync/loop4){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
 #1: ffffc9000465fd20 ((work_completion)(&(&log->l_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
3 locks held by kworker/1:18/6510:
 #0: ffff88814ad58138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
 #1: ffffc90005007d20 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
 #2: ffffffff8d9e7688 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_dad_work+0xcc/0x1720 net/ipv6/addrconf.c:4112
1 lock held by syz-executor.1/7551:
 #0: ffff888057e840e0 (&type->s_umount_key#77){++++}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:365
2 locks held by syz-executor.2/8281:
 #0: ffffffff8d9e7688 (rtnl_mutex){+.+.}-{3:3}, at: tun_detach drivers/net/tun.c:699 [inline]
 #0: ffffffff8d9e7688 (rtnl_mutex){+.+.}-{3:3}, at: tun_chr_close+0x3a/0x1b0 drivers/net/tun.c:3435
 #1: ffffffff8c9240e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
 #1: ffffffff8c9240e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x280/0x740 kernel/rcu/tree_exp.h:845
1 lock held by syz-executor.4/8298:
 #0: ffffffff8d9e7688 (rtnl_mutex){+.+.}-{3:3}, at: tun_detach drivers/net/tun.c:699 [inline]
 #0: ffffffff8d9e7688 (rtnl_mutex){+.+.}-{3:3}, at: tun_chr_close+0x3a/0x1b0 drivers/net/tun.c:3435

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

NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted 5.15.156-syzkaller #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+0x1e3/0x2d0 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
 watchdog+0xe72/0xeb0 kernel/hung_task.c:295
 kthread+0x3f6/0x4f0 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:300
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 3247 Comm: kworker/0:3 Not tainted 5.15.156-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Workqueue: events bpf_prog_free_deferred
RIP: 0010:check_preemption_disabled+0x63/0x110 lib/smp_processor_id.c:19
Code: 44 24 08 0f 85 c7 00 00 00 89 d8 48 83 c4 10 5b 41 5c 41 5e 41 5f c3 48 c7 04 24 00 00 00 00 9c 8f 04 24 f7 04 24 00 02 00 00 <74> c9 49 89 f6 49 89 ff 65 4c 8b 25 dd bd e4 75 41 f6 44 24 2f 04
RSP: 0018:ffffc90002eb7a88 EFLAGS: 00000046
RAX: 0000000080000000 RBX: 0000000000000000 RCX: ffff88801b618000
RDX: 0000000000000000 RSI: ffffffff8ad8f360 RDI: ffffffff8ad8f320
RBP: ffffc90002eb7ba0 R08: ffffffff8186e150 R09: ffffed100ca60800
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffea000194c100
R13: dffffc0000000000 R14: 1ffff920005d6f5c R15: ffffc90002eb7b20
FS:  0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b32b25000 CR3: 000000005814d000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 free_unref_page+0x121/0x2d0 mm/page_alloc.c:3415
 __vunmap+0x8d4/0xa20 mm/vmalloc.c:2621
 bpf_jit_binary_free kernel/bpf/core.c:914 [inline]
 bpf_jit_free+0x92/0x180 kernel/bpf/core.c:927
 process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
 worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
 kthread+0x3f6/0x4f0 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:300
 </TASK>

Crashes (9):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/25 22:13 linux-5.15.y c52b9710c83d 8bdc0f22 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in filename_create
2024/04/24 05:05 linux-5.15.y c52b9710c83d 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in filename_create
2024/04/21 20:39 linux-5.15.y c52b9710c83d af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in filename_create
2024/04/21 08:24 linux-5.15.y c52b9710c83d af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in filename_create
2024/04/21 02:21 linux-5.15.y c52b9710c83d af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in filename_create
2024/04/22 18:44 linux-5.15.y c52b9710c83d 36c961ad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in filename_create
2024/04/18 03:28 linux-5.15.y c52b9710c83d acc528cb .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in filename_create
2024/04/18 00:15 linux-5.15.y c52b9710c83d acc528cb .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in filename_create
2024/04/15 05:31 linux-5.15.y fa3df276cd36 c8349e48 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in filename_create
* Struck through repros no longer work on HEAD.