From: syzbot <syzbot+9ca499bb57a2b9e4c652@syzkaller.appspotmail.com>
To: glider@google.com, jack@suse.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] KMSAN: uninit-value in udf_evict_inode (2)
Date: Mon, 13 Dec 2021 07:28:26 -0800 [thread overview]
Message-ID: <0000000000005affb705d308b986@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 8b936c96768e kmsan: core: remove the accidentally committe..
git tree: https://github.com/google/kmsan.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=12c9f1beb00000
kernel config: https://syzkaller.appspot.com/x/.config?x=e00a8959fdd3f3e8
dashboard link: https://syzkaller.appspot.com/bug?extid=9ca499bb57a2b9e4c652
compiler: clang version 14.0.0 (git@github.com:llvm/llvm-project.git 0996585c8e3b3d409494eb5f1cad714b9e1f7fb5), GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: i386
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9ca499bb57a2b9e4c652@syzkaller.appspotmail.com
UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2020/09/19 18:44 (1000)
=====================================================
BUG: KMSAN: uninit-value in udf_evict_inode+0x2b6/0x830 fs/udf/inode.c:148
udf_evict_inode+0x2b6/0x830 fs/udf/inode.c:148
evict+0x4f7/0xdc0 fs/inode.c:590
iput_final fs/inode.c:1670 [inline]
iput+0xc5d/0x1110 fs/inode.c:1696
udf_new_inode+0x5d2/0x16e0 fs/udf/ialloc.c:89
udf_tmpfile+0x7e/0x2d0 fs/udf/namei.c:631
vfs_tmpfile+0x2d9/0x5b0 fs/namei.c:3474
do_tmpfile+0x29f/0x6c0 fs/namei.c:3509
path_openat+0x4116/0x5dd0 fs/namei.c:3550
do_filp_open+0x306/0x760 fs/namei.c:3586
do_sys_openat2+0x263/0x8f0 fs/open.c:1212
do_sys_open fs/open.c:1228 [inline]
__do_compat_sys_openat fs/open.c:1288 [inline]
__se_compat_sys_openat fs/open.c:1286 [inline]
__ia32_compat_sys_openat+0x353/0x3c0 fs/open.c:1286
do_syscall_32_irqs_on arch/x86/entry/common.c:114 [inline]
__do_fast_syscall_32+0x96/0xf0 arch/x86/entry/common.c:180
do_fast_syscall_32+0x34/0x70 arch/x86/entry/common.c:205
do_SYSENTER_32+0x1b/0x20 arch/x86/entry/common.c:248
entry_SYSENTER_compat_after_hwframe+0x4d/0x5c
Uninit was stored to memory at:
udf_new_inode+0xac1/0x16e0 fs/udf/ialloc.c:67
udf_tmpfile+0x7e/0x2d0 fs/udf/namei.c:631
vfs_tmpfile+0x2d9/0x5b0 fs/namei.c:3474
do_tmpfile+0x29f/0x6c0 fs/namei.c:3509
path_openat+0x4116/0x5dd0 fs/namei.c:3550
do_filp_open+0x306/0x760 fs/namei.c:3586
do_sys_openat2+0x263/0x8f0 fs/open.c:1212
do_sys_open fs/open.c:1228 [inline]
__do_compat_sys_openat fs/open.c:1288 [inline]
__se_compat_sys_openat fs/open.c:1286 [inline]
__ia32_compat_sys_openat+0x353/0x3c0 fs/open.c:1286
do_syscall_32_irqs_on arch/x86/entry/common.c:114 [inline]
__do_fast_syscall_32+0x96/0xf0 arch/x86/entry/common.c:180
do_fast_syscall_32+0x34/0x70 arch/x86/entry/common.c:205
do_SYSENTER_32+0x1b/0x20 arch/x86/entry/common.c:248
entry_SYSENTER_compat_after_hwframe+0x4d/0x5c
Uninit was stored to memory at:
udf_alloc_inode+0x28a/0x2c0 fs/udf/super.c:149
alloc_inode fs/inode.c:235 [inline]
new_inode_pseudo+0xa6/0x5a0 fs/inode.c:944
new_inode+0x5a/0x3c0 fs/inode.c:973
udf_new_inode+0x139/0x16e0 fs/udf/ialloc.c:60
udf_tmpfile+0x7e/0x2d0 fs/udf/namei.c:631
vfs_tmpfile+0x2d9/0x5b0 fs/namei.c:3474
do_tmpfile+0x29f/0x6c0 fs/namei.c:3509
path_openat+0x4116/0x5dd0 fs/namei.c:3550
do_filp_open+0x306/0x760 fs/namei.c:3586
do_sys_openat2+0x263/0x8f0 fs/open.c:1212
do_sys_open fs/open.c:1228 [inline]
__do_compat_sys_openat fs/open.c:1288 [inline]
__se_compat_sys_openat fs/open.c:1286 [inline]
__ia32_compat_sys_openat+0x353/0x3c0 fs/open.c:1286
do_syscall_32_irqs_on arch/x86/entry/common.c:114 [inline]
__do_fast_syscall_32+0x96/0xf0 arch/x86/entry/common.c:180
do_fast_syscall_32+0x34/0x70 arch/x86/entry/common.c:205
do_SYSENTER_32+0x1b/0x20 arch/x86/entry/common.c:248
entry_SYSENTER_compat_after_hwframe+0x4d/0x5c
Uninit was created at:
__alloc_pages+0xbc7/0x10a0 mm/page_alloc.c:5409
alloc_pages+0x8a5/0xb80
alloc_slab_page mm/slub.c:1810 [inline]
allocate_slab+0x287/0x1c20 mm/slub.c:1947
new_slab mm/slub.c:2010 [inline]
___slab_alloc+0xbdf/0x1e90 mm/slub.c:3039
__slab_alloc mm/slub.c:3126 [inline]
slab_alloc_node mm/slub.c:3217 [inline]
slab_alloc mm/slub.c:3259 [inline]
kmem_cache_alloc+0xbb3/0x11c0 mm/slub.c:3264
udf_alloc_inode+0x60/0x2c0 fs/udf/super.c:139
alloc_inode fs/inode.c:235 [inline]
new_inode_pseudo+0xa6/0x5a0 fs/inode.c:944
new_inode+0x5a/0x3c0 fs/inode.c:973
udf_new_inode+0x139/0x16e0 fs/udf/ialloc.c:60
udf_tmpfile+0x7e/0x2d0 fs/udf/namei.c:631
vfs_tmpfile+0x2d9/0x5b0 fs/namei.c:3474
do_tmpfile+0x29f/0x6c0 fs/namei.c:3509
path_openat+0x4116/0x5dd0 fs/namei.c:3550
do_filp_open+0x306/0x760 fs/namei.c:3586
do_sys_openat2+0x263/0x8f0 fs/open.c:1212
do_sys_open fs/open.c:1228 [inline]
__do_compat_sys_openat fs/open.c:1288 [inline]
__se_compat_sys_openat fs/open.c:1286 [inline]
__ia32_compat_sys_openat+0x353/0x3c0 fs/open.c:1286
do_syscall_32_irqs_on arch/x86/entry/common.c:114 [inline]
__do_fast_syscall_32+0x96/0xf0 arch/x86/entry/common.c:180
do_fast_syscall_32+0x34/0x70 arch/x86/entry/common.c:205
do_SYSENTER_32+0x1b/0x20 arch/x86/entry/common.c:248
entry_SYSENTER_compat_after_hwframe+0x4d/0x5c
CPU: 1 PID: 9774 Comm: syz-executor.4 Not tainted 5.16.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
=====================================================
---
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:[~2021-12-13 15:28 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=0000000000005affb705d308b986@google.com \
--to=syzbot+9ca499bb57a2b9e4c652@syzkaller.appspotmail.com \
--cc=glider@google.com \
--cc=jack@suse.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.