[v5.15] INFO: task hung in btrfs_page_mkwrite

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 471e639e59d1 Linux 5.15.117
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13fae8f3280000
kernel config: https://syzkaller.appspot.com/x/.config?x=eeb4064efec7aa39
dashboard link: https://syzkaller.appspot.com/bug?extid=a5a0956b72fa605f4763
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2e7359ecba67/disk-471e639e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ef6d17e44bc3/vmlinux-471e639e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/99b68dbd7e00/Image-471e639e.gz.xz

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

INFO: task syz-executor.2:4364 blocked for more than 143 seconds.
Not tainted 5.15.117-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.2 state:D stack: 0 pid: 4364 ppid: 4017 flags:0x00000001
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
io_schedule+0x8c/0x194 kernel/sched/core.c:8472
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:8888
do_page_mkwrite+0x144/0x37c mm/memory.c:2883
wp_page_shared+0x14c/0x398 mm/memory.c:3216
do_wp_page+0x7cc/0x9c4 mm/memory.c:3317
handle_pte_fault mm/memory.c:4626 [inline]
__handle_mm_fault mm/memory.c:4743 [inline]
handle_mm_fault+0x1ce4/0x33c4 mm/memory.c:4841
__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:482
el0t_64_sync_handler+0xc0/0xe4 arch/arm64/kernel/entry-common.c:617
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor.2:4435 blocked for more than 143 seconds.
Not tainted 5.15.117-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.2 state:D stack: 0 pid: 4435 ppid: 4017 flags:0x00000009
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
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:8898
do_page_mkwrite+0x144/0x37c mm/memory.c:2883
wp_page_shared+0x14c/0x398 mm/memory.c:3216
do_wp_page+0x7cc/0x9c4 mm/memory.c:3317
handle_pte_fault mm/memory.c:4626 [inline]
__handle_mm_fault mm/memory.c:4743 [inline]
handle_mm_fault+0x1ce4/0x33c4 mm/memory.c:4841
__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+0x5c/0x98 arch/arm64/kernel/entry-common.c:409
el1h_64_sync+0x78/0x7c arch/arm64/kernel/entry.S:579
__arch_copy_to_user+0x88/0x218 arch/arm64/lib/copy_template.S:90
emit_fiemap_extent fs/btrfs/extent_io.c:5460 [inline]
extent_fiemap+0xd84/0x10d4 fs/btrfs/extent_io.c:5686
btrfs_fiemap+0x100/0x150 fs/btrfs/inode.c:8521
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:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
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: ffff800014ac19a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:268
2 locks held by getty/3727:
#0: ffff0000d30c6098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff80001a29e2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1200 drivers/tty/n_tty.c:2147
3 locks held by syz-executor.2/4364:
#0: ffff0000c0ec5d18 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:136 [inline]
#0: ffff0000c0ec5d18 (&mm->mmap_lock){++++}-{3:3}, at: do_page_fault+0x380/0xb60 arch/arm64/mm/fault.c:586
#1: ffff0000cffae558 (sb_pagefaults#2){.+.+}-{0:0}, at: do_page_mkwrite+0x144/0x37c mm/memory.c:2883
#2: ffff0000df1e5318 (&ei->i_mmap_lock){.+.+}-{3:3}, at: btrfs_page_mkwrite+0x530/0xde8 fs/btrfs/inode.c:8887
3 locks held by syz-executor.2/4435:
#0: ffff0000c0ec5d18 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:136 [inline]
#0: ffff0000c0ec5d18 (&mm->mmap_lock){++++}-{3:3}, at: do_page_fault+0x380/0xb60 arch/arm64/mm/fault.c:586
#1: ffff0000cffae558 (sb_pagefaults#2){.+.+}-{0:0}, at: do_page_mkwrite+0x144/0x37c mm/memory.c:2883
#2: ffff0000df1e5318 (&ei->i_mmap_lock){.+.+}-{3:3}, at: btrfs_page_mkwrite+0x530/0xde8 fs/btrfs/inode.c:8887
3 locks held by kworker/u4:9/4545:
2 locks held by kworker/u4:11/4547:
#0: ffff0000c0029138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2280
#1: ffff80001d477c00 ((work_completion)(&sub_info->work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2282
3 locks held by kworker/u4:12/4811:
1 lock held by syz-executor.4/6754:
#0: ffff0000d2f634d8 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_lock include/linux/mmap_lock.h:117 [inline]
#0: ffff0000d2f634d8 (&mm->mmap_lock){++++}-{3:3}, at: do_page_fault+0x66c/0xb60 arch/arm64/mm/fault.c:590
1 lock held by syz-executor.4/6759:
#0: ffff800014ac5f28 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
#0: ffff800014ac5f28 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x320/0x660 kernel/rcu/tree_exp.h:842
1 lock held by syz-executor.4/6764:
1 lock held by syz-executor.4/6804:
#0: ffff0000d2f634d8 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_lock include/linux/mmap_lock.h:117 [inline]
#0: ffff0000d2f634d8 (&mm->mmap_lock){++++}-{3:3}, at: do_page_fault+0x66c/0xb60 arch/arm64/mm/fault.c:590
1 lock held by syz-executor.4/6807:
#0: ffff0000d2f634d8 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_lock include/linux/mmap_lock.h:117 [inline]
#0: ffff0000d2f634d8 (&mm->mmap_lock){++++}-{3:3}, at: do_page_fault+0x66c/0xb60 arch/arm64/mm/fault.c:590
1 lock held by syz-executor.4/6810:
#0: ffff0000d2f634d8 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_lock include/linux/mmap_lock.h:117 [inline]
#0: ffff0000d2f634d8 (&mm->mmap_lock){++++}-{3:3}, at: do_page_fault+0x66c/0xb60 arch/arm64/mm/fault.c:590
1 lock held by syz-executor.4/6811:
#0: ffff0000d2f634d8 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_lock include/linux/mmap_lock.h:117 [inline]
#0: ffff0000d2f634d8 (&mm->mmap_lock){++++}-{3:3}, at: do_page_fault+0x66c/0xb60 arch/arm64/mm/fault.c:590
1 lock held by syz-executor.3/6765:
#0: ffff0000cbc9a468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xa8/0x9b8 drivers/block/loop.c:1365
1 lock held by udevadm/6806:

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



---
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.