[v5.15] unexpected kernel reboot

Hello,

syzbot found the following issue on:

HEAD commit: 1d146b1875fc Linux 5.15.144
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=135ce7d6e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=ef8f6be2f337b090
dashboard link: https://syzkaller.appspot.com/bug?extid=b29f8f762ea670f12a22
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/02ba22e2f6d3/disk-1d146b18.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/778fe9fed2a2/vmlinux-1d146b18.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f8a4e41c460a/bzImage-1d146b18.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

BTRFS info (device loop1): using blake2b (blake2b-256-generic) checksum algorithm
BTRFS error (device loop1): unrecognized mount option 'Booting the kernel. '
BTRFS error (device loop1): open_ctree failed


---
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 [email protected].

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

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