[v5.15] kernel BUG in clear_inode (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b925f60c6ee7 Linux 5.15.157
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=160c637f180000
kernel config: https://syzkaller.appspot.com/x/.config?x=2a1cb0d51cbb9dfb
dashboard link: https://syzkaller.appspot.com/bug?extid=0bcec20798338ff74b95
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/07f51426f82f/disk-b925f60c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d41cc73399aa/vmlinux-b925f60c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0f542c09e64b/bzImage-b925f60c.xz

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

------------[ cut here ]------------
kernel BUG at fs/inode.c:546!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 5164 Comm: syz-executor.4 Not tainted 5.15.157-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
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 c6 be a3 ff 0f 0b e8 bf be a3 ff 0f 0b e8 b8 be a3 ff 0f 0b e8 b1 be a3 ff <0f> 0b e8 aa be a3 ff 0f 0b 0f 1f 84 00 00 00 00 00 55 48 89 e5 41
RSP: 0018:ffffc900036e7af0 EFLAGS: 00010293
RAX: ffffffff81dc9e2f RBX: 0000000000000040 RCX: ffff88805cd75940
RDX: 0000000000000000 RSI: 0000000000000040 RDI: 0000000000000000
RBP: ffffc900036e7c20 R08: ffffffff81dc9dc4 R09: fffffbfff1f7ee42
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff1100e4eff6b R14: ffff88807277fb58 R15: ffff88807277fa80
FS: 0000555556efe480(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c000cd6020 CR3: 0000000055acb000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
btrfs_evict_inode+0x9de/0xff0 fs/btrfs/inode.c:5737
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:1076
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:181
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:214
__syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
syscall_exit_to_user_mode+0x5d/0x240 kernel/entry/common.c:307
do_syscall_64+0x47/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fca3e6c21d7
Code: b0 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 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 00 f0 ff ff 77 01 c3 48 c7 c2 b0 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007fff0e375058 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007fca3e6c21d7
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007fff0e375110
RBP: 00007fff0e375110 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007fff0e3761d0
R13: 00007fca3e70c3b9 R14: 000000000002096b R15: 000000000000000a
</TASK>
Modules linked in:
---[ end trace bf40b11beecf9437 ]---
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 c6 be a3 ff 0f 0b e8 bf be a3 ff 0f 0b e8 b8 be a3 ff 0f 0b e8 b1 be a3 ff <0f> 0b e8 aa be a3 ff 0f 0b 0f 1f 84 00 00 00 00 00 55 48 89 e5 41
RSP: 0018:ffffc900036e7af0 EFLAGS: 00010293
RAX: ffffffff81dc9e2f RBX: 0000000000000040 RCX: ffff88805cd75940
RDX: 0000000000000000 RSI: 0000000000000040 RDI: 0000000000000000
RBP: ffffc900036e7c20 R08: ffffffff81dc9dc4 R09: fffffbfff1f7ee42
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff1100e4eff6b R14: ffff88807277fb58 R15: ffff88807277fa80
FS: 0000555556efe480(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2f431000 CR3: 0000000055acb000 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 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