From: syzbot <syzbot+394aa8a792cb99dbc837@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, glider@google.com,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: [syzbot] [ext4?] KMSAN: uninit-value in htree_dirblock_to_tree
Date: Tue, 03 Jan 2023 02:58:38 -0800 [thread overview]
Message-ID: <00000000000034388605f159f31e@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 5c6259d6d19f kmsan: fix memcpy tests
git tree: https://github.com/google/kmsan.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=1343a1e4480000
kernel config: https://syzkaller.appspot.com/x/.config?x=e2f77da22508204e
dashboard link: https://syzkaller.appspot.com/bug?extid=394aa8a792cb99dbc837
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project.git 610139d2d9ce6746b3c617fb3e2f7886272d26ff), GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: i386
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/76b6594632b8/disk-5c6259d6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/81a2113c440e/vmlinux-5c6259d6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fd12d098edab/bzImage-5c6259d6.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+394aa8a792cb99dbc837@syzkaller.appspotmail.com
[EXT4 FS bs=2048, gc=1, bpg=16384, ipg=32, mo=e000e01c, mo2=0002]
System zones: 0-11
EXT4-fs (loop4): mounted filesystem without journal. Quota mode: none.
=====================================================
BUG: KMSAN: uninit-value in htree_dirblock_to_tree+0x101b/0x1710 fs/ext4/namei.c:1116
htree_dirblock_to_tree+0x101b/0x1710 fs/ext4/namei.c:1116
ext4_htree_fill_tree+0x1ac9/0x1cc0 fs/ext4/namei.c:1204
ext4_dx_readdir fs/ext4/dir.c:597 [inline]
ext4_readdir+0x53cd/0x6450 fs/ext4/dir.c:142
iterate_dir+0x3e5/0x9b0
__do_compat_sys_getdents fs/readdir.c:537 [inline]
__se_compat_sys_getdents+0x182/0x560 fs/readdir.c:522
__ia32_compat_sys_getdents+0x8f/0xd0 fs/readdir.c:522
do_syscall_32_irqs_on arch/x86/entry/common.c:112 [inline]
__do_fast_syscall_32+0xa2/0x100 arch/x86/entry/common.c:178
do_fast_syscall_32+0x33/0x70 arch/x86/entry/common.c:203
do_SYSENTER_32+0x1b/0x20 arch/x86/entry/common.c:246
entry_SYSENTER_compat_after_hwframe+0x70/0x82
Local variable hinfo created at:
ext4_htree_fill_tree+0x5f/0x1cc0 fs/ext4/namei.c:1170
ext4_dx_readdir fs/ext4/dir.c:597 [inline]
ext4_readdir+0x53cd/0x6450 fs/ext4/dir.c:142
CPU: 0 PID: 6235 Comm: syz-executor.4 Not tainted 6.1.0-syzkaller-64311-g5c6259d6d19f #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
=====================================================
---
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@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
reply other threads:[~2023-01-03 10:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=00000000000034388605f159f31e@google.com \
--to=syzbot+394aa8a792cb99dbc837@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=glider@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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.