[moderation] [fs?] WARNING in invalidate_bh_lrus_cpu (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 85a2dd7d7c81 Add linux-next specific files for 20241125
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=125665c0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e348a4873516af92
dashboard link: https://syzkaller.appspot.com/bug?extid=3c249314730382052089
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [bra...@kernel.org ja...@suse.cz linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/eff72ae97118/disk-85a2dd7d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/18f336c941c2/vmlinux-85a2dd7d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ddb67e7b7257/bzImage-85a2dd7d.xz

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

------------[ cut here ]------------
VFS: brelse: Trying to free free buffer
WARNING: CPU: 1 PID: 46 at fs/buffer.c:1229 __brelse fs/buffer.c:1229 [inline]
WARNING: CPU: 1 PID: 46 at fs/buffer.c:1229 brelse include/linux/buffer_head.h:324 [inline]
WARNING: CPU: 1 PID: 46 at fs/buffer.c:1229 __invalidate_bh_lrus fs/buffer.c:1498 [inline]
WARNING: CPU: 1 PID: 46 at fs/buffer.c:1229 invalidate_bh_lrus_cpu+0x1ba/0x280 fs/buffer.c:1544
Modules linked in:
CPU: 1 UID: 0 PID: 46 Comm: kworker/1:1 Not tainted 6.12.0-next-20241125-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: mm_percpu_wq lru_add_drain_per_cpu
RIP: 0010:__brelse fs/buffer.c:1229 [inline]
RIP: 0010:brelse include/linux/buffer_head.h:324 [inline]
RIP: 0010:__invalidate_bh_lrus fs/buffer.c:1498 [inline]
RIP: 0010:invalidate_bh_lrus_cpu+0x1ba/0x280 fs/buffer.c:1544
Code: df be 04 00 00 00 e8 c5 eb da ff f0 ff 0b eb 1e e8 5b f8 6f ff eb 21 e8 54 f8 6f ff 90 48 c7 c7 20 e1 18 8c e8 d7 96 30 ff 90 <0f> 0b 90 90 49 bf 00 00 00 00 00 fc ff df 48 8b 5c 24 10 43 80 3c
RSP: 0018:ffffc90000b67ac0 EFLAGS: 00010046
RAX: 49145d4b45237b00 RBX: ffff8880611e3c28 RCX: ffff888020ec8000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90000b67b78 R08: ffffffff81601b32 R09: fffffbfff1cfa218
R10: dffffc0000000000 R11: fffffbfff1cfa218 R12: 0000000000000000
R13: ffff8880b8739838 R14: 1ffff110170e7307 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f46763e96e8 CR3: 0000000065ae4000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
lru_add_and_bh_lrus_drain mm/swap.c:714 [inline]
lru_add_drain_per_cpu+0x21a/0x3f0 mm/swap.c:733
process_one_work kernel/workqueue.c:3229 [inline]
process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310
worker_thread+0x870/0xd30 kernel/workqueue.c:3391
kthread+0x2f0/0x390 kernel/kthread.c:389
ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
</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 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

[Dmitry Vyukov]

#syz dup: WARNING in invalidate_bh_lru

See:
https://github.com/google/syzkaller/issues/5555#issuecomment-2511129887

Though, there is some mess in the "WARNING in invalidate_bh_lru" bug,
it looks like several root causes glued together since the original
bug wasn't closed:
https://syzkaller.appspot.com/bug?extid=9743a41f74f00e50fc77

> --
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-upstream-m...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/674596d6.050a0220.21d33d.0014.GAE%40google.com.