[v6.1] WARNING in invalidate_bh_lrus_cpu

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 61fd484b2cf6 Linux 6.1.38
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1481e6eca80000
kernel config: https://syzkaller.appspot.com/x/.config?x=43a813745c91c8b3
dashboard link: https://syzkaller.appspot.com/bug?extid=2a59566d2d8d2b2393c0
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/f3fe059efa91/disk-61fd484b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b69bfadef125/vmlinux-61fd484b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8ecbf54ec382/bzImage-61fd484b.xz

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

------------[ cut here ]------------
VFS: brelse: Trying to free free buffer
WARNING: CPU: 0 PID: 7972 at fs/buffer.c:1145 __brelse fs/buffer.c:1145 [inline]
WARNING: CPU: 0 PID: 7972 at fs/buffer.c:1145 brelse include/linux/buffer_head.h:326 [inline]
WARNING: CPU: 0 PID: 7972 at fs/buffer.c:1145 __invalidate_bh_lrus fs/buffer.c:1380 [inline]
WARNING: CPU: 0 PID: 7972 at fs/buffer.c:1145 invalidate_bh_lrus_cpu+0x1b0/0x270 fs/buffer.c:1426
Modules linked in:
CPU: 0 PID: 7972 Comm: kworker/0:15 Not tainted 6.1.38-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023
Workqueue: mm_percpu_wq lru_add_drain_per_cpu
RIP: 0010:__brelse fs/buffer.c:1145 [inline]
RIP: 0010:brelse include/linux/buffer_head.h:326 [inline]
RIP: 0010:__invalidate_bh_lrus fs/buffer.c:1380 [inline]
RIP: 0010:invalidate_bh_lrus_cpu+0x1b0/0x270 fs/buffer.c:1426
Code: 48 89 df be 04 00 00 00 e8 6d e2 e0 ff f0 ff 0b eb 1a e8 03 7b 8a ff eb 1d e8 fc 7a 8a ff 48 c7 c7 60 b6 f9 8a e8 d0 e9 52 ff <0f> 0b 49 bf 00 00 00 00 00 fc ff df 48 8b 5c 24 10 43 80 3c 3e 00
RSP: 0018:ffffc900152a7b80 EFLAGS: 00010046
RAX: 9392a0c3a0af6e00 RBX: ffff88809a1a9060 RCX: ffff88807a16bb80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc900152a7c30 R08: ffffffff81524cae R09: ffffed1017304f1c
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: ffff8880b9835d38 R14: 1ffff11017306ba7 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f795e35dd58 CR3: 000000003d9c0000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
lru_add_and_bh_lrus_drain mm/swap.c:789 [inline]
lru_add_drain_per_cpu+0xf1/0x140 mm/swap.c:808
process_one_work+0x8aa/0x11f0 kernel/workqueue.c:2289
worker_thread+0xa5f/0x1210 kernel/workqueue.c:2436
kthread+0x26e/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</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.

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.