[v6.1] WARNING in invalidate_bh_lru (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 082280fe94a0 Linux 6.1.57
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1407022e680000
kernel config: https://syzkaller.appspot.com/x/.config?x=2fcfda4f62e1716c
dashboard link: https://syzkaller.appspot.com/bug?extid=af4e12eac13350853897
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/13811dd7bcb9/disk-082280fe.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/78b9e829ec6f/vmlinux-082280fe.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2d5fc66b2352/bzImage-082280fe.xz

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

------------[ cut here ]------------
VFS: brelse: Trying to free free buffer
WARNING: CPU: 1 PID: 3595 at fs/buffer.c:1145 __brelse fs/buffer.c:1145 [inline]
WARNING: CPU: 1 PID: 3595 at fs/buffer.c:1145 brelse include/linux/buffer_head.h:326 [inline]
WARNING: CPU: 1 PID: 3595 at fs/buffer.c:1145 __invalidate_bh_lrus fs/buffer.c:1380 [inline]
WARNING: CPU: 1 PID: 3595 at fs/buffer.c:1145 invalidate_bh_lru+0xf8/0x1a0 fs/buffer.c:1393
Modules linked in:
CPU: 1 PID: 3595 Comm: syz-executor.4 Not tainted 6.1.57-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/06/2023
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_lru+0xf8/0x1a0 fs/buffer.c:1393
Code: 00 e8 2c c0 e0 ff f0 ff 0b eb 21 e8 12 98 89 ff 41 80 3c 2e 00 75 26 eb 2c e8 04 98 89 ff 48 c7 c7 20 ce f9 8a e8 28 92 51 ff <0f> 0b 48 bd 00 00 00 00 00 fc ff df 41 80 3c 2e 00 74 08 4c 89 ff
RSP: 0018:ffffc90003d4f848 EFLAGS: 00010046
RAX: fdaf650fac6d8e00 RBX: ffff888074f817a0 RCX: ffff888015f40000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff81526dae R09: ffffed1017324f1c
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8880b9935d38
R13: 0000000000000030 R14: 1ffff11017326bad R15: ffff8880b9935d68
FS: 0000555556e47480(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f07c17aeff0 CR3: 000000003eb10000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
smp_call_function_many_cond+0x1cda/0x33d0 kernel/smp.c:978
on_each_cpu_cond_mask+0x3b/0x80 kernel/smp.c:1155
kill_bdev block/bdev.c:75 [inline]
blkdev_flush_mapping+0x14a/0x2b0 block/bdev.c:662
blkdev_put_whole block/bdev.c:693 [inline]
blkdev_put+0x4c0/0x750 block/bdev.c:953
deactivate_locked_super+0xa0/0x110 fs/super.c:332
cleanup_mnt+0x490/0x520 fs/namespace.c:1186
task_work_run+0x246/0x300 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xde/0x100 kernel/entry/common.c:171
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:297
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f226887de17
Code: b0 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 b0 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffdc62a29d8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f226887de17
RDX: 0000000000000000 RSI: 000000000000000a RDI: 00007ffdc62a2a90
RBP: 00007ffdc62a2a90 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffdc62a3b50
R13: 00007f22688c73b9 R14: 0000000000107bc4 R15: 0000000000000003
</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 overwrite 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]

syzbot has found a reproducer for the following issue on:

HEAD commit: 082280fe94a0 Linux 6.1.57
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=16fd1131680000

kernel config: https://syzkaller.appspot.com/x/.config?x=2fcfda4f62e1716c
dashboard link: https://syzkaller.appspot.com/bug?extid=af4e12eac13350853897
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13539ae5680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10bf41f9680000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/13811dd7bcb9/disk-082280fe.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/78b9e829ec6f/vmlinux-082280fe.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2d5fc66b2352/bzImage-082280fe.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/25e5ec9d86df/mount_0.gz

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

loop0: detected capacity change from 0 to 2048
UDF-fs: error (device loop0): udf_process_sequence: Primary Volume Descriptor not found!
UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000)

------------[ cut here ]------------
VFS: brelse: Trying to free free buffer

WARNING: CPU: 0 PID: 3546 at fs/buffer.c:1145 __brelse fs/buffer.c:1145 [inline]
WARNING: CPU: 0 PID: 3546 at fs/buffer.c:1145 brelse include/linux/buffer_head.h:326 [inline]
WARNING: CPU: 0 PID: 3546 at fs/buffer.c:1145 __invalidate_bh_lrus fs/buffer.c:1380 [inline]
WARNING: CPU: 0 PID: 3546 at fs/buffer.c:1145 invalidate_bh_lru+0xf8/0x1a0 fs/buffer.c:1393
Modules linked in:
CPU: 0 PID: 3546 Comm: syz-executor793 Not tainted 6.1.57-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/06/2023
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_lru+0xf8/0x1a0 fs/buffer.c:1393
Code: 00 e8 2c c0 e0 ff f0 ff 0b eb 21 e8 12 98 89 ff 41 80 3c 2e 00 75 26 eb 2c e8 04 98 89 ff 48 c7 c7 20 ce f9 8a e8 28 92 51 ff <0f> 0b 48 bd 00 00 00 00 00 fc ff df 41 80 3c 2e 00 74 08 4c 89 ff

RSP: 0018:ffffc90003a3f6c8 EFLAGS: 00010046
RAX: c2aa8b301ef35b00 RBX: ffff888072ed6df8 RCX: ffff888026185940

RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000

RBP: 0000000000000000 R08: ffffffff81526dae R09: ffffed1017304f1c
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8880b9835d38
R13: 0000000000000010 R14: 1ffff11017306ba9 R15: ffff8880b9835d48
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007f71b200ced8 CR3: 000000007ec93000 CR4: 00000000003506f0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
smp_call_function_many_cond+0x1cda/0x33d0 kernel/smp.c:978
on_each_cpu_cond_mask+0x3b/0x80 kernel/smp.c:1155
kill_bdev block/bdev.c:75 [inline]
blkdev_flush_mapping+0x14a/0x2b0 block/bdev.c:662
blkdev_put_whole block/bdev.c:693 [inline]
blkdev_put+0x4c0/0x750 block/bdev.c:953
deactivate_locked_super+0xa0/0x110 fs/super.c:332
cleanup_mnt+0x490/0x520 fs/namespace.c:1186
task_work_run+0x246/0x300 kernel/task_work.c:179

exit_task_work include/linux/task_work.h:38 [inline]
do_exit+0xa73/0x26a0 kernel/exit.c:869
do_group_exit+0x202/0x2b0 kernel/exit.c:1019
__do_sys_exit_group kernel/exit.c:1030 [inline]
__se_sys_exit_group kernel/exit.c:1028 [inline]
__x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1028
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f4bb4dbb649
Code: Unable to access opcode bytes at 0x7f4bb4dbb61f.
RSP: 002b:00007fff6937c828 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f4bb4dbb649
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 00007f4bb4e46370 R08: ffffffffffffffb0 R09: 000000ff00ff4650
R10: 0000000000000c17 R11: 0000000000000246 R12: 00007f4bb4e46370
R13: 0000000000000000 R14: 00007f4bb4e470e0 R15: 00007f4bb4d863a0
</TASK>


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

[syzbot]

syzbot suspects this issue could be fixed by backporting the following commit:

commit e9109a92d2a95889498bed3719cd2318892171a2
git tree: upstream
Author: Jan Kara <ja...@suse.cz>
Date: Thu Oct 6 14:41:23 2022 +0000

udf: Convert udf_rename() to new directory iteration code

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=121917cae80000

kernel config: https://syzkaller.appspot.com/x/.config?x=2fcfda4f62e1716c
dashboard link: https://syzkaller.appspot.com/bug?extid=af4e12eac13350853897

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13539ae5680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10bf41f9680000

Please keep in mind that other backports might be required as well.

For information about bisection process see: https://goo.gl/tpsmEJ#bisection