[v5.15] INFO: task hung in lock_extent_bits

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c957cbb87315 Linux 5.15.105
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=125d2315c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=6f83fab0469f5de7
dashboard link: https://syzkaller.appspot.com/bug?extid=d359f673fb66296c98be
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/35817fda76e5/disk-c957cbb8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/80f96399b8d4/vmlinux-c957cbb8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4336a6ad59ec/bzImage-c957cbb8.xz

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

INFO: task kworker/u4:17:4783 blocked for more than 144 seconds.
Not tainted 5.15.105-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:17 state:D stack:24192 pid: 4783 ppid: 2 flags:0x00004000
Workqueue: btrfs-endio-write btrfs_work_helper
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+0x10d/0x1e0 fs/btrfs/extent_io.c:1469
btrfs_finish_ordered_io+0x6e9/0x1c40 fs/btrfs/inode.c:3108
btrfs_work_helper+0x368/0xba0 fs/btrfs/async-thread.c:325
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2306
worker_thread+0xaca/0x1280 kernel/workqueue.c:2453
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
INFO: task syz-executor.2:4952 blocked for more than 144 seconds.
Not tainted 5.15.105-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.2 state:D stack:23184 pid: 4952 ppid: 3629 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
wait_on_state fs/btrfs/extent_io.c:868 [inline]
wait_extent_bit+0x3f9/0x530 fs/btrfs/extent_io.c:906
lock_extent_bits+0x10d/0x1e0 fs/btrfs/extent_io.c:1469
btrfs_page_mkwrite+0x5f2/0xd60 fs/btrfs/inode.c:8898
do_page_mkwrite+0x1a9/0x440 mm/memory.c:2883
wp_page_shared+0x179/0x690 mm/memory.c:3216
handle_pte_fault mm/memory.c:4612 [inline]
__handle_mm_fault mm/memory.c:4729 [inline]
handle_mm_fault+0x2a3d/0x5950 mm/memory.c:4827
do_user_addr_fault arch/x86/mm/fault.c:1397 [inline]
handle_page_fault arch/x86/mm/fault.c:1485 [inline]
exc_page_fault+0x271/0x740 arch/x86/mm/fault.c:1541
asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:568
RIP: 0010:copy_user_generic_unrolled+0x89/0xc0 arch/x86/lib/copy_user_64.S:92
Code: 38 4c 89 47 20 4c 89 4f 28 4c 89 57 30 4c 89 5f 38 48 8d 76 40 48 8d 7f 40 ff c9 75 b6 89 d1 83 e2 07 c1 e9 03 74 12 4c 8b 06 <4c> 89 07 48 8d 76 08 48 8d 7f 08 ff c9 75 ee 21 d2 74 10 89 d1 8a
RSP: 0018:ffffc90004dcf668 EFLAGS: 00050202
RAX: ffffffff8405d101 RBX: 0000000020000098 RCX: 0000000000000007
RDX: 0000000000000000 RSI: ffffc90004dcf720 RDI: 0000000020000060
RBP: ffffc90004dcf7d0 R08: 0000000000000000 R09: fffff520009b9eeb
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000038
R13: 00007ffffffff000 R14: ffffc90004dcf720 R15: 0000000020000060
copy_user_generic arch/x86/include/asm/uaccess_64.h:37 [inline]
raw_copy_to_user arch/x86/include/asm/uaccess_64.h:58 [inline]
_copy_to_user+0xef/0x130 lib/usercopy.c:40
copy_to_user include/linux/uaccess.h:200 [inline]
fiemap_fill_next_extent+0x231/0x410 fs/ioctl.c:144
emit_fiemap_extent fs/btrfs/extent_io.c:5447 [inline]
extent_fiemap+0x1185/0x1650 fs/btrfs/extent_io.c:5686
btrfs_fiemap+0x121/0x160 fs/btrfs/inode.c:8521
ioctl_fiemap fs/ioctl.c:219 [inline]
do_vfs_ioctl+0x1934/0x2b70 fs/ioctl.c:814
__do_sys_ioctl fs/ioctl.c:872 [inline]
__se_sys_ioctl+0x81/0x160 fs/ioctl.c:860
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:0x7f02959050f9
RSP: 002b:00007f0293e77168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f0295a24f80 RCX: 00007f02959050f9
RDX: 0000000020000040 RSI: 00000000c020660b RDI: 0000000000000004
RBP: 00007f0295960b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd697eab9f R14: 00007f0293e77300 R15: 0000000000022000
</TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/26:
#0: ffffffff8c91b920 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3268:
#0: ffff888024961098 (&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/u4:10/3794:
#0: ffff888078325938 ((wq_completion)btrfs-flush_delalloc){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2279
#1: ffffc90004cafd20 ((work_completion)(&work->normal_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2281
2 locks held by kworker/u4:17/4783:
#0: ffff88801e35d938 ((wq_completion)btrfs-endio-write#2){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2279
#1: ffffc90005c87d20 ((work_completion)(&work->normal_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2281
3 locks held by syz-executor.2/4952:
#0: ffff88801986c728 (&mm->mmap_lock#2){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:136 [inline]
#0: ffff88801986c728 (&mm->mmap_lock#2){++++}-{3:3}, at: do_user_addr_fault arch/x86/mm/fault.c:1338 [inline]
#0: ffff88801986c728 (&mm->mmap_lock#2){++++}-{3:3}, at: handle_page_fault arch/x86/mm/fault.c:1485 [inline]
#0: ffff88801986c728 (&mm->mmap_lock#2){++++}-{3:3}, at: exc_page_fault+0x181/0x740 arch/x86/mm/fault.c:1541
#1: ffff888033fbc558 (sb_pagefaults#3){.+.+}-{0:0}, at: do_page_mkwrite+0x1a9/0x440 mm/memory.c:2883
#2: ffff888035009838 (&ei->i_mmap_lock){++++}-{3:3}, at: btrfs_page_mkwrite+0x4a2/0xd60 fs/btrfs/inode.c:8887
1 lock held by btrfs-transacti/5035:
#0: ffff88806f1687b0 (&fs_info->transaction_kthread_mutex){+.+.}-{3:3}, at: transaction_kthread+0xe4/0x410 fs/btrfs/disk-io.c:1865
3 locks held by syz-executor.3/5348:
#0: ffff888033fbc0e0 (&type->s_umount_key#57){++++}-{3:3}, at: iterate_supers+0xac/0x1e0 fs/super.c:703
#1: ffff88806f1689f8 (&fs_info->ordered_operations_mutex){+.+.}-{3:3}, at: btrfs_wait_ordered_roots+0x100/0x950 fs/btrfs/ordered-data.c:690
#2: ffff888019dc6848 (&root->ordered_extent_mutex){+.+.}-{3:3}, at: btrfs_wait_ordered_extents+0x1ef/0xe20 fs/btrfs/ordered-data.c:636
2 locks held by syz-executor.5/5444:
#0: ffff888033fbc0e0 (&type->s_umount_key#57){++++}-{3:3}, at: iterate_supers+0xac/0x1e0 fs/super.c:703
#1: ffff88806f1689f8 (&fs_info->ordered_operations_mutex){+.+.}-{3:3}, at: btrfs_wait_ordered_roots+0x100/0x950 fs/btrfs/ordered-data.c:690
2 locks held by syz-executor.3/5479:
#0: ffff888033fbc0e0 (&type->s_umount_key#57){++++}-{3:3}, at: iterate_supers+0xac/0x1e0 fs/super.c:703
#1: ffff88806f1689f8 (&fs_info->ordered_operations_mutex){+.+.}-{3:3}, at: btrfs_wait_ordered_roots+0x100/0x950 fs/btrfs/ordered-data.c:690

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

NMI backtrace for cpu 0
CPU: 0 PID: 26 Comm: khungtaskd Not tainted 5.15.105-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
watchdog+0xe72/0xeb0 kernel/hung_task.c:295
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 5480 Comm: kworker/u4:19 Not tainted 5.15.105-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: bat_events batadv_nc_worker
RIP: 0010:check_preemption_disabled+0x4d/0x110 lib/smp_processor_id.c:55
Code: 81 84 eb 75 a9 ff ff ff 7f 74 22 65 48 8b 04 25 28 00 00 00 48 3b 44 24 08 0f 85 c7 00 00 00 89 d8 48 83 c4 10 5b 41 5c 41 5e <41> 5f c3 48 c7 04 24 00 00 00 00 9c 8f 04 24 f7 04 24 00 02 00 00
RSP: 0018:ffffc9000c6bfbc8 EFLAGS: 00000282
RAX: 0000000000000001 RBX: ffff88802bbb0a20 RCX: ffff888024693a00
RDX: ffff888024693a00 RSI: ffffffff8ad85120 RDI: ffffffff8ad850e0
RBP: 0000000000000001 R08: ffffffff89f451b1 R09: fffffbfff1f76e15
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000144
R13: dffffc0000000000 R14: ffff88802ba54c80 R15: ffff88802426ba00
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005604a2c23600 CR3: 0000000023450000 CR4: 00000000003506e0
Call Trace:
<TASK>
rcu_dynticks_curr_cpu_in_eqs kernel/rcu/tree.c:330 [inline]
rcu_is_watching+0x11/0xa0 kernel/rcu/tree.c:1121
rcu_read_lock include/linux/rcupdate.h:697 [inline]
batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:412 [inline]
batadv_nc_worker+0xda/0x5b0 net/batman-adv/network-coding.c:723
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2306
worker_thread+0xaca/0x1280 kernel/workqueue.c:2453
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>


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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 0ab06468cbd1 Linux 5.15.114
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12337915280000
kernel config: https://syzkaller.appspot.com/x/.config?x=2d24dbde73b9b505

dashboard link: https://syzkaller.appspot.com/bug?extid=d359f673fb66296c98be
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17863c2d280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=175fb659280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/48a0cd4fb454/disk-0ab06468.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d857ea64526d/vmlinux-0ab06468.xz
kernel image: https://storage.googleapis.com/syzbot-assets/330499c124c4/bzImage-0ab06468.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/f36c1d03ef25/mount_0.gz

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

INFO: task kworker/u4:5:1464 blocked for more than 143 seconds.
Not tainted 5.15.114-syzkaller #0

"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

task:kworker/u4:5 state:D stack:19520 pid: 1464 ppid: 2 flags:0x00004000

Workqueue: btrfs-endio-write btrfs_work_helper
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+0x10d/0x1e0 fs/btrfs/extent_io.c:1469
btrfs_finish_ordered_io+0x6e9/0x1c40 fs/btrfs/inode.c:3108
btrfs_work_helper+0x368/0xba0 fs/btrfs/async-thread.c:325

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-executor259:3521 blocked for more than 143 seconds.
Not tainted 5.15.114-syzkaller #0

"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

task:syz-executor259 state:D stack:22416 pid: 3521 ppid: 3520 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
wait_on_state fs/btrfs/extent_io.c:868 [inline]
wait_extent_bit+0x3f9/0x530 fs/btrfs/extent_io.c:906
lock_extent_bits+0x10d/0x1e0 fs/btrfs/extent_io.c:1469
btrfs_page_mkwrite+0x5f2/0xd60 fs/btrfs/inode.c:8898
do_page_mkwrite+0x1a9/0x440 mm/memory.c:2883
wp_page_shared+0x179/0x690 mm/memory.c:3216

handle_pte_fault mm/memory.c:4626 [inline]
__handle_mm_fault mm/memory.c:4743 [inline]
handle_mm_fault+0x2a3d/0x5950 mm/memory.c:4841

do_user_addr_fault arch/x86/mm/fault.c:1397 [inline]
handle_page_fault arch/x86/mm/fault.c:1485 [inline]
exc_page_fault+0x271/0x740 arch/x86/mm/fault.c:1541
asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:568
RIP: 0010:copy_user_generic_unrolled+0x89/0xc0 arch/x86/lib/copy_user_64.S:92
Code: 38 4c 89 47 20 4c 89 4f 28 4c 89 57 30 4c 89 5f 38 48 8d 76 40 48 8d 7f 40 ff c9 75 b6 89 d1 83 e2 07 c1 e9 03 74 12 4c 8b 06 <4c> 89 07 48 8d 76 08 48 8d 7f 08 ff c9 75 ee 21 d2 74 10 89 d1 8a

RSP: 0018:ffffc90002b9f668 EFLAGS: 00050202
RAX: ffffffff84063501 RBX: 0000000020000118 RCX: 0000000000000007
RDX: 0000000000000000 RSI: ffffc90002b9f720 RDI: 00000000200000e0
RBP: ffffc90002b9f7d0 R08: 0000000000000000 R09: fffff52000573eeb

R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000038

R13: 00007ffffffff000 R14: ffffc90002b9f720 R15: 00000000200000e0

copy_user_generic arch/x86/include/asm/uaccess_64.h:37 [inline]
raw_copy_to_user arch/x86/include/asm/uaccess_64.h:58 [inline]
_copy_to_user+0xef/0x130 lib/usercopy.c:40
copy_to_user include/linux/uaccess.h:200 [inline]
fiemap_fill_next_extent+0x231/0x410 fs/ioctl.c:144

emit_fiemap_extent fs/btrfs/extent_io.c:5460 [inline]
extent_fiemap+0x1218/0x1650 fs/btrfs/extent_io.c:5686

btrfs_fiemap+0x121/0x160 fs/btrfs/inode.c:8521
ioctl_fiemap fs/ioctl.c:219 [inline]
do_vfs_ioctl+0x1934/0x2b70 fs/ioctl.c:814
__do_sys_ioctl fs/ioctl.c:872 [inline]
__se_sys_ioctl+0x81/0x160 fs/ioctl.c:860
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:0x7fdeb3193309
RSP: 002b:00007ffe1bf08708 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000020000080 RCX: 00007fdeb3193309
RDX: 00000000200000c0 RSI: 00000000c020660b RDI: 0000000000000004
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffe1bf08740
R13: 0000000000000000 R14: 431bde82d7b634db R15: 0000000000000000

</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
2 locks held by kworker/u4:5/1464:
#0: ffff8880242eb138 ((wq_completion)btrfs-endio-write){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2280
#1: ffffc90006897d20 ((work_completion)(&work->normal_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2282
2 locks held by getty/3255:
#0: ffff888024832098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002bb62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1da0 drivers/tty/n_tty.c:2147
3 locks held by syz-executor259/3521:
#0: ffff88807aa86328 (&mm->mmap_lock#2){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:136 [inline]
#0: ffff88807aa86328 (&mm->mmap_lock#2){++++}-{3:3}, at: do_user_addr_fault arch/x86/mm/fault.c:1338 [inline]
#0: ffff88807aa86328 (&mm->mmap_lock#2){++++}-{3:3}, at: handle_page_fault arch/x86/mm/fault.c:1485 [inline]
#0: ffff88807aa86328 (&mm->mmap_lock#2){++++}-{3:3}, at: exc_page_fault+0x181/0x740 arch/x86/mm/fault.c:1541
#1: ffff888078478558 (sb_pagefaults){.+.+}-{0:0}, at: do_page_mkwrite+0x1a9/0x440 mm/memory.c:2883
#2: ffff888070850e68 (&ei->i_mmap_lock){.+.+}-{3:3}, at: btrfs_page_mkwrite+0x4a2/0xd60 fs/btrfs/inode.c:8887

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

NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted 5.15.114-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023

Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
watchdog+0xe72/0xeb0 kernel/hung_task.c:295
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>

Sending NMI from CPU 1 to CPUs 0:

NMI backtrace for cpu 0

CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.114-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
RIP: 0010:kvm_set_cpu_l1tf_flush_l1d+0x0/0x20 arch/x86/include/asm/hardirq.h:67
Code: db fe ff ff 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c df fe ff ff 4c 89 e7 89 d3 e8 ab 24 94 00 89 da e9 ce fe ff ff cc cc cc cc <48> c7 c7 e0 99 87 8a e8 94 9d e5 08 65 c6 05 ae 5c ce 7e 01 c3 66
RSP: 0018:ffffffff8c607ab8 EFLAGS: 00000093
RAX: ffffffff81866d01 RBX: ffffffff8c607ad8 RCX: ffffffff8c6bb5c0
RDX: 0000000000000000 RSI: ffffffff8ad85f60 RDI: ffffffff8ad85f20
RBP: 0000000081866d01 R08: ffffffff81866d05 R09: fffffbfff1bc7736
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007ffef421c158 CR3: 0000000022a45000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
sysvec_call_function_single+0x11/0xb0 arch/x86/kernel/smp.c:243
asm_sysvec_call_function_single+0x16/0x20 arch/x86/include/asm/idtentry.h:646
RIP: 0010:native_save_fl arch/x86/include/asm/irqflags.h:22 [inline]
RIP: 0010:arch_local_save_flags arch/x86/include/asm/irqflags.h:70 [inline]
RIP: 0010:arch_irqs_disabled arch/x86/include/asm/irqflags.h:132 [inline]
RIP: 0010:acpi_safe_halt drivers/acpi/processor_idle.c:110 [inline]
RIP: 0010:acpi_idle_do_entry+0x10f/0x340 drivers/acpi/processor_idle.c:570
Code: ed 5b f7 48 83 e3 08 0f 85 0a 01 00 00 4c 8d 74 24 20 e8 94 5a 62 f7 0f 1f 44 00 00 e8 aa e9 5b f7 0f 00 2d 93 49 be 00 fb f4 <4c> 89 f3 48 c1 eb 03 42 80 3c 3b 00 74 08 4c 89 f7 e8 bb 44 a5 f7
RSP: 0018:ffffffff8c607b80 EFLAGS: 000002d3
RAX: ffffffff8a240fa6 RBX: 0000000000000000 RCX: ffffffff8c6bb5c0
RDX: 0000000000000000 RSI: ffffffff8a8afc60 RDI: ffffffff8ad85f80
RBP: ffffffff8c607c10 R08: ffffffff81866a60 R09: fffffbfff18d76b9
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffffffff18c0f70
R13: ffff888141fa3004 R14: ffffffff8c607ba0 R15: dffffc0000000000
acpi_idle_enter+0x352/0x4f0 drivers/acpi/processor_idle.c:705
cpuidle_enter_state+0x521/0xef0 drivers/cpuidle/cpuidle.c:237
cpuidle_enter+0x59/0x90 drivers/cpuidle/cpuidle.c:351
call_cpuidle kernel/sched/idle.c:158 [inline]
cpuidle_idle_call kernel/sched/idle.c:239 [inline]
do_idle+0x3e4/0x670 kernel/sched/idle.c:306
cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:403
start_kernel+0x491/0x53a init/main.c:1144
secondary_startup_64_no_verify+0xb1/0xbb
</TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.025 msecs


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

[syzbot]

syzbot suspects this issue could be fixed by backporting the following commit:

commit a1912f712188291f9d7d434fba155461f1ebef66
git tree: upstream
Author: Josef Bacik <jo...@toxicpanda.com>
Date: Wed Nov 22 17:17:55 2023 +0000

btrfs: remove code for inode_cache and recovery mount options

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=176b36e6180000

kernel config: https://syzkaller.appspot.com/x/.config?x=2d24dbde73b9b505
dashboard link: https://syzkaller.appspot.com/bug?extid=d359f673fb66296c98be

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17863c2d280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=175fb659280000

Please keep in mind that other backports might be required as well.

For information about bisection process see: https://goo.gl/tpsmEJ#bisection