[<prev] [next>] [day] [month] [year] [list]
Message-ID: <672b1213.050a0220.2a847.1b9d.GAE@google.com>
Date: Tue, 05 Nov 2024 22:52:03 -0800
From: syzbot <syzbot+d395b0c369e492a17530@...kaller.appspotmail.com>
To: linux-kernel@...r.kernel.org, sarvesh20123@...il.com,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [hfs?] KMSAN: uninit-value in __hfs_ext_cache_extent (2)
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KMSAN: uninit-value in __hfs_ext_cache_extent
loop0: detected capacity change from 0 to 64
=====================================================
BUG: KMSAN: uninit-value in __hfs_ext_read_extent fs/hfs/extent.c:160 [inline]
BUG: KMSAN: uninit-value in __hfs_ext_cache_extent+0x69f/0x7e0 fs/hfs/extent.c:179
__hfs_ext_read_extent fs/hfs/extent.c:160 [inline]
__hfs_ext_cache_extent+0x69f/0x7e0 fs/hfs/extent.c:179
hfs_ext_read_extent fs/hfs/extent.c:202 [inline]
hfs_get_block+0x73e/0xf60 fs/hfs/extent.c:366
__block_write_begin_int+0xa6b/0x2f80 fs/buffer.c:2121
block_write_begin fs/buffer.c:2231 [inline]
cont_write_begin+0xf82/0x1940 fs/buffer.c:2582
hfs_write_begin+0x85/0x120 fs/hfs/inode.c:52
cont_expand_zero fs/buffer.c:2509 [inline]
cont_write_begin+0x32f/0x1940 fs/buffer.c:2572
hfs_write_begin+0x85/0x120 fs/hfs/inode.c:52
hfs_file_truncate+0x1a5/0xd30 fs/hfs/extent.c:494
hfs_inode_setattr+0x998/0xab0 fs/hfs/inode.c:654
notify_change+0x1a8e/0x1b80 fs/attr.c:503
do_truncate+0x22a/0x2b0 fs/open.c:65
vfs_truncate+0x5d4/0x680 fs/open.c:111
do_sys_truncate+0x104/0x240 fs/open.c:134
__do_sys_truncate fs/open.c:146 [inline]
__se_sys_truncate fs/open.c:144 [inline]
__x64_sys_truncate+0x6c/0xa0 fs/open.c:144
x64_sys_call+0x2ce3/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:77
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Uninit was created at:
slab_post_alloc_hook mm/slub.c:4091 [inline]
slab_alloc_node mm/slub.c:4134 [inline]
__do_kmalloc_node mm/slub.c:4263 [inline]
__kmalloc_noprof+0x661/0xf30 mm/slub.c:4276
kmalloc_noprof include/linux/slab.h:882 [inline]
hfs_find_init+0x91/0x250 fs/hfs/bfind.c:21
hfs_ext_read_extent fs/hfs/extent.c:200 [inline]
hfs_get_block+0x699/0xf60 fs/hfs/extent.c:366
__block_write_begin_int+0xa6b/0x2f80 fs/buffer.c:2121
block_write_begin fs/buffer.c:2231 [inline]
cont_write_begin+0xf82/0x1940 fs/buffer.c:2582
hfs_write_begin+0x85/0x120 fs/hfs/inode.c:52
cont_expand_zero fs/buffer.c:2509 [inline]
cont_write_begin+0x32f/0x1940 fs/buffer.c:2572
hfs_write_begin+0x85/0x120 fs/hfs/inode.c:52
hfs_file_truncate+0x1a5/0xd30 fs/hfs/extent.c:494
hfs_inode_setattr+0x998/0xab0 fs/hfs/inode.c:654
notify_change+0x1a8e/0x1b80 fs/attr.c:503
do_truncate+0x22a/0x2b0 fs/open.c:65
vfs_truncate+0x5d4/0x680 fs/open.c:111
do_sys_truncate+0x104/0x240 fs/open.c:134
__do_sys_truncate fs/open.c:146 [inline]
__se_sys_truncate fs/open.c:144 [inline]
__x64_sys_truncate+0x6c/0xa0 fs/open.c:144
x64_sys_call+0x2ce3/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:77
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
CPU: 0 UID: 0 PID: 6025 Comm: syz.0.15 Not tainted 6.12.0-rc6-syzkaller-00077-g2e1b3cc9d7f7-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
=====================================================
Tested on:
commit: 2e1b3cc9 Merge tag 'arm-fixes-6.12-2' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14cbf587980000
kernel config: https://syzkaller.appspot.com/x/.config?x=b8a4f4c5365f96b
dashboard link: https://syzkaller.appspot.com/bug?extid=d395b0c369e492a17530
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=15185d5f980000
Powered by blists - more mailing lists