From: syzbot <syzbot+efde959319469ff8d4d7@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hfs?] KMSAN: uninit-value in copy_name
Date: Mon, 20 May 2024 20:10:04 -0700 [thread overview]
Message-ID: <00000000000086f5b40618ee2716@google.com> (raw)
In-Reply-To: <tencent_CAB0DDA2192E4FE30DA8A5990DFD923A5D07@qq.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KMSAN: uninit-value in hfsplus_listxattr
loop0: detected capacity change from 0 to 1024
1sb: ffff888027b26c00, xnl: 762, hfsplus_listxattr
res: 1, cc: 121, op:ffff888027b26c12, len: 744, ustrlen: 0, hfsplus_uni2asc
=====================================================
BUG: KMSAN: uninit-value in string_nocheck lib/vsprintf.c:647 [inline]
BUG: KMSAN: uninit-value in string+0x36f/0x580 lib/vsprintf.c:728
string_nocheck lib/vsprintf.c:647 [inline]
string+0x36f/0x580 lib/vsprintf.c:728
vsnprintf+0x1b3b/0x2a00 lib/vsprintf.c:2824
vprintk_store+0x414/0x13f0 kernel/printk/printk.c:2228
vprintk_emit+0x1e4/0xbc0 kernel/printk/printk.c:2329
vprintk_default+0x3e/0x50 kernel/printk/printk.c:2363
vprintk+0xee/0xf0 kernel/printk/printk_safe.c:45
_printk+0x157/0x190 kernel/printk/printk.c:2373
hfsplus_listxattr+0xb53/0x1740 fs/hfsplus/xattr.c:743
vfs_listxattr fs/xattr.c:493 [inline]
listxattr+0x1f3/0x6b0 fs/xattr.c:840
path_listxattr fs/xattr.c:864 [inline]
__do_sys_listxattr fs/xattr.c:876 [inline]
__se_sys_listxattr fs/xattr.c:873 [inline]
__x64_sys_listxattr+0x16b/0x2f0 fs/xattr.c:873
x64_sys_call+0x2ba0/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:195
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcf/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:3877 [inline]
slab_alloc_node mm/slub.c:3918 [inline]
kmalloc_trace+0x57b/0xbe0 mm/slub.c:4065
kmalloc include/linux/slab.h:628 [inline]
hfsplus_listxattr+0x4b6/0x1740 fs/hfsplus/xattr.c:699
vfs_listxattr fs/xattr.c:493 [inline]
listxattr+0x1f3/0x6b0 fs/xattr.c:840
path_listxattr fs/xattr.c:864 [inline]
__do_sys_listxattr fs/xattr.c:876 [inline]
__se_sys_listxattr fs/xattr.c:873 [inline]
__x64_sys_listxattr+0x16b/0x2f0 fs/xattr.c:873
x64_sys_call+0x2ba0/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:195
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
CPU: 1 PID: 5518 Comm: syz-executor.0 Not tainted 6.9.0-syzkaller-01768-ga5131c3fdf26-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
=====================================================
Tested on:
commit: a5131c3f Merge tag 'x86-shstk-2024-05-13' of git://git..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=14dc197c980000
kernel config: https://syzkaller.appspot.com/x/.config?x=64e100d74625a6a5
dashboard link: https://syzkaller.appspot.com/bug?extid=efde959319469ff8d4d7
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1234ddf0980000
next prev parent reply other threads:[~2024-05-21 3:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-18 9:21 [syzbot] [hfs?] KMSAN: uninit-value in copy_name syzbot
2024-05-21 0:40 ` Edward Adam Davis
2024-05-21 3:10 ` syzbot [this message]
2024-05-21 3:45 ` Edward Adam Davis
2024-05-21 4:21 ` syzbot
2024-05-21 5:21 ` [PATCH] hfsplus: fix " Edward Adam Davis
2024-07-04 13:36 ` Dmitry Vyukov
2024-07-05 13:46 ` Edward Adam Davis
2024-07-05 21:20 ` Kees Cook
2024-07-06 7:20 ` Christian Brauner
2024-07-08 6:52 ` Dmitry Vyukov
2024-07-08 19:20 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00000000000086f5b40618ee2716@google.com \
--to=syzbot+efde959319469ff8d4d7@syzkaller.appspotmail.com \
--cc=eadavis@qq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.