syzbot


INFO: task hung in vfs_setxattr (7)

Status: upstream: reported syz repro on 2025/06/05 17:55
Subsystems: xfs
[Documentation on labels]
Reported-by: syzbot+3d0a18cd22695979a7c6@syzkaller.appspotmail.com
First crash: 50d, last: 2d08h
Cause bisection: failed (error log, bisect log)
  
Discussions (2)
Title Replies (including bot) Last reply
[syzbot] Monthly xfs report (Jun 2025) 0 (1) 2025/06/25 14:15
[syzbot] [xfs?] INFO: task hung in vfs_setxattr (7) 0 (1) 2025/06/05 17:55
Similar bugs (14)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in vfs_setxattr (2) fs 1 1861d 1861d 0/29 auto-closed as invalid on 2020/07/28 17:13
linux-5.15 INFO: task hung in vfs_setxattr (2) syz error 1 666d 666d 0/3 auto-obsoleted due to no activity on 2023/12/15 17:11
upstream INFO: task hung in vfs_setxattr (6) bcachefs 8 180d 272d 0/29 auto-obsoleted due to no activity on 2025/04/04 18:48
upstream INFO: task hung in vfs_setxattr (5) fs 1 381d 381d 0/29 auto-obsoleted due to no activity on 2024/09/15 03:42
android-49 INFO: task hung in vfs_setxattr 4 2518d 2544d 0/3 auto-closed as invalid on 2019/02/22 13:09
linux-5.15 INFO: task hung in vfs_setxattr (3) 1 431d 431d 0/3 auto-obsoleted due to no activity on 2024/08/06 16:46
upstream INFO: task hung in vfs_setxattr (3) fs syz done error 49 1334d 1752d 0/29 closed as invalid on 2022/02/08 10:51
upstream INFO: task hung in vfs_setxattr fs 46 2391d 2551d 0/29 auto-closed as invalid on 2019/06/15 01:37
linux-4.19 INFO: task hung in vfs_setxattr (2) C error 3 1364d 1644d 0/1 upstream: reported C repro on 2021/01/01 10:53
android-414 INFO: task hung in vfs_setxattr 1 2267d 2267d 0/1 auto-closed as invalid on 2019/10/16 16:43
linux-5.15 INFO: task hung in vfs_setxattr 1 817d 817d 0/3 auto-obsoleted due to no activity on 2023/08/06 19:50
upstream INFO: task hung in vfs_setxattr (4) ext4 1 730d 730d 0/29 auto-obsoleted due to no activity on 2023/10/02 09:30
linux-4.19 INFO: task hung in vfs_setxattr 3 2063d 2125d 0/1 auto-closed as invalid on 2020/03/08 20:30
android-44 INFO: task hung in vfs_setxattr C 3 2142d 2147d 0/2 public: reported C repro on 2019/08/17 15:36

Sample crash report:
INFO: task syz.4.337:10415 blocked for more than 143 seconds.
      Not tainted 6.16.0-rc3-next-20250625-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.4.337       state:D stack:28136 pid:10415 tgid:10358 ppid:5982   task_flags:0x400040 flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5313 [inline]
 __schedule+0x16f5/0x4d00 kernel/sched/core.c:6696
 __schedule_loop kernel/sched/core.c:6774 [inline]
 schedule+0x165/0x360 kernel/sched/core.c:6789
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6846
 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:869 [inline]
 vfs_setxattr+0x144/0x2f0 fs/xattr.c:320
 do_setxattr fs/xattr.c:636 [inline]
 filename_setxattr+0x274/0x600 fs/xattr.c:665
 path_setxattrat+0x364/0x3a0 fs/xattr.c:713
 __do_sys_lsetxattr fs/xattr.c:754 [inline]
 __se_sys_lsetxattr fs/xattr.c:750 [inline]
 __x64_sys_lsetxattr+0xbf/0xe0 fs/xattr.c:750
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f062478e929
RSP: 002b:00007f0625667038 EFLAGS: 00000246 ORIG_RAX: 00000000000000bd
RAX: ffffffffffffffda RBX: 00007f06249b6080 RCX: 00007f062478e929
RDX: 0000200000000340 RSI: 0000200000000180 RDI: 0000200000000040
RBP: 00007f0624810b39 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000000000d4 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007f06249b6080 R15: 00007ffecb25e5a8
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/31:
 #0: ffffffff8e13bf60 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #0: ffffffff8e13bf60 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline]
 #0: ffffffff8e13bf60 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6770
2 locks held by getty/5591:
 #0: ffff888034dca0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc9000331b2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x43e/0x1400 drivers/tty/n_tty.c:2222
1 lock held by udevd/5896:
 #0: ffff888022e707a0 (&sb->s_type->i_mutex_key#8){++++}-{4:4}, at: inode_lock_shared include/linux/fs.h:884 [inline]
 #0: ffff888022e707a0 (&sb->s_type->i_mutex_key#8){++++}-{4:4}, at: blkdev_read_iter+0x2f8/0x440 block/fops.c:832
1 lock held by syz-executor/5969:
 #0: ffff888073b620e0 (&type->s_umount_key#53){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff888073b620e0 (&type->s_umount_key#53){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff888073b620e0 (&type->s_umount_key#53){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:506
1 lock held by syz-executor/5973:
 #0: ffff8880315e20e0 (&type->s_umount_key#53){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff8880315e20e0 (&type->s_umount_key#53){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff8880315e20e0 (&type->s_umount_key#53){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:506
4 locks held by syz.4.337/10359:
2 locks held by syz.4.337/10415:
 #0: ffff8880721a2428 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:557
 #1: ffff888057138330 (&sb->s_type->i_mutex_key#20){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:869 [inline]
 #1: ffff888057138330 (&sb->s_type->i_mutex_key#20){+.+.}-{4:4}, at: vfs_setxattr+0x144/0x2f0 fs/xattr.c:320
2 locks held by syz.3.652/14481:
2 locks held by syz.2.654/14493:
2 locks held by dhcpcd/14497:
 #0: ffff8880753d4408 (&sb->s_type->i_mutex_key#11){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:869 [inline]
 #0: ffff8880753d4408 (&sb->s_type->i_mutex_key#11){+.+.}-{4:4}, at: __sock_release net/socket.c:648 [inline]
 #0: ffff8880753d4408 (&sb->s_type->i_mutex_key#11){+.+.}-{4:4}, at: sock_close+0x9b/0x240 net/socket.c:1439
 #1: ffffffff8e141a78 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock kernel/rcu/tree_exp.h:311 [inline]
 #1: ffffffff8e141a78 (rcu_state.exp_mutex){+.+.}-{4:4}, at: synchronize_rcu_expedited+0x2f6/0x730 kernel/rcu/tree_exp.h:967
2 locks held by dhcpcd/14514:
 #0: ffff8880753d6808 (&sb->s_type->i_mutex_key#11){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:869 [inline]
 #0: ffff8880753d6808 (&sb->s_type->i_mutex_key#11){+.+.}-{4:4}, at: __sock_release net/socket.c:648 [inline]
 #0: ffff8880753d6808 (&sb->s_type->i_mutex_key#11){+.+.}-{4:4}, at: sock_close+0x9b/0x240 net/socket.c:1439
 #1: ffffffff8e141a78 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock kernel/rcu/tree_exp.h:343 [inline]
 #1: ffffffff8e141a78 (rcu_state.exp_mutex){+.+.}-{4:4}, at: synchronize_rcu_expedited+0x3b9/0x730 kernel/rcu/tree_exp.h:967
2 locks held by syz.0.656/14522:

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 31 Comm: khungtaskd Not tainted 6.16.0-rc3-next-20250625-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:160 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:307 [inline]
 watchdog+0xfee/0x1030 kernel/hung_task.c:470
 kthread+0x711/0x8a0 kernel/kthread.c:463
 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148
 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: 10745 Comm: syz-executor Not tainted 6.16.0-rc3-next-20250625-syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:format_decode+0x6b/0xe30 lib/vsprintf.c:2671
Code: 00 41 0f b6 c6 83 f8 03 0f 84 65 06 00 00 45 31 f6 48 b9 00 00 00 00 00 fc ff df 4d 8d 24 2e 4c 89 e0 48 c1 e8 03 0f b6 04 08 <84> c0 75 28 42 0f b6 5c 35 00 48 89 df 48 c7 c6 70 a4 88 8f e8 6c
RSP: 0018:ffffc9000c4e7190 EFLAGS: 00000a03
RAX: 0000000000000000 RBX: 000000000000002e RCX: dffffc0000000000
RDX: 0000000000000000 RSI: ffffffff8f88a470 RDI: 000000000000002e
RBP: ffffffff8b8b7385 R08: ffff88802f3a1e00 R09: 0000000000000002
R10: 0000000000000025 R11: 0000000000000000 R12: ffffffff8b8b7386
R13: ffffc9000c4e7238 R14: 0000000000000001 R15: ffffffff8b8b7385
FS:  0000555563705500(0000) GS:ffff888125d21000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005647e6ad0660 CR3: 0000000073564000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 vsnprintf+0x102/0xf00 lib/vsprintf.c:2869
 sprintf+0xd9/0x120 lib/vsprintf.c:3089
 print_time kernel/printk/printk.c:1381 [inline]
 info_print_prefix+0x155/0x310 kernel/printk/printk.c:1407
 record_print_text+0x154/0x430 kernel/printk/printk.c:1456
 printk_get_next_message+0x26d/0x7b0 kernel/printk/printk.c:3024
 console_emit_next_record kernel/printk/printk.c:3092 [inline]
 console_flush_all+0x4ca/0xc40 kernel/printk/printk.c:3226
 __console_flush_and_unlock kernel/printk/printk.c:3285 [inline]
 console_unlock+0xc4/0x270 kernel/printk/printk.c:3325
 vprintk_emit+0x5b7/0x7a0 kernel/printk/printk.c:2450
 _printk+0xcf/0x120 kernel/printk/printk.c:2475
 __xfs_printk fs/xfs/xfs_message.c:24 [inline]
 xfs_printk_level+0x18b/0x280 fs/xfs/xfs_message.c:44
 xfs_fs_put_super+0x55/0x160 fs/xfs/xfs_super.c:1245
 generic_shutdown_super+0x132/0x2c0 fs/super.c:643
 kill_block_super+0x44/0x90 fs/super.c:1755
 xfs_kill_sb+0x15/0x50 fs/xfs/xfs_super.c:2317
 deactivate_locked_super+0xbc/0x130 fs/super.c:474
 cleanup_mnt+0x425/0x4c0 fs/namespace.c:1417
 task_work_run+0x1d4/0x260 kernel/task_work.c:227
 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
 exit_to_user_mode_loop+0xec/0x110 kernel/entry/common.c:114
 exit_to_user_mode_prepare include/linux/entry-common.h:330 [inline]
 syscall_exit_to_user_mode_work include/linux/entry-common.h:414 [inline]
 syscall_exit_to_user_mode include/linux/entry-common.h:449 [inline]
 do_syscall_64+0x2bd/0x3b0 arch/x86/entry/syscall_64.c:100
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f067d78fc57
Code: a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffc16a11ef8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f067d810925 RCX: 00007f067d78fc57
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffc16a11fb0
RBP: 00007ffc16a11fb0 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffc16a13040
R13: 00007f067d810925 R14: 000000000009b2b8 R15: 00007ffc16a13080
 </TASK>

Crashes (16):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/06/25 20:01 linux-next 1b152eeca84a 26d77996 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/06/01 17:34 linux-next 3a83b350b5be 3d2f584d .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/07/01 17:48 upstream 66701750d556 ffe4b334 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/06/18 15:03 upstream 52da431bf03b ca631f70 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/06/09 21:18 upstream 19272b37aa4f 4826c28e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/06/02 20:25 upstream cd2e103d57e5 b396b4bf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/05/27 15:52 upstream 914873bc7df9 874a1386 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/05/16 20:36 upstream 3c21441eeffc f41472b0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/05/14 08:19 upstream 405e6c37c89e 7344edeb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/06/25 13:10 linux-next 1b152eeca84a 26d77996 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/06/08 08:28 linux-next 475c850a7fdd 4826c28e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/06/02 10:36 linux-next 3a83b350b5be 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/06/01 18:10 linux-next 3a83b350b5be 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/06/01 14:23 linux-next 3a83b350b5be 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/06/01 09:10 linux-next 3a83b350b5be 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/05/30 22:03 linux-next 3a83b350b5be 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
* Struck through repros no longer work on HEAD.