[v5.15] kernel BUG in clear_inode

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8a7f2a5c5aa1 Linux 5.15.110
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1260c664280000
kernel config: https://syzkaller.appspot.com/x/.config?x=ba8d5c9d6c5289f
dashboard link: https://syzkaller.appspot.com/bug?extid=5f80757c41c983a43f80
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/fc04f54c047f/disk-8a7f2a5c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6b4ba4cb1191/vmlinux-8a7f2a5c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d927dc3f9670/bzImage-8a7f2a5c.xz

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

------------[ cut here ]------------
kernel BUG at fs/inode.c:546!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 3539 Comm: syz-executor.5 Not tainted 5.15.110-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
RIP: 0010:clear_inode+0x13f/0x150 fs/inode.c:546
Code: c7 06 60 00 00 00 5b 41 5c 41 5d 41 5e 41 5f c3 e8 36 49 a4 ff 0f 0b e8 2f 49 a4 ff 0f 0b e8 28 49 a4 ff 0f 0b e8 21 49 a4 ff <0f> 0b e8 1a 49 a4 ff 0f 0b 0f 1f 84 00 00 00 00 00 55 48 89 e5 41
RSP: 0018:ffffc90002e1faf0 EFLAGS: 00010293
RAX: ffffffff81db955f RBX: 0000000000000040 RCX: ffff8880209c9d00
RDX: 0000000000000000 RSI: 0000000000000040 RDI: 0000000000000000
RBP: ffffc90002e1fc20 R08: ffffffff81db94f4 R09: fffffbfff1f78c52
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff1100515659b R14: ffff888028ab2cd8 R15: ffff888028ab2c00
FS: 00005555555b9400(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30022000 CR3: 00000000489ab000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
btrfs_evict_inode+0x9de/0xff0 fs/btrfs/inode.c:5726
evict+0x2a4/0x620 fs/inode.c:587
dispose_list fs/inode.c:620 [inline]
evict_inodes+0x601/0x6a0 fs/inode.c:670
generic_shutdown_super+0x99/0x2c0 fs/super.c:454
kill_anon_super+0x37/0x60 fs/super.c:1067
btrfs_kill_super+0x3d/0x50 fs/btrfs/super.c:2391
deactivate_locked_super+0xa0/0x110 fs/super.c:335
cleanup_mnt+0x44e/0x500 fs/namespace.c:1143
task_work_run+0x129/0x1a0 kernel/task_work.c:164
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop+0x106/0x130 kernel/entry/common.c:175
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208
__syscall_exit_to_user_mode_work kernel/entry/common.c:290 [inline]
syscall_exit_to_user_mode+0x5d/0x250 kernel/entry/common.c:301
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f49f9a575d7
Code: ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffde0560628 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f49f9a575d7
RDX: 00007ffde05606fb RSI: 000000000000000a RDI: 00007ffde05606f0
RBP: 00007ffde05606f0 R08: 00000000ffffffff R09: 00007ffde05604c0
R10: 00005555555ba893 R11: 0000000000000246 R12: 00007f49f9ab0cdc
R13: 00007ffde05617b0 R14: 00005555555ba810 R15: 00007ffde05617f0
</TASK>
Modules linked in:
---[ end trace 46e7029b8bf4907d ]---
RIP: 0010:clear_inode+0x13f/0x150 fs/inode.c:546
Code: c7 06 60 00 00 00 5b 41 5c 41 5d 41 5e 41 5f c3 e8 36 49 a4 ff 0f 0b e8 2f 49 a4 ff 0f 0b e8 28 49 a4 ff 0f 0b e8 21 49 a4 ff <0f> 0b e8 1a 49 a4 ff 0f 0b 0f 1f 84 00 00 00 00 00 55 48 89 e5 41
RSP: 0018:ffffc90002e1faf0 EFLAGS: 00010293
RAX: ffffffff81db955f RBX: 0000000000000040 RCX: ffff8880209c9d00
RDX: 0000000000000000 RSI: 0000000000000040 RDI: 0000000000000000
RBP: ffffc90002e1fc20 R08: ffffffff81db94f4 R09: fffffbfff1f78c52
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff1100515659b R14: ffff888028ab2cd8 R15: ffff888028ab2c00
FS: 00005555555b9400(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fbc54ce4000 CR3: 00000000489ab000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


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