[v6.1] WARNING in __brelse

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: a3eb3a74aa8c Linux 6.1.80
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=163516ee180000
kernel config: https://syzkaller.appspot.com/x/.config?x=40fd5f1c69352c2d
dashboard link: https://syzkaller.appspot.com/bug?extid=bcb509d47bddc5f9a0be
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/fcf176340788/disk-a3eb3a74.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/31d4ae9bb2ff/vmlinux-a3eb3a74.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cb907876b80a/Image-a3eb3a74.gz.xz

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

------------[ cut here ]------------
VFS: brelse: Trying to free free buffer
WARNING: CPU: 1 PID: 9788 at fs/buffer.c:1145 __brelse+0x84/0xd8 fs/buffer.c:1145
Modules linked in:
CPU: 1 PID: 9788 Comm: syz-executor.2 Not tainted 6.1.80-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __brelse+0x84/0xd8 fs/buffer.c:1145
lr : __brelse+0x84/0xd8 fs/buffer.c:1145
sp : ffff8000211c7620
x29: ffff8000211c7620 x28: ffff8000211c7780 x27: ffff000122492c18
x26: ffff8000211c77d0 x25: 1ffff00004238f04 x24: ffff000122492d38
x23: ffff700004238edc x22: 1ffff00004238ee8 x21: ffff0001254a2d98
x20: 0000000000000000 x19: ffff0001254a2df8 x18: 1fffe00036870176
x17: ffff80001581d000 x16: ffff800008304ad0 x15: ffff0001b4380bbc
x14: 1ffff00002b040b0 x13: dfff800000000000 x12: 0000000000000003
x11: 0000000000ff0100 x10: 0000000000000003 x9 : 76801629cb0e8400
x8 : 76801629cb0e8400 x7 : ffff80000827c520 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000006 x1 : ffff80001229c6e0 x0 : ffff80019ec0f000
Call trace:
__brelse+0x84/0xd8 fs/buffer.c:1145
brelse include/linux/buffer_head.h:326 [inline]
udf_rename+0xd1c/0x10b0 fs/udf/namei.c:1214
vfs_rename+0xac8/0xe04 fs/namei.c:4876
do_renameat2+0x9ec/0xe64 fs/namei.c:5029
__do_sys_renameat2 fs/namei.c:5062 [inline]
__se_sys_renameat2 fs/namei.c:5059 [inline]
__arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5059
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
irq event stamp: 7344
hardirqs last enabled at (7343): [<ffff80000827c5c0>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1366 [inline]
hardirqs last enabled at (7343): [<ffff80000827c5c0>] finish_lock_switch+0xbc/0x1e8 kernel/sched/core.c:5004
hardirqs last disabled at (7344): [<ffff800012141c04>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (7336): [<ffff800008020d7c>] softirq_handle_end kernel/softirq.c:414 [inline]
softirqs last enabled at (7336): [<ffff800008020d7c>] __do_softirq+0xc1c/0xe38 kernel/softirq.c:600
softirqs last disabled at (7247): [<ffff80000802a99c>] ____do_softirq+0x14/0x20 arch/arm64/kernel/irq.c:80
---[ end trace 0000000000000000 ]---


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