INFO: task hung in vfs

Kernel	Title	Rank 🛈	Repro	Cause bisect	Fix bisect	Count	Last	Reported	Patched	Status
upstream	INFO: task hung in vfs_setxattr (2) fs	1				1	1928d	1928d	0/29	auto-closed as invalid on 2020/07/28 17:13
linux-5.15	INFO: task hung in vfs_setxattr (2)	1	syz		error	1	733d	733d	0/3	auto-obsoleted due to no activity on 2023/12/15 17:11
upstream	INFO: task hung in vfs_setxattr (6) bcachefs	1				8	247d	339d	0/29	auto-obsoleted due to no activity on 2025/04/04 18:48
upstream	INFO: task hung in vfs_setxattr (5) fs	1				1	448d	448d	0/29	auto-obsoleted due to no activity on 2024/09/15 03:42
android-49	INFO: task hung in vfs_setxattr	1				4	2584d	2611d	0/3	auto-closed as invalid on 2019/02/22 13:09
linux-5.15	INFO: task hung in vfs_setxattr (3)	1				1	498d	498d	0/3	auto-obsoleted due to no activity on 2024/08/06 16:46
upstream	INFO: task hung in vfs_setxattr (3) fs	1	syz	done	error	49	1401d	1819d	0/29	closed as invalid on 2022/02/08 10:51
upstream	INFO: task hung in vfs_setxattr fs	1				46	2457d	2618d	0/29	auto-closed as invalid on 2019/06/15 01:37
linux-4.19	INFO: task hung in vfs_setxattr (2)	1	C		error	3	1431d	1711d	0/1	upstream: reported C repro on 2021/01/01 10:53
linux-5.15	INFO: task hung in vfs_setxattr	1				1	884d	884d	0/3	auto-obsoleted due to no activity on 2023/08/06 19:50
upstream	INFO: task hung in vfs_setxattr (7) xfs	1	syz	error		34	1d07h	95d	0/29	upstream: reported syz repro on 2025/06/05 17:55
upstream	INFO: task hung in vfs_setxattr (4) ext4	1				1	797d	797d	0/29	auto-obsoleted due to no activity on 2023/10/02 09:30
linux-4.19	INFO: task hung in vfs_setxattr	1				3	2130d	2192d	0/1	auto-closed as invalid on 2020/03/08 20:30
android-6-12	INFO: task hung in vfs_setxattr	1				1	54d	54d	0/1	premoderation: reported on 2025/07/16 10:56
android-44	INFO: task hung in vfs_setxattr	1	C			3	2209d	2214d	0/2	public: reported C repro on 2019/08/17 15:36

INFO: task syz-executor.0:23887 blocked for more than 140 seconds. Not tainted 4.14.112+ #57 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. syz-executor.0 D30176 23887 1840 0x00000004 Call Trace: schedule+0x92/0x1c0 kernel/sched/core.c:3498 __rwsem_down_write_failed_common kernel/locking/rwsem-xadd.c:572 [inline] rwsem_down_write_failed+0x3b1/0x760 kernel/locking/rwsem-xadd.c:601 call_rwsem_down_write_failed+0x13/0x20 arch/x86/lib/rwsem.S:105 __down_write arch/x86/include/asm/rwsem.h:126 [inline] down_write+0x4f/0x90 kernel/locking/rwsem.c:56 inode_lock include/linux/fs.h:715 [inline] vfs_setxattr+0x89/0xe0 fs/xattr.c:219 setxattr+0x1bc/0x330 fs/xattr.c:453 path_setxattr+0x138/0x150 fs/xattr.c:472 SYSC_lsetxattr fs/xattr.c:494 [inline] SyS_lsetxattr+0x33/0x40 fs/xattr.c:490 do_syscall_64+0x19b/0x4b0 arch/x86/entry/common.c:289 Showing all locks held in the system: 1 lock held by khungtaskd/23: #0: (tasklist_lock){.+.+}, at: [<000000007dbd6acf>] debug_show_all_locks+0x7c/0x21a kernel/locking/lockdep.c:4544 2 locks held by getty/1748: #0: (&tty->ldisc_sem){++++}, at: [<00000000fe2cbad5>] tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:284 #1: (&ldata->atomic_read_lock){+.+.}, at: [<000000004d05e1fd>] n_tty_read+0x1f7/0x1700 drivers/tty/n_tty.c:2156 2 locks held by syz-executor.0/23887: #0: (sb_writers#4){.+.+}, at: [<00000000acdbf830>] sb_start_write include/linux/fs.h:1545 [inline] #0: (sb_writers#4){.+.+}, at: [<00000000acdbf830>] mnt_want_write+0x3a/0xb0 fs/namespace.c:387 #1: (&sb->s_type->i_mutex_key#9){++++}, at: [<0000000036ad98a4>] inode_lock include/linux/fs.h:715 [inline] #1: (&sb->s_type->i_mutex_key#9){++++}, at: [<0000000036ad98a4>] vfs_setxattr+0x89/0xe0 fs/xattr.c:219 =============================================