syzbot


INFO: task hung in vfs_setxattr

Status: auto-closed as invalid on 2019/02/22 13:09
First crash: 2103d, last: 2077d
Similar bugs (10)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in vfs_setxattr (2) fs 1 1420d 1420d 0/26 auto-closed as invalid on 2020/07/28 17:13
linux-5.15 INFO: task hung in vfs_setxattr (2) syz error 1 225d 225d 0/3 auto-obsoleted due to no activity on 2023/12/15 17:11
upstream INFO: task hung in vfs_setxattr (3) fs syz done error 49 894d 1312d 0/26 closed as invalid on 2022/02/08 10:51
upstream INFO: task hung in vfs_setxattr fs 46 1950d 2111d 0/26 auto-closed as invalid on 2019/06/15 01:37
linux-4.19 INFO: task hung in vfs_setxattr (2) C error 3 924d 1204d 0/1 upstream: reported C repro on 2021/01/01 10:53
android-414 INFO: task hung in vfs_setxattr 1 1826d 1826d 0/1 auto-closed as invalid on 2019/10/16 16:43
linux-5.15 INFO: task hung in vfs_setxattr 1 376d 376d 0/3 auto-obsoleted due to no activity on 2023/08/06 19:50
upstream INFO: task hung in vfs_setxattr (4) ext4 1 290d 290d 0/26 auto-obsoleted due to no activity on 2023/10/02 09:30
linux-4.19 INFO: task hung in vfs_setxattr 3 1622d 1685d 0/1 auto-closed as invalid on 2020/03/08 20:30
android-44 INFO: task hung in vfs_setxattr C 3 1702d 1706d 0/2 public: reported C repro on 2019/08/17 15:36

Sample crash report:
blk_update_request: I/O error, dev loop3, sector 0
Buffer I/O error on dev loop3p2, logical block 0, async page read
blk_update_request: I/O error, dev loop3, sector 0
Buffer I/O error on dev loop3p2, logical block 0, async page read
Buffer I/O error on dev loop3p2, logical block 0, async page read
INFO: task syz-executor1:9009 blocked for more than 140 seconds.
      Not tainted 4.9.119-g9dc978d #23
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor1   D29048  9009   3875 0x00000004
 ffff8801b55ae000 ffff8801d53e8000 ffff8801d53e8000 ffff88019cbec800
 ffff8801db321c18 ffff88019bf7f988 ffffffff839ebdcd ffffffff81235627
 0000000000000000 ffff8801b55ae8c0 0000000600000007 ffff8801db3224e8
Call Trace:
 [<ffffffff839ed3cf>] schedule+0x7f/0x1b0 kernel/sched/core.c:3553
 [<ffffffff839f8a08>] __rwsem_down_write_failed_common kernel/locking/rwsem-xadd.c:526 [inline]
 [<ffffffff839f8a08>] rwsem_down_write_failed+0x598/0x990 kernel/locking/rwsem-xadd.c:555
 [<ffffffff81ee8ec7>] call_rwsem_down_write_failed+0x17/0x30 arch/x86/lib/rwsem.S:105
 [<ffffffff839f67dc>] __down_write arch/x86/include/asm/rwsem.h:125 [inline]
 [<ffffffff839f67dc>] down_write+0x5c/0xa0 kernel/locking/rwsem.c:54
 [<ffffffff815f139b>] inode_lock include/linux/fs.h:766 [inline]
 [<ffffffff815f139b>] vfs_setxattr+0x8b/0xe0 fs/xattr.c:218
 [<ffffffff815f15ac>] setxattr+0x1bc/0x270 fs/xattr.c:449
 [<ffffffff815f17c7>] path_setxattr+0x167/0x180 fs/xattr.c:468
 [<ffffffff815f1b8b>] SYSC_setxattr fs/xattr.c:483 [inline]
 [<ffffffff815f1b8b>] SyS_setxattr+0x3b/0x50 fs/xattr.c:479
 [<ffffffff81006316>] do_syscall_64+0x1a6/0x490 arch/x86/entry/common.c:282
 [<ffffffff839fccd3>] entry_SYSCALL_64_after_swapgs+0x5d/0xdb

Showing all locks held in the system:
2 locks held by khungtaskd/519:
 #0:  (rcu_read_lock){......}, at: [<ffffffff813667bc>] check_hung_uninterruptible_tasks kernel/hung_task.c:168 [inline]
 #0:  (rcu_read_lock){......}, at: [<ffffffff813667bc>] watchdog+0x11c/0xa20 kernel/hung_task.c:239
 #1:  (tasklist_lock){.+.?..}, at: [<ffffffff81426027>] debug_show_all_locks+0x79/0x218 kernel/locking/lockdep.c:4336
2 locks held by getty/3778:
 #0:  (&tty->ldisc_sem){++++++}, at: [<ffffffff839fae72>] ldsem_down_read+0x32/0x40 drivers/tty/tty_ldsem.c:367
 #1:  (&ldata->atomic_read_lock){+.+...}, at: [<ffffffff821208d2>] n_tty_read+0x202/0x16e0 drivers/tty/n_tty.c:2142
1 lock held by syz-executor1/8914:
 #0:  (&sb->s_type->i_mutex_key#23){++++++}, at: [<ffffffff81595061>] inode_lock_shared include/linux/fs.h:776 [inline]
 #0:  (&sb->s_type->i_mutex_key#23){++++++}, at: [<ffffffff81595061>] lookup_slow+0x141/0x470 fs/namei.c:1645
2 locks held by syz-executor1/9009:
 #0:  (sb_writers#17){.+.+.+}, at: [<ffffffff815e0e3f>] sb_start_write include/linux/fs.h:1573 [inline]
 #0:  (sb_writers#17){.+.+.+}, at: [<ffffffff815e0e3f>] mnt_want_write+0x3f/0xb0 fs/namespace.c:391
 #1:  (&sb->s_type->i_mutex_key#23){++++++}, at: [<ffffffff815f139b>] inode_lock include/linux/fs.h:766 [inline]
 #1:  (&sb->s_type->i_mutex_key#23){++++++}, at: [<ffffffff815f139b>] vfs_setxattr+0x8b/0xe0 fs/xattr.c:218
1 lock held by syz-executor1/9011:
 #0:  (&sb->s_type->i_mutex_key#23){++++++}, at: [<ffffffff815e1c5c>] inode_lock include/linux/fs.h:766 [inline]
 #0:  (&sb->s_type->i_mutex_key#23){++++++}, at: [<ffffffff815e1c5c>] lock_mount+0x8c/0x2c0 fs/namespace.c:2077

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

NMI backtrace for cpu 0
CPU: 0 PID: 519 Comm: khungtaskd Not tainted 4.9.119-g9dc978d #23
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
 ffff8801d8617d08 ffffffff81eb4be9 0000000000000000 0000000000000000
 0000000000000000 0000000000000001 ffffffff810b9bd0 ffff8801d8617d40
 ffffffff81ebfee7 0000000000000000 0000000000000000 0000000000000003
Call Trace:
 [<ffffffff81eb4be9>] __dump_stack lib/dump_stack.c:15 [inline]
 [<ffffffff81eb4be9>] dump_stack+0xc1/0x128 lib/dump_stack.c:51
 [<ffffffff81ebfee7>] nmi_cpu_backtrace.cold.2+0x48/0x87 lib/nmi_backtrace.c:99
 [<ffffffff81ebfe7a>] nmi_trigger_cpumask_backtrace+0x12a/0x14f lib/nmi_backtrace.c:60
 [<ffffffff810b9cd4>] arch_trigger_cpumask_backtrace+0x14/0x20 arch/x86/kernel/apic/hw_nmi.c:37
 [<ffffffff81366d54>] trigger_all_cpu_backtrace include/linux/nmi.h:58 [inline]
 [<ffffffff81366d54>] check_hung_task kernel/hung_task.c:125 [inline]
 [<ffffffff81366d54>] check_hung_uninterruptible_tasks kernel/hung_task.c:182 [inline]
 [<ffffffff81366d54>] watchdog+0x6b4/0xa20 kernel/hung_task.c:239
 [<ffffffff8119d0ed>] kthread+0x26d/0x300 kernel/kthread.c:211
 [<ffffffff839fce9c>] ret_from_fork+0x5c/0x70 arch/x86/entry/entry_64.S:373
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at pc 0xffffffff839fb8d6

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2018/08/12 00:20 https://android.googlesource.com/kernel/common android-4.9 9dc978d43ec7 7a88b141 .config console log report ci-android-49-kasan-gce-root
2018/08/10 03:44 https://android.googlesource.com/kernel/common android-4.9 92e87041ed2d 1fb62d58 .config console log report ci-android-49-kasan-gce-root
2018/08/01 22:27 https://android.googlesource.com/kernel/common android-4.9 0137ea2134c0 0a7cf4ec .config console log report ci-android-49-kasan-gce-root
2018/07/16 22:16 https://android.googlesource.com/kernel/common android-4.9 9e7903954483 40cb0c9a .config console log report ci-android-49-kasan-gce-root
* Struck through repros no longer work on HEAD.