[v5.15] INFO: task hung in btrfs_page_mkwrite (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 284087d4f7d5 Linux 5.15.158
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16820e20980000
kernel config: https://syzkaller.appspot.com/x/.config?x=ab74f93e8454887c
dashboard link: https://syzkaller.appspot.com/bug?extid=568ce2aeddf99237f29a
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0accc7dacf9d/disk-284087d4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fb6b5b110f8c/vmlinux-284087d4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6763bebdbfea/Image-284087d4.gz.xz

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

INFO: task syz-executor.1:5232 blocked for more than 143 seconds.
Not tainted 5.15.158-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1 state:D stack: 0 pid: 5232 ppid: 5039 flags:0x00000005
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0xf10/0x1e48 kernel/sched/core.c:6376
schedule+0x11c/0x1c8 kernel/sched/core.c:6459
io_schedule+0x8c/0x194 kernel/sched/core.c:8484
wait_on_page_bit_common+0x6fc/0xc14 mm/filemap.c:1356
__lock_page+0x8c/0xa8 mm/filemap.c:1648
lock_page include/linux/pagemap.h:625 [inline]
btrfs_page_mkwrite+0x5e8/0xde8 fs/btrfs/inode.c:8943
do_page_mkwrite+0x144/0x37c mm/memory.c:2892
wp_page_shared+0x14c/0x398 mm/memory.c:3229
do_wp_page+0x7cc/0x9c4 mm/memory.c:3330
handle_pte_fault mm/memory.c:4639 [inline]
__handle_mm_fault mm/memory.c:4756 [inline]
handle_mm_fault+0x1bf8/0x3424 mm/memory.c:4854
__do_page_fault arch/arm64/mm/fault.c:505 [inline]
do_page_fault+0x700/0xb60 arch/arm64/mm/fault.c:605
do_mem_abort+0x70/0x1d8 arch/arm64/mm/fault.c:819
el0_da+0x94/0x20c arch/arm64/kernel/entry-common.c:494
el0t_64_sync_handler+0xc0/0xe4 arch/arm64/kernel/entry-common.c:629
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor.1:5233 blocked for more than 143 seconds.
Not tainted 5.15.158-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1 state:D stack: 0 pid: 5233 ppid: 5039 flags:0x0000000d
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0xf10/0x1e48 kernel/sched/core.c:6376
schedule+0x11c/0x1c8 kernel/sched/core.c:6459
wait_on_state fs/btrfs/extent_io.c:868 [inline]
wait_extent_bit+0x3e4/0x52c fs/btrfs/extent_io.c:906
lock_extent_bits+0x100/0x1d4 fs/btrfs/extent_io.c:1469
btrfs_page_mkwrite+0x66c/0xde8 fs/btrfs/inode.c:8953
do_page_mkwrite+0x144/0x37c mm/memory.c:2892
wp_page_shared+0x14c/0x398 mm/memory.c:3229
do_wp_page+0x7cc/0x9c4 mm/memory.c:3330
handle_pte_fault mm/memory.c:4639 [inline]
__handle_mm_fault mm/memory.c:4756 [inline]
handle_mm_fault+0x1bf8/0x3424 mm/memory.c:4854
__do_page_fault arch/arm64/mm/fault.c:505 [inline]
do_page_fault+0x700/0xb60 arch/arm64/mm/fault.c:605
do_mem_abort+0x70/0x1d8 arch/arm64/mm/fault.c:819
el1_abort+0x3c/0x5c arch/arm64/kernel/entry-common.c:358
el1h_64_sync_handler+0x60/0xac arch/arm64/kernel/entry-common.c:418
el1h_64_sync+0x78/0x7c arch/arm64/kernel/entry.S:522
__arch_copy_to_user+0x88/0x218 arch/arm64/lib/copy_template.S:90
emit_fiemap_extent fs/btrfs/extent_io.c:5461 [inline]
extent_fiemap+0xd84/0x10d4 fs/btrfs/extent_io.c:5687
btrfs_fiemap+0x100/0x150 fs/btrfs/inode.c:8576
ioctl_fiemap fs/ioctl.c:219 [inline]
do_vfs_ioctl+0x1bcc/0x2a38 fs/ioctl.c:814
__do_sys_ioctl fs/ioctl.c:872 [inline]
__se_sys_ioctl fs/ioctl.c:860 [inline]
__arm64_sys_ioctl+0xe4/0x1c8 fs/ioctl.c:860
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffff800014b114a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:311
2 locks held by getty/3726:
#0: ffff0000d3d09098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff80001a33b2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1204 drivers/tty/n_tty.c:2158
3 locks held by syz-executor.1/5232:
#0: ffff0000c1dad758 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:136 [inline]
#0: ffff0000c1dad758 (&mm->mmap_lock){++++}-{3:3}, at: do_page_fault+0x380/0xb60 arch/arm64/mm/fault.c:586
#1: ffff0000d79d2558 (sb_pagefaults){.+.+}-{0:0}, at: do_page_mkwrite+0x144/0x37c mm/memory.c:2892
#2: ffff0000e9651838 (&ei->i_mmap_lock){.+.+}-{3:3}, at: btrfs_page_mkwrite+0x530/0xde8 fs/btrfs/inode.c:8942
3 locks held by syz-executor.1/5233:
#0: ffff0000c1dad758 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:136 [inline]
#0: ffff0000c1dad758 (&mm->mmap_lock){++++}-{3:3}, at: do_page_fault+0x380/0xb60 arch/arm64/mm/fault.c:586
#1: ffff0000d79d2558 (sb_pagefaults){.+.+}-{0:0}, at: do_page_mkwrite+0x144/0x37c mm/memory.c:2892
#2: ffff0000e9651838 (&ei->i_mmap_lock){.+.+}-{3:3}, at: btrfs_page_mkwrite+0x530/0xde8 fs/btrfs/inode.c:8942

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



---
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 report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

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

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

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