From: syzbot <syzbot+eaba5abe296837a640c0@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: [syzbot] [ext4?] KMSAN: uninit-value in ext4_inlinedir_to_tree
Date: Mon, 29 Apr 2024 09:05:32 -0700 [thread overview]
Message-ID: <000000000000440b0a06173e6ca8@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: e88c4cfcb7b8 Merge tag 'for-6.9-rc5-tag' of git://git.kern..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=12fbc980980000
kernel config: https://syzkaller.appspot.com/x/.config?x=776c05250f36d55c
dashboard link: https://syzkaller.appspot.com/bug?extid=eaba5abe296837a640c0
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=13e2cd27180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1741a028980000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/76771e00ba79/disk-e88c4cfc.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c957ed943a4f/vmlinux-e88c4cfc.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e719306ed8e3/bzImage-e88c4cfc.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/9d3c2a1fa449/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+eaba5abe296837a640c0@syzkaller.appspotmail.com
EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none.
EXT4-fs warning (device loop0): __ext4fs_dirhash:270: inode #12: comm syz-executor253: Siphash requires key
=====================================================
BUG: KMSAN: uninit-value in ext4_inlinedir_to_tree+0xde2/0x15a0 fs/ext4/inline.c:1415
ext4_inlinedir_to_tree+0xde2/0x15a0 fs/ext4/inline.c:1415
ext4_htree_fill_tree+0x1941/0x1cd0 fs/ext4/namei.c:1210
ext4_dx_readdir fs/ext4/dir.c:597 [inline]
ext4_readdir+0x4bbf/0x5b00 fs/ext4/dir.c:142
iterate_dir+0x688/0x870 fs/readdir.c:110
__do_sys_getdents64 fs/readdir.c:409 [inline]
__se_sys_getdents64+0x169/0x530 fs/readdir.c:394
__x64_sys_getdents64+0x96/0xe0 fs/readdir.c:394
x64_sys_call+0x343d/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:218
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
Local variable hinfo created at:
ext4_htree_fill_tree+0x52/0x1cd0 fs/ext4/namei.c:1185
ext4_dx_readdir fs/ext4/dir.c:597 [inline]
ext4_readdir+0x4bbf/0x5b00 fs/ext4/dir.c:142
CPU: 1 PID: 5020 Comm: syz-executor253 Not tainted 6.9.0-rc5-syzkaller-00042-ge88c4cfcb7b8 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
=====================================================
---
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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
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.
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
next reply other threads:[~2024-04-29 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 16:05 syzbot [this message]
2024-04-30 5:34 ` [syzbot] [ext4?] KMSAN: uninit-value in ext4_inlinedir_to_tree Edward Adam Davis
2024-04-30 7:35 ` syzbot
2024-04-30 7:13 ` [syzbot] " syzbot
2024-04-30 17:28 ` syzbot
[not found] <CABtBSaYXM0jR-HovWtxiX+KWhmL7M0aDwo6w488igKgkrCOyJg@mail.gmail.com>
2024-04-30 8:47 ` [syzbot] [ext4?] " syzbot
[not found] <CABtBSaZ-Qqb0ZB7CC1JMuO2pkT6YmRvibhb67x=QkOQMCdq8ow@mail.gmail.com>
2024-04-30 20:09 ` syzbot
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=000000000000440b0a06173e6ca8@google.com \
--to=syzbot+eaba5abe296837a640c0@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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.