linux-kernel - [syzbot] [udf?] WARNING in __find_get

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <6741d52e.050a0220.1cc393.0010.GAE@google.com>
Date: Sat, 23 Nov 2024 05:14:22 -0800
From: syzbot <syzbot+3c9f079f8fb1d7d331be@...kaller.appspotmail.com>
To: hirofumi@...l.parknet.co.jp, jack@...e.com, linux-kernel@...r.kernel.org, 
	syzkaller-bugs@...glegroups.com
Subject: [syzbot] [udf?] WARNING in __find_get_block (2)

Hello,

syzbot found the following issue on:

HEAD commit:    cfba9f07a1d6 Add linux-next specific files for 20241122
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=178636e8580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=45719eec4c74e6ba
dashboard link: https://syzkaller.appspot.com/bug?extid=3c9f079f8fb1d7d331be
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/be35516c7ba5/disk-cfba9f07.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/70295210dc7d/vmlinux-cfba9f07.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8b5d044072ee/bzImage-cfba9f07.xz

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

------------[ cut here ]------------
VFS: brelse: Trying to free free buffer
WARNING: CPU: 0 PID: 12266 at fs/buffer.c:1229 __brelse fs/buffer.c:1229 [inline]
WARNING: CPU: 0 PID: 12266 at fs/buffer.c:1229 brelse include/linux/buffer_head.h:324 [inline]
WARNING: CPU: 0 PID: 12266 at fs/buffer.c:1229 bh_lru_install fs/buffer.c:1346 [inline]
WARNING: CPU: 0 PID: 12266 at fs/buffer.c:1229 __find_get_block+0x109d/0x1150 fs/buffer.c:1400
Modules linked in:
CPU: 0 UID: 0 PID: 12266 Comm: syz.6.1269 Not tainted 6.12.0-next-20241122-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:__brelse fs/buffer.c:1229 [inline]
RIP: 0010:brelse include/linux/buffer_head.h:324 [inline]
RIP: 0010:bh_lru_install fs/buffer.c:1346 [inline]
RIP: 0010:__find_get_block+0x109d/0x1150 fs/buffer.c:1400
Code: 67 3e 9a e8 05 20 db ff e9 1b f7 ff ff e8 4b 2f 70 ff e9 87 f7 ff ff e8 41 2f 70 ff 90 48 c7 c7 20 e1 18 8c e8 c4 cd 30 ff 90 <0f> 0b 90 90 e9 6b f7 ff ff e8 25 2f 70 ff 48 c7 c7 c0 cf a8 8e 4c
RSP: 0018:ffffc90005d974a0 EFLAGS: 00010246
RAX: 678501cd73c0d900 RBX: 0000000000000000 RCX: 0000000000080000
RDX: ffffc9000fba1000 RSI: 0000000000011153 RDI: 0000000000011154
RBP: ffffc90005d975d0 R08: ffffffff81601b32 R09: fffffbfff1cfa218
R10: dffffc0000000000 R11: fffffbfff1cfa218 R12: ffff88807bcf69f8
R13: ffff8880b86398b0 R14: ffff888034c6d828 R15: ffff88805ae4f6b8
FS:  00007fbd27ae76c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30210ff8 CR3: 0000000067510000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 bdev_getblk+0x33/0x550 fs/buffer.c:1425
 __bread_gfp+0x86/0x400 fs/buffer.c:1485
 sb_bread include/linux/buffer_head.h:346 [inline]
 fat__get_entry fs/fat/dir.c:100 [inline]
 fat_get_entry+0x78f/0xae0 fs/fat/dir.c:128
 fat_get_short_entry fs/fat/dir.c:885 [inline]
 fat_subdirs+0x227/0x3c0 fs/fat/dir.c:951
 fat_read_root+0x5e5/0x8b0 fs/fat/inode.c:1345
 fat_fill_super+0x205f/0x35a0 fs/fat/inode.c:1814
 get_tree_bdev_flags+0x48c/0x5c0 fs/super.c:1636
 vfs_get_tree+0x90/0x2b0 fs/super.c:1814
 do_new_mount+0x2be/0xb40 fs/namespace.c:3507
 do_mount fs/namespace.c:3847 [inline]
 __do_sys_mount fs/namespace.c:4057 [inline]
 __se_sys_mount+0x2d6/0x3c0 fs/namespace.c:4034
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fbd26d7ffba
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fbd27ae6e68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fbd27ae6ef0 RCX: 00007fbd26d7ffba
RDX: 00000000200000c0 RSI: 0000000020000000 RDI: 00007fbd27ae6eb0
RBP: 00000000200000c0 R08: 00007fbd27ae6ef0 R09: 0000000002010000
R10: 0000000002010000 R11: 0000000000000246 R12: 0000000020000000
R13: 00007fbd27ae6eb0 R14: 0000000000000336 R15: 0000000020000640
 </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 syzkaller@...glegroups.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