syzbot


INFO: task hung in vfs_setxattr

Status: auto-obsoleted due to no activity on 2023/08/06 19:50
Reported-by: syzbot+873479d6585b213f694e@syzkaller.appspotmail.com
First crash: 592d, last: 592d
Similar bugs (12)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in vfs_setxattr (2) fs 1 1636d 1636d 0/28 auto-closed as invalid on 2020/07/28 17:13
linux-5.15 INFO: task hung in vfs_setxattr (2) syz error 1 441d 441d 0/3 auto-obsoleted due to no activity on 2023/12/15 17:11
upstream INFO: task hung in vfs_setxattr (5) fs 1 157d 157d 0/28 auto-obsoleted due to no activity on 2024/09/15 03:42
android-49 INFO: task hung in vfs_setxattr 4 2293d 2319d 0/3 auto-closed as invalid on 2019/02/22 13:09
linux-5.15 INFO: task hung in vfs_setxattr (3) 1 206d 206d 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 1110d 1528d 0/28 closed as invalid on 2022/02/08 10:51
upstream INFO: task hung in vfs_setxattr fs 46 2166d 2327d 0/28 auto-closed as invalid on 2019/06/15 01:37
linux-4.19 INFO: task hung in vfs_setxattr (2) C error 3 1139d 1420d 0/1 upstream: reported C repro on 2021/01/01 10:53
android-414 INFO: task hung in vfs_setxattr 1 2042d 2042d 0/1 auto-closed as invalid on 2019/10/16 16:43
upstream INFO: task hung in vfs_setxattr (4) ext4 1 506d 506d 0/28 auto-obsoleted due to no activity on 2023/10/02 09:30
linux-4.19 INFO: task hung in vfs_setxattr 3 1838d 1901d 0/1 auto-closed as invalid on 2020/03/08 20:30
android-44 INFO: task hung in vfs_setxattr C 3 1918d 1922d 0/2 public: reported C repro on 2019/08/17 15:36

Sample crash report:
INFO: task syz-executor.3:13467 blocked for more than 143 seconds.
      Not tainted 5.15.106-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.3  state:D stack:    0 pid:13467 ppid:  4109 flags:0x00000009
Call trace:
 __switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
 context_switch kernel/sched/core.c:5026 [inline]
 __schedule+0xf10/0x1e38 kernel/sched/core.c:6372
 schedule+0x11c/0x1c8 kernel/sched/core.c:6455
 rwsem_down_write_slowpath+0xca8/0x1340 kernel/locking/rwsem.c:1157
 __down_write_common kernel/locking/rwsem.c:1284 [inline]
 __down_write kernel/locking/rwsem.c:1293 [inline]
 down_write+0x25c/0x260 kernel/locking/rwsem.c:1542
 inode_lock include/linux/fs.h:787 [inline]
 vfs_setxattr+0x17c/0x344 fs/xattr.c:302
 do_setxattr fs/xattr.c:588 [inline]
 setxattr+0x250/0x2b4 fs/xattr.c:611
 path_setxattr+0x17c/0x258 fs/xattr.c:630
 __do_sys_setxattr fs/xattr.c:646 [inline]
 __se_sys_setxattr fs/xattr.c:642 [inline]
 __arm64_sys_setxattr+0xbc/0xd8 fs/xattr.c:642
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
 el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Showing all locks held in the system:
1 lock held by khungtaskd/27:
 #0: ffff800014aa1660 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:268
2 locks held by getty/3741:
 #0: ffff0000d2ab3098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
 #1: ffff80001a2be2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1200 drivers/tty/n_tty.c:2147
1 lock held by syz-executor.2/4105:
 #0: ffff000139b500e0 (&type->s_umount_key#66){+.+.}-{3:3}, at: deactivate_super+0x100/0x128 fs/super.c:365
2 locks held by kworker/1:9/11045:
 #0: ffff0001213cf138 ((wq_completion)xfs-sync/loop3){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2279
 #1: ffff80001f307c00 ((work_completion)(&(&log->l_work)->work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2281
2 locks held by kworker/u4:14/12304:
2 locks held by syz-executor.3/13467:
 #0: ffff0000d79fa460 (sb_writers#17){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:377
 #1: ffff0000df2e8300 (&sb->s_type->i_mutex_key#23){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #1: ffff0000df2e8300 (&sb->s_type->i_mutex_key#23){+.+.}-{3:3}, at: vfs_setxattr+0x17c/0x344 fs/xattr.c:302
3 locks held by syz-executor.3/13493:
 #0: ffff0000d79fa460 (sb_writers#17){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:377
 #1: ffff0000df2e8300 (&sb->s_type->i_mutex_key#23){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #1: ffff0000df2e8300 (&sb->s_type->i_mutex_key#23){+.+.}-{3:3}, at: vfs_setxattr+0x17c/0x344 fs/xattr.c:302
 #2: ffff0000d79fa650 (sb_internal#3){.+.+}-{0:0}, at: xfs_trans_alloc_inode+0x114/0x404 fs/xfs/xfs_trans.c:1047
1 lock held by syz-executor.3/14732:
2 locks held by syz-executor.1/14751:

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


Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/04/08 19:50 linux-5.15.y d86dfc4d95cd 71147e29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in vfs_setxattr
* Struck through repros no longer work on HEAD.