syzbot


INFO: task hung in do_get_write_access

Status: closed as invalid on 2022/02/08 09:40
Reported-by: syzbot+@syzkaller.appspotmail.com
First crash: 371d, last: 371d

Sample crash report:
INFO: task syz-executor.1:2226 blocked for more than 430 seconds.
      Not tainted 5.15.0-rc1-syzkaller-00001-g64a19591a293 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1  state:D stack:    0 pid: 2226 ppid:  2139 flags:0x00000000
Call Trace:
[<ffffffff82bdaf8a>] context_switch kernel/sched/core.c:4940 [inline]
[<ffffffff82bdaf8a>] __schedule+0x506/0x1048 kernel/sched/core.c:6287
[<ffffffff82bdbb32>] schedule+0x66/0x168 kernel/sched/core.c:6366
[<ffffffff82bdbce2>] io_schedule+0x5a/0x88 kernel/sched/core.c:8389
[<ffffffff82bdc8ca>] bit_wait_io+0x12/0x70 kernel/sched/wait_bit.c:209
[<ffffffff82bdc4c6>] __wait_on_bit+0x7c/0xf6 kernel/sched/wait_bit.c:49
[<ffffffff82bdc5ba>] out_of_line_wait_on_bit+0x7a/0x92 kernel/sched/wait_bit.c:64
[<ffffffff807158f2>] wait_on_bit_io include/linux/wait_bit.h:101 [inline]
[<ffffffff807158f2>] do_get_write_access+0x776/0xb18 fs/jbd2/transaction.c:1098
[<ffffffff80715d6c>] jbd2_journal_get_write_access+0xd8/0x124 fs/jbd2/transaction.c:1233
[<ffffffff80628504>] __ext4_journal_get_write_access+0x122/0x2b6 fs/ext4/ext4_jbd2.c:233
[<ffffffff80670020>] ext4_reserve_inode_write+0x10a/0x164 fs/ext4/inode.c:5763
[<ffffffff806704b2>] __ext4_mark_inode_dirty+0x100/0x602 fs/ext4/inode.c:5929
[<ffffffff8067b34e>] ext4_dirty_inode+0x90/0xba fs/ext4/inode.c:5966
[<ffffffff804a25f8>] __mark_inode_dirty+0x40a/0xefe fs/fs-writeback.c:2398
[<ffffffff80475b40>] generic_update_time fs/inode.c:1774 [inline]
[<ffffffff80475b40>] update_time fs/inode.c:1787 [inline]
[<ffffffff80475b40>] touch_atime+0x5ea/0x60e fs/inode.c:1858
[<ffffffff80460250>] file_accessed include/linux/fs.h:2504 [inline]
[<ffffffff80460250>] iterate_dir+0x254/0x386 fs/readdir.c:70
[<ffffffff8046095e>] __do_sys_getdents64 fs/readdir.c:369 [inline]
[<ffffffff8046095e>] sys_getdents64+0x8a/0x216 fs/readdir.c:354
[<ffffffff8000519c>] ret_from_syscall+0x0/0x2

Showing all locks held in the system:
1 lock held by khungtaskd/27:
 #0: ffffffff83d2b3e8 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x32/0x1fa kernel/locking/lockdep.c:6448
1 lock held by klogd/1791:
2 locks held by getty/1958:
 #0: ffffffe00da35098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x48 drivers/tty/tty_ldsem.c:340
 #1: ffffffd0107f52e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x9a0/0xafa drivers/tty/n_tty.c:2113
1 lock held by syz-fuzzer/1994:
3 locks held by syz-executor.1/2226:
 #0: ffffffe00bdca1c0 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: iterate_dir+0x8e/0x386 fs/readdir.c:55
 #1: ffffffe009e72460 (sb_writers#4){.+.+}-{0:0}, at: file_accessed include/linux/fs.h:2504 [inline]
 #1: ffffffe009e72460 (sb_writers#4){.+.+}-{0:0}, at: iterate_dir+0x254/0x386 fs/readdir.c:70
 #2: ffffffe009cae990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0x24a/0xad6 fs/jbd2/transaction.c:427
2 locks held by kworker/0:1/3793:
6 locks held by kworker/u4:1/3810:

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


Crashes (1):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-qemu2-riscv64 2021/12/02 00:14 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 64a19591a293 61f86278 .config log report info INFO: task hung in do_get_write_access
* Struck through repros no longer work on HEAD.