[v5.15] INFO: task hung in bio_release_pages

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4af60700a60c Linux 5.15.119
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=174803b8a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=ba2032bf87adc4c7
dashboard link: https://syzkaller.appspot.com/bug?extid=df81bbb72428e5760081
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5a37f09fce32/disk-4af60700.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/28ef8a07cc8f/vmlinux-4af60700.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ff6087a74939/bzImage-4af60700.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+df81bb...@syzkaller.appspotmail.com

INFO: task kworker/0:6:3602 blocked for more than 143 seconds.
Not tainted 5.15.119-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:6 state:D stack:25344 pid: 3602 ppid: 2 flags:0x00004000
Workqueue: events bio_dirty_fn
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6372
schedule+0x11b/0x1f0 kernel/sched/core.c:6455
io_schedule+0x88/0x100 kernel/sched/core.c:8472
wait_on_page_bit_common+0xa13/0x1180 mm/filemap.c:1356
lock_page include/linux/pagemap.h:625 [inline]
set_page_dirty_lock+0xae/0xe0 mm/page-writeback.c:2633
bio_release_pages+0x231/0x550 block/bio.c:1030
bio_dirty_fn+0x6b/0xa0 block/bio.c:1385
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2307
worker_thread+0xaca/0x1280 kernel/workqueue.c:2454
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
INFO: task kworker/u4:8:3783 blocked for more than 143 seconds.
Not tainted 5.15.119-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:8 state:D stack:24320 pid: 3783 ppid: 2 flags:0x00004000
Workqueue: events_unbound btrfs_async_reclaim_metadata_space
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6372
schedule+0x11b/0x1f0 kernel/sched/core.c:6455
wait_on_state fs/btrfs/extent_io.c:868 [inline]
wait_extent_bit+0x3f9/0x530 fs/btrfs/extent_io.c:906
lock_extent_bits fs/btrfs/extent_io.c:1469 [inline]
find_lock_delalloc_range+0x469/0x8f0 fs/btrfs/extent_io.c:2047
writepage_delalloc+0x1a0/0x5a0 fs/btrfs/extent_io.c:3795
__extent_writepage+0x57d/0xbc0 fs/btrfs/extent_io.c:4108
extent_write_cache_pages fs/btrfs/extent_io.c:5029 [inline]
extent_writepages+0xbbd/0x1590 fs/btrfs/extent_io.c:5156
do_writepages+0x481/0x730 mm/page-writeback.c:2364
filemap_fdatawrite_wbc+0x1d6/0x230 mm/filemap.c:400
start_delalloc_inodes+0x7df/0xca0 fs/btrfs/inode.c:10064
btrfs_start_delalloc_roots+0x72f/0xa70 fs/btrfs/inode.c:10143
shrink_delalloc fs/btrfs/space-info.c:538 [inline]
flush_space+0x650/0xd50 fs/btrfs/space-info.c:646
btrfs_async_reclaim_metadata_space+0x29b/0x340 fs/btrfs/space-info.c:953
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2307
worker_thread+0xaca/0x1280 kernel/workqueue.c:2454
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
INFO: task syz-executor.3:8301 blocked for more than 150 seconds.
Not tainted 5.15.119-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.3 state:D stack:23264 pid: 8301 ppid: 3556 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6372
schedule+0x11b/0x1f0 kernel/sched/core.c:6455
io_schedule+0x88/0x100 kernel/sched/core.c:8472
wait_on_page_bit_common+0xa13/0x1180 mm/filemap.c:1356
lock_page include/linux/pagemap.h:625 [inline]
extent_write_cache_pages fs/btrfs/extent_io.c:5007 [inline]
extent_writepages+0x8fb/0x1590 fs/btrfs/extent_io.c:5156
do_writepages+0x481/0x730 mm/page-writeback.c:2364
filemap_fdatawrite_wbc+0x1d6/0x230 mm/filemap.c:400
__filemap_fdatawrite_range mm/filemap.c:433 [inline]
filemap_write_and_wait_range+0x19e/0x280 mm/filemap.c:704
__iomap_dio_rw+0x897/0x1f40 fs/iomap/direct-io.c:557
iomap_dio_rw+0x38/0x80 fs/iomap/direct-io.c:672
btrfs_direct_read fs/btrfs/file.c:3788 [inline]
btrfs_file_read_iter+0x3a1/0x6a0 fs/btrfs/file.c:3828
do_iter_readv_writev+0x594/0x7a0
do_iter_read+0x1ec/0x760 fs/read_write.c:790
vfs_readv fs/read_write.c:910 [inline]
do_preadv+0x211/0x350 fs/read_write.c:1002
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f0412f9a389
RSP: 002b:00007f041150c168 EFLAGS: 00000246 ORIG_RAX: 0000000000000147
RAX: ffffffffffffffda RBX: 00007f04130b9f80 RCX: 00007f0412f9a389
RDX: 0000000000000001 RSI: 0000000020000100 RDI: 0000000000000004
RBP: 00007f0412fe5493 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffee730941f R14: 00007f041150c300 R15: 0000000000022000
</TASK>
INFO: task syz-executor.3:8357 blocked for more than 150 seconds.
Not tainted 5.15.119-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.3 state:D stack:24000 pid: 8357 ppid: 3556 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6372
schedule+0x11b/0x1f0 kernel/sched/core.c:6455
io_schedule+0x88/0x100 kernel/sched/core.c:8472
wait_on_page_bit_common+0xa13/0x1180 mm/filemap.c:1356
lock_page include/linux/pagemap.h:625 [inline]
set_page_dirty_lock+0xae/0xe0 mm/page-writeback.c:2633
bio_set_pages_dirty+0x1f3/0x2c0 block/bio.c:1349
iomap_dio_bio_iter+0xb8d/0x1540 fs/iomap/direct-io.c:338
__iomap_dio_rw+0xf9f/0x1f40 fs/iomap/direct-io.c:586
iomap_dio_rw+0x38/0x80 fs/iomap/direct-io.c:672
btrfs_direct_read fs/btrfs/file.c:3788 [inline]
btrfs_file_read_iter+0x3a1/0x6a0 fs/btrfs/file.c:3828
do_iter_readv_writev+0x594/0x7a0
do_iter_read+0x1ec/0x760 fs/read_write.c:790
vfs_readv fs/read_write.c:910 [inline]
do_preadv+0x211/0x350 fs/read_write.c:1002
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f0412f9a389
RSP: 002b:00007f040a0eb168 EFLAGS: 00000246 ORIG_RAX: 0000000000000147
RAX: ffffffffffffffda RBX: 00007f04130ba050 RCX: 00007f0412f9a389
RDX: 0000000000000001 RSI: 0000000020000100 RDI: 0000000000000004
RBP: 00007f0412fe5493 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffee730941f R14: 00007f040a0eb300 R15: 0000000000022000
</TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c91c5e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
3 locks held by kworker/0:2/1196:
#0: ffff888011c64d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2280
#1: ffffc900048ffd20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2282
#2: ffffffff8c920b28 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
#2: ffffffff8c920b28 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x350/0x740 kernel/rcu/tree_exp.h:842
2 locks held by getty/3257:
#0: ffff88814b37a098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002bb32e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1da0 drivers/tty/n_tty.c:2147
2 locks held by kworker/0:6/3602:
#0: ffff888011c64d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2280
#1: ffffc90003d7fd20 (bio_dirty_work){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2282
2 locks held by kworker/0:8/3613:
4 locks held by kworker/u4:8/3783:
#0: ffff888011c69138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2280
#1: ffffc90004b3fd20 ((work_completion)(&fs_info->async_reclaim_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2282
#2: ffff888073f80eb0 (&fs_info->delalloc_root_mutex){+.+.}-{3:3}, at: btrfs_start_delalloc_roots+0x1c6/0xa70 fs/btrfs/inode.c:10124
#3: ffff88801b04c750 (&root->delalloc_mutex){+.+.}-{3:3}, at: start_delalloc_inodes+0x1a8/0xca0 fs/btrfs/inode.c:10029
3 locks held by kworker/u4:16/3879:
#0: ffff88814199c938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2280
#1: ffffc900042ffd20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2282
#2: ffff888074b0c0e0 (&type->s_umount_key#59){++++}-{3:3}, at: trylock_super+0x1b/0xf0 fs/super.c:418
2 locks held by kworker/u4:19/4242:
#0: ffff888011c69138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2280
#1: ffffc9000508fd20 ((work_completion)(&sub_info->work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2282
4 locks held by kworker/u4:20/4732:
2 locks held by kworker/0:17/8287:
#0: ffff888011c66538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2280
#1: ffffc90006f27d20 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2282


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.