syzbot


INFO: task hung in v9fs_file_fsync_dotl

Status: auto-closed as invalid on 2019/02/22 15:09
First crash: 2067d, last: 2067d
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in v9fs_file_fsync_dotl v9fs 1 2018d 2017d 0/26 auto-closed as invalid on 2019/04/06 19:26

Sample crash report:
INFO: task syz-executor4:1716 blocked for more than 140 seconds.
      Not tainted 4.9.122-g54068d6 #26
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor4   D28248  1716   3876 0x00000004
 ffff88019f2ac800 0000000000000000 ffff8801ccab4fc0 ffff8801d9a6b000
 ffff8801db321c18 ffff8801c2a77b98 ffffffff839efdcd ffffffff812378c7
 0000000000000000 ffff88019f2ad0c0 0000000600000007 ffff8801db3224e8
Call Trace:
 [<ffffffff839f13cf>] schedule+0x7f/0x1b0 kernel/sched/core.c:3553
 [<ffffffff839fca08>] __rwsem_down_write_failed_common kernel/locking/rwsem-xadd.c:526 [inline]
 [<ffffffff839fca08>] rwsem_down_write_failed+0x598/0x990 kernel/locking/rwsem-xadd.c:555
 [<ffffffff81eecb47>] call_rwsem_down_write_failed+0x17/0x30 arch/x86/lib/rwsem.S:105
 [<ffffffff839fa7dc>] __down_write arch/x86/include/asm/rwsem.h:125 [inline]
 [<ffffffff839fa7dc>] down_write+0x5c/0xa0 kernel/locking/rwsem.c:54
 [<ffffffff8195bf07>] inode_lock include/linux/fs.h:766 [inline]
 [<ffffffff8195bf07>] v9fs_file_fsync_dotl+0xc7/0x140 fs/9p/vfs_file.c:475
 [<ffffffff8161e2fc>] vfs_fsync_range+0x10c/0x260 fs/sync.c:195
 [<ffffffff8161e4c2>] vfs_fsync fs/sync.c:209 [inline]
 [<ffffffff8161e4c2>] do_fsync+0x42/0xb0 fs/sync.c:219
 [<ffffffff8161ec69>] SYSC_fdatasync fs/sync.c:233 [inline]
 [<ffffffff8161ec69>] SyS_fdatasync+0x19/0x20 fs/sync.c:231
 [<ffffffff81006316>] do_syscall_64+0x1a6/0x490 arch/x86/entry/common.c:282
 [<ffffffff83a00cd3>] 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: [<ffffffff81368a5c>] check_hung_uninterruptible_tasks kernel/hung_task.c:168 [inline]
 #0:  (rcu_read_lock){......}, at: [<ffffffff81368a5c>] watchdog+0x11c/0xa20 kernel/hung_task.c:239
 #1:  (tasklist_lock){.+.+..}, at: [<ffffffff814282c8>] debug_show_all_locks+0x79/0x218 kernel/locking/lockdep.c:4336
2 locks held by rs:main Q:Reg/3676:
 #0:  (&f->f_pos_lock){+.+.+.}, at: [<ffffffff815dbb4c>] __fdget_pos+0xac/0xd0 fs/file.c:781
 #1:  (sb_writers#3){.+.+.+}, at: [<ffffffff815767be>] file_start_write include/linux/fs.h:2640 [inline]
 #1:  (sb_writers#3){.+.+.+}, at: [<ffffffff815767be>] vfs_write+0x3ae/0x530 fs/read_write.c:556
1 lock held by rsyslogd/3678:
 #0:  (&f->f_pos_lock){+.+.+.}, at: [<ffffffff815dbb4c>] __fdget_pos+0xac/0xd0 fs/file.c:781
2 locks held by getty/3774:
 #0:  (&tty->ldisc_sem){++++++}, at: [<ffffffff839fee72>] ldsem_down_read+0x32/0x40 drivers/tty/tty_ldsem.c:367
 #1:  (&ldata->atomic_read_lock){+.+...}, at: [<ffffffff82124562>] n_tty_read+0x202/0x16e0 drivers/tty/n_tty.c:2142
1 lock held by syz-executor4/1654:
 #0:  (&sb->s_type->i_mutex_key#21){++++++}, at: [<ffffffff8195bf07>] inode_lock include/linux/fs.h:766 [inline]
 #0:  (&sb->s_type->i_mutex_key#21){++++++}, at: [<ffffffff8195bf07>] v9fs_file_fsync_dotl+0xc7/0x140 fs/9p/vfs_file.c:475
1 lock held by syz-executor4/1716:
 #0:  (&sb->s_type->i_mutex_key#21){++++++}, at: [<ffffffff8195bf07>] inode_lock include/linux/fs.h:766 [inline]
 #0:  (&sb->s_type->i_mutex_key#21){++++++}, at: [<ffffffff8195bf07>] v9fs_file_fsync_dotl+0xc7/0x140 fs/9p/vfs_file.c:475

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

NMI backtrace for cpu 1
CPU: 1 PID: 519 Comm: khungtaskd Not tainted 4.9.122-g54068d6 #26
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
 ffff8801d8507d08 ffffffff81eb8829 0000000000000000 0000000000000001
 0000000000000001 0000000000000001 ffffffff810b9fa0 ffff8801d8507d40
 ffffffff81ec3b67 0000000000000001 0000000000000000 0000000000000003
Call Trace:
 [<ffffffff81eb8829>] __dump_stack lib/dump_stack.c:15 [inline]
 [<ffffffff81eb8829>] dump_stack+0xc1/0x128 lib/dump_stack.c:51
 [<ffffffff81ec3b67>] nmi_cpu_backtrace.cold.2+0x48/0x87 lib/nmi_backtrace.c:99
 [<ffffffff81ec3afa>] nmi_trigger_cpumask_backtrace+0x12a/0x14f lib/nmi_backtrace.c:60
 [<ffffffff810ba0a4>] arch_trigger_cpumask_backtrace+0x14/0x20 arch/x86/kernel/apic/hw_nmi.c:37
 [<ffffffff81368ff4>] trigger_all_cpu_backtrace include/linux/nmi.h:58 [inline]
 [<ffffffff81368ff4>] check_hung_task kernel/hung_task.c:125 [inline]
 [<ffffffff81368ff4>] check_hung_uninterruptible_tasks kernel/hung_task.c:182 [inline]
 [<ffffffff81368ff4>] watchdog+0x6b4/0xa20 kernel/hung_task.c:239
 [<ffffffff8119f38d>] kthread+0x26d/0x300 kernel/kthread.c:211
 [<ffffffff83a00e9c>] ret_from_fork+0x5c/0x70 arch/x86/entry/entry_64.S:373
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0 skipped: idling at pc 0xffffffff839ff8d6

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2018/08/20 21:56 https://android.googlesource.com/kernel/common android-4.9 54068d61e7d8 95b5c82b .config console log report ci-android-49-kasan-gce-root
* Struck through repros no longer work on HEAD.