From: syzbot <syzbot+8901c4560b7ab5c2f9df@syzkaller.appspotmail.com>
To: jack@suse.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [udf?] KMSAN: uninit-value in udf_get_fileshortad
Date: Tue, 17 Sep 2024 07:52:34 -0700 [thread overview]
Message-ID: <000000000000f9e854062251d673@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 0babf683783d Merge tag 'pinctrl-v6.11-4' of git://git.kern..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=17139900580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ea008021530b2de3
dashboard link: https://syzkaller.appspot.com/bug?extid=8901c4560b7ab5c2f9df
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=14080c9f980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13927c77980000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a92580d12355/disk-0babf683.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8c7829a87d5b/vmlinux-0babf683.xz
kernel image: https://storage.googleapis.com/syzbot-assets/52de69e62dfd/bzImage-0babf683.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/e314f05a944a/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8901c4560b7ab5c2f9df@syzkaller.appspotmail.com
loop0: detected capacity change from 2048 to 2047
=====================================================
BUG: KMSAN: uninit-value in udf_get_fileshortad+0x174/0x1c0 fs/udf/directory.c:504
udf_get_fileshortad+0x174/0x1c0 fs/udf/directory.c:504
udf_current_aext+0x6cb/0x950 fs/udf/inode.c:2225
udf_next_aext+0x94/0x500 fs/udf/inode.c:2171
udf_discard_prealloc+0x47c/0x830 fs/udf/truncate.c:135
udf_release_file+0xfd/0x160 fs/udf/file.c:184
__fput+0x344/0x1160 fs/file_table.c:422
__fput_sync+0x74/0x90 fs/file_table.c:507
__do_sys_close fs/open.c:1566 [inline]
__se_sys_close+0x290/0x4d0 fs/open.c:1551
__x64_sys_close+0x48/0x60 fs/open.c:1551
x64_sys_call+0x2c26/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:4
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:
__alloc_pages_noprof+0x9d6/0xe70 mm/page_alloc.c:4725
alloc_pages_mpol_noprof+0x299/0x990 mm/mempolicy.c:2263
alloc_pages_noprof mm/mempolicy.c:2343 [inline]
folio_alloc_noprof+0x1db/0x310 mm/mempolicy.c:2350
filemap_alloc_folio_noprof+0xa6/0x440 mm/filemap.c:1008
__filemap_get_folio+0xa05/0x14b0 mm/filemap.c:1950
grow_dev_folio fs/buffer.c:1047 [inline]
grow_buffers fs/buffer.c:1113 [inline]
__getblk_slow fs/buffer.c:1139 [inline]
bdev_getblk+0x2c9/0xab0 fs/buffer.c:1441
__bread_gfp+0x93/0x730 fs/buffer.c:1495
sb_bread include/linux/buffer_head.h:347 [inline]
udf_next_aext+0x302/0x500 fs/udf/inode.c:2186
udf_discard_prealloc+0x47c/0x830 fs/udf/truncate.c:135
udf_release_file+0xfd/0x160 fs/udf/file.c:184
__fput+0x344/0x1160 fs/file_table.c:422
__fput_sync+0x74/0x90 fs/file_table.c:507
__do_sys_close fs/open.c:1566 [inline]
__se_sys_close+0x290/0x4d0 fs/open.c:1551
__x64_sys_close+0x48/0x60 fs/open.c:1551
x64_sys_call+0x2c26/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:4
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: 1 UID: 0 PID: 5181 Comm: syz-executor248 Not tainted 6.11.0-rc7-syzkaller-00149-g0babf683783d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/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-09-17 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 14:52 syzbot [this message]
2024-09-19 15:42 ` [syzbot] KMSAN: uninit-value in udf_get_fileshortad syzbot
2024-09-24 14:51 ` syzbot
[not found] <8da7cb9d-5d28-4203-9a24-03a1201d8a2d@gmail.com>
2024-09-19 19:13 ` [syzbot] [udf?] " syzbot
[not found] <8cef3615-5553-49b9-89cd-393b2794f016@gmail.com>
2024-09-24 15:21 ` 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=000000000000f9e854062251d673@google.com \
--to=syzbot+8901c4560b7ab5c2f9df@syzkaller.appspotmail.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.