syzbot


INFO: task hung in vfs_setxattr

Status: auto-closed as invalid on 2019/10/16 16:43
Reported-by: syzbot+d7733b47586629a22411@syzkaller.appspotmail.com
First crash: 1884d, last: 1884d
Similar bugs (11)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in vfs_setxattr (2) fs 1 1478d 1478d 0/27 auto-closed as invalid on 2020/07/28 17:13
linux-5.15 INFO: task hung in vfs_setxattr (2) syz error 1 283d 283d 0/3 auto-obsoleted due to no activity on 2023/12/15 17:11
android-49 INFO: task hung in vfs_setxattr 4 2135d 2161d 0/3 auto-closed as invalid on 2019/02/22 13:09
linux-5.15 INFO: task hung in vfs_setxattr (3) 1 48d 48d 0/3 upstream: reported on 2024/04/28 16:46
upstream INFO: task hung in vfs_setxattr (3) fs syz done error 49 951d 1370d 0/27 closed as invalid on 2022/02/08 10:51
upstream INFO: task hung in vfs_setxattr fs 46 2008d 2168d 0/27 auto-closed as invalid on 2019/06/15 01:37
linux-4.19 INFO: task hung in vfs_setxattr (2) C error 3 981d 1261d 0/1 upstream: reported C repro on 2021/01/01 10:53
linux-5.15 INFO: task hung in vfs_setxattr 1 434d 434d 0/3 auto-obsoleted due to no activity on 2023/08/06 19:50
upstream INFO: task hung in vfs_setxattr (4) ext4 1 347d 347d 0/27 auto-obsoleted due to no activity on 2023/10/02 09:30
linux-4.19 INFO: task hung in vfs_setxattr 3 1680d 1742d 0/1 auto-closed as invalid on 2020/03/08 20:30
android-44 INFO: task hung in vfs_setxattr C 3 1759d 1764d 0/2 public: reported C repro on 2019/08/17 15:36

Sample crash report:
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

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


Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2019/04/19 16:42 android-4.14 cec361536f1e b0e8efcb .config console log report ci-android-414-kasan-gce-root
* Struck through repros no longer work on HEAD.