[v5.15] WARNING in __find_get_block

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c61bd26ae81a Linux 5.15.160
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10ecf261980000
kernel config: https://syzkaller.appspot.com/x/.config?x=235f0e81ca937c17
dashboard link: https://syzkaller.appspot.com/bug?extid=8a819fb457300c5b1f74
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/d61a97eef8b9/disk-c61bd26a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ab4908b4b59b/vmlinux-c61bd26a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d818fd46802b/bzImage-c61bd26a.xz

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

------------[ cut here ]------------
VFS: brelse: Trying to free free buffer
WARNING: CPU: 0 PID: 2926 at fs/buffer.c:1148 __brelse fs/buffer.c:1148 [inline]
WARNING: CPU: 0 PID: 2926 at fs/buffer.c:1148 brelse include/linux/buffer_head.h:325 [inline]
WARNING: CPU: 0 PID: 2926 at fs/buffer.c:1148 bh_lru_install fs/buffer.c:1262 [inline]
WARNING: CPU: 0 PID: 2926 at fs/buffer.c:1148 __find_get_block+0x110e/0x1350 fs/buffer.c:1312
Modules linked in:
CPU: 0 PID: 2926 Comm: jbd2/sda1-8 Not tainted 5.15.160-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
RIP: 0010:__brelse fs/buffer.c:1148 [inline]
RIP: 0010:brelse include/linux/buffer_head.h:325 [inline]
RIP: 0010:bh_lru_install fs/buffer.c:1262 [inline]
RIP: 0010:__find_get_block+0x110e/0x1350 fs/buffer.c:1312
Code: 58 d0 9a ff e8 53 50 a1 ff fb e9 e4 f1 ff ff e8 48 d0 9a ff e9 da f1 ff ff e8 3e d0 9a ff 48 c7 c7 a0 6b 97 8a e8 82 78 66 ff <0f> 0b e9 c2 f1 ff ff 44 89 f1 80 e1 07 38 c1 0f 8c 86 f2 ff ff 4c
RSP: 0018:ffffc9000b4e7440 EFLAGS: 00010246
RAX: 5853ee4556ed9400 RBX: 0000000000000000 RCX: ffff88807f140000
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc9000b4e75a0 R08: ffffffff8166860c R09: fffffbfff1bc8cce
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8880738f4cb0
R13: 1ffff11017346cbe R14: ffff888057bce0e8 R15: ffff88805850cd10
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555555d54978 CR3: 000000000c68e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__getblk_gfp+0x2d/0xaf0 fs/buffer.c:1332
__getblk include/linux/buffer_head.h:416 [inline]
jbd2_journal_get_descriptor_buffer+0x15a/0x440 fs/jbd2/journal.c:1022


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