From: syzbot <syzbot+d395b0c369e492a17530@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [hfs?] KMSAN: uninit-value in __hfs_ext_cache_extent (2)
Date: Tue, 01 Oct 2024 02:27:29 -0700 [thread overview]
Message-ID: <66fbc081.050a0220.6bad9.0056.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: ad46e8f95e93 Merge tag 'pm-6.12-rc1-2' of git://git.kernel..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=11b9be27980000
kernel config: https://syzkaller.appspot.com/x/.config?x=85d8f50d88ddf2a
dashboard link: https://syzkaller.appspot.com/bug?extid=d395b0c369e492a17530
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=15b9be27980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10ddd507980000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/265feec46ffa/disk-ad46e8f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d0f41ea693d3/vmlinux-ad46e8f9.xz
kernel image: https://storage.googleapis.com/syzbot-assets/45082d33d192/bzImage-ad46e8f9.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/c19549ac916f/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d395b0c369e492a17530@syzkaller.appspotmail.com
loop0: detected capacity change from 0 to 64
=====================================================
BUG: KMSAN: uninit-value in __hfs_ext_read_extent fs/hfs/extent.c:160 [inline]
BUG: KMSAN: uninit-value in __hfs_ext_cache_extent+0x69f/0x7e0 fs/hfs/extent.c:179
__hfs_ext_read_extent fs/hfs/extent.c:160 [inline]
__hfs_ext_cache_extent+0x69f/0x7e0 fs/hfs/extent.c:179
hfs_ext_read_extent fs/hfs/extent.c:202 [inline]
hfs_get_block+0x733/0xf50 fs/hfs/extent.c:366
__block_write_begin_int+0xa6b/0x2f80 fs/buffer.c:2121
block_write_begin fs/buffer.c:2231 [inline]
cont_write_begin+0xf82/0x1940 fs/buffer.c:2582
hfs_write_begin+0x85/0x120 fs/hfs/inode.c:52
cont_expand_zero fs/buffer.c:2509 [inline]
cont_write_begin+0x32f/0x1940 fs/buffer.c:2572
hfs_write_begin+0x85/0x120 fs/hfs/inode.c:52
hfs_file_truncate+0x1a5/0xd30 fs/hfs/extent.c:494
hfs_inode_setattr+0x998/0xab0 fs/hfs/inode.c:654
notify_change+0x1a8e/0x1b80 fs/attr.c:503
do_truncate+0x22a/0x2b0 fs/open.c:65
vfs_truncate+0x5d4/0x680 fs/open.c:111
do_sys_truncate+0x104/0x240 fs/open.c:134
__do_sys_truncate fs/open.c:146 [inline]
__se_sys_truncate fs/open.c:144 [inline]
__x64_sys_truncate+0x6c/0xa0 fs/open.c:144
x64_sys_call+0x2ce3/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:77
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:
slab_post_alloc_hook mm/slub.c:4092 [inline]
slab_alloc_node mm/slub.c:4135 [inline]
__do_kmalloc_node mm/slub.c:4264 [inline]
__kmalloc_noprof+0x661/0xf30 mm/slub.c:4277
kmalloc_noprof include/linux/slab.h:882 [inline]
hfs_find_init+0x91/0x250 fs/hfs/bfind.c:21
hfs_ext_read_extent fs/hfs/extent.c:200 [inline]
hfs_get_block+0x68d/0xf50 fs/hfs/extent.c:366
__block_write_begin_int+0xa6b/0x2f80 fs/buffer.c:2121
block_write_begin fs/buffer.c:2231 [inline]
cont_write_begin+0xf82/0x1940 fs/buffer.c:2582
hfs_write_begin+0x85/0x120 fs/hfs/inode.c:52
cont_expand_zero fs/buffer.c:2509 [inline]
cont_write_begin+0x32f/0x1940 fs/buffer.c:2572
hfs_write_begin+0x85/0x120 fs/hfs/inode.c:52
hfs_file_truncate+0x1a5/0xd30 fs/hfs/extent.c:494
hfs_inode_setattr+0x998/0xab0 fs/hfs/inode.c:654
notify_change+0x1a8e/0x1b80 fs/attr.c:503
do_truncate+0x22a/0x2b0 fs/open.c:65
vfs_truncate+0x5d4/0x680 fs/open.c:111
do_sys_truncate+0x104/0x240 fs/open.c:134
__do_sys_truncate fs/open.c:146 [inline]
__se_sys_truncate fs/open.c:144 [inline]
__x64_sys_truncate+0x6c/0xa0 fs/open.c:144
x64_sys_call+0x2ce3/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:77
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: 0 UID: 0 PID: 5188 Comm: syz-executor246 Not tainted 6.11.0-syzkaller-11728-gad46e8f95e93 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/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-10-01 9:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 9:27 syzbot [this message]
2024-10-01 21:44 ` [syzbot] Re: [syzbot] [hfs?] KMSAN: uninit-value in __hfs_ext_cache_extent (2) syzbot
2024-10-02 7:08 ` syzbot
2024-10-10 13:41 ` Qianqiang Liu
2024-10-10 14:16 ` syzbot
2024-10-22 15:21 ` [syzbot] " syzbot
2024-11-05 8:26 ` syzbot
2024-11-05 12:20 ` [syzbot] KMSAN: uninit-value in __hfs_ext_cache_extent (2) Inbox syzbot
2024-11-06 3:30 ` [syzbot] KMSAN: uninit-value in __hfs_ext_cache_extent (2) syzbot
2024-11-06 6:23 ` [syzbot] KMSAN: uninit-value in __hfs_ext_cache_extent (2) Inbox syzbot
2024-11-11 19:55 ` [syzbot] KMSAN: uninit-value in __hfs_ext_cache_extent (2) syzbot
2024-11-12 16:14 ` syzbot
[not found] <CAHiZj8gaK1pvOZzxndtb8KTCMoj=UczhHv6_f6ogbMtOU7HdPQ@mail.gmail.com>
2024-10-01 22:35 ` [syzbot] [hfs?] " syzbot
[not found] <CAHiZj8j_3jKyqB=_KB9ctK_hYu_gS6nn0VtDokTrnJ=4P9OGWw@mail.gmail.com>
2024-10-02 7:34 ` syzbot
[not found] <3b0be684-0b50-4151-a275-0751715d1be8@gmail.com>
2024-10-22 15:52 ` syzbot
2024-10-22 17:05 ` Gianfranco Trad
2024-10-22 17:31 ` syzbot
[not found] <CAN=OONzfDPeFZ-BnRd53psEUgv2-wLFxq299SLLK9UqG_iZ4NA@mail.gmail.com>
2024-11-05 10:25 ` syzbot
[not found] <CAN=OONwWNfETusinz2A7yGG2OFtS8Nnn8z9FhUTpPuugHKnMkw@mail.gmail.com>
2024-11-05 21:12 ` syzbot
[not found] <CAN=OONw=P_=3i7RSj67ZqW++8wcrmzuE-oN_fwjS7aR1t_B94g@mail.gmail.com>
2024-11-06 3:57 ` syzbot
[not found] <CAN=OONzCeRjbK6TbqenTyjYSpPh4f1-5UmrzeYcW2anq80P_EA@mail.gmail.com>
2024-11-06 6:52 ` syzbot
[not found] <9be1baa3-d2f4-4e20-9f13-c6c12f0813dc@gmail.com>
2024-11-11 21:10 ` syzbot
[not found] <d703694c-a0a7-480b-bafa-c8703306d2f5@gmail.com>
2024-11-13 0:26 ` 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=66fbc081.050a0220.6bad9.0056.GAE@google.com \
--to=syzbot+d395b0c369e492a17530@syzkaller.appspotmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--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.