WARNING in __brelse

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=163c5d04880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=9fe23c7ceaed0aea4b6b
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=127a683f080000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12bec750880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz

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

IPVS: ftp: loaded support on port[0] = 21
UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/09/12 12:00 (1000)
------------[ cut here ]------------
VFS: brelse: Trying to free free buffer
WARNING: CPU: 0 PID: 8108 at fs/buffer.c:1144 __brelse fs/buffer.c:1144 [inline]
WARNING: CPU: 0 PID: 8108 at fs/buffer.c:1144 __brelse+0x67/0xa0 fs/buffer.c:1138
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 8108 Comm: syz-executor328 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:__brelse fs/buffer.c:1144 [inline]
RIP: 0010:__brelse+0x67/0xa0 fs/buffer.c:1138
Code: 7c 04 84 d2 75 4e 44 8b 63 60 31 ff 44 89 e6 e8 bf 16 b2 ff 45 85 e4 75 1c e8 45 15 b2 ff 48 c7 c7 e0 1c 75 88 e8 1e 4d 42 06 <0f> 0b 5b 5d 41 5c e9 2e 15 b2 ff e8 29 15 b2 ff be 04 00 00 00 48
RSP: 0018:ffff8880952cfa38 EFLAGS: 00010086
RAX: 0000000000000000 RBX: ffff88808df92498 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed1012a59f39
RBP: ffff88808df924f8 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000005 R11: ffffffff8c66501b R12: 0000000000000000
R13: dffffc0000000000 R14: ffff8880ba0287e0 R15: ffffffff81b08270
brelse include/linux/buffer_head.h:297 [inline]
invalidate_bh_lru+0x90/0x140 fs/buffer.c:1385
on_each_cpu_mask+0xf7/0x240 kernel/smp.c:636
on_each_cpu_cond+0x12d/0x1c0 kernel/smp.c:684
kill_bdev fs/block_dev.c:85 [inline]
__blkdev_put+0x29e/0x870 fs/block_dev.c:1813
deactivate_locked_super+0x94/0x160 fs/super.c:329
deactivate_super+0x174/0x1a0 fs/super.c:360
cleanup_mnt+0x1a8/0x290 fs/namespace.c:1098
task_work_run+0x148/0x1c0 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xbf3/0x2be0 kernel/exit.c:870
do_group_exit+0x125/0x310 kernel/exit.c:967
__do_sys_exit_group kernel/exit.c:978 [inline]
__se_sys_exit_group kernel/exit.c:976 [inline]
__x64_sys_exit_group+0x3a/0x50 kernel/exit.c:976
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f639e97f889
Code: Bad RIP value.
RSP: 002b:00007ffe99912a18 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007f639e9f6330 RCX: 00007f639e97f889
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 0000000000000001 R08: ffffffffffffffc0 R09: 00007f639e9f0e40
R10: 00007f639e9f0e40 R11: 0000000000000246 R12: 00007f639e9f6330
R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000001
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches