From: syzbot <syzbot+d395b0c369e492a17530@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, sarvesh20123@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hfs?] KMSAN: uninit-value in __hfs_ext_cache_extent (2)
Date: Tue, 05 Nov 2024 19:57:04 -0800 [thread overview]
Message-ID: <672ae910.050a0220.2edce.151b.GAE@google.com> (raw)
In-Reply-To: <CAN=OONw=P_=3i7RSj67ZqW++8wcrmzuE-oN_fwjS7aR1t_B94g@mail.gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KMSAN: uninit-value in __hfs_ext_cache_extent
loop0: detected capacity change from 0 to 64
=====================================================
BUG: KMSAN: uninit-value in __hfs_ext_read_extent fs/hfs/extent.c:163 [inline]
BUG: KMSAN: uninit-value in __hfs_ext_cache_extent+0x779/0x7e0 fs/hfs/extent.c:179
__hfs_ext_read_extent fs/hfs/extent.c:163 [inline]
__hfs_ext_cache_extent+0x779/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
Local variable fd.i created at:
hfs_ext_read_extent fs/hfs/extent.c:193 [inline]
hfs_get_block+0x295/0xf50 fs/hfs/extent.c:366
__block_write_begin_int+0xa6b/0x2f80 fs/buffer.c:2121
CPU: 0 UID: 0 PID: 6068 Comm: syz.0.15 Not tainted 6.12.0-rc6-syzkaller-00077-g2e1b3cc9d7f7-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
=====================================================
Tested on:
commit: 2e1b3cc9 Merge tag 'arm-fixes-6.12-2' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10194e30580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b8a4f4c5365f96b
dashboard link: https://syzkaller.appspot.com/bug?extid=d395b0c369e492a17530
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=129d9d5f980000
next parent reply other threads:[~2024-11-06 3:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAN=OONw=P_=3i7RSj67ZqW++8wcrmzuE-oN_fwjS7aR1t_B94g@mail.gmail.com>
2024-11-06 3:57 ` syzbot [this message]
[not found] <d703694c-a0a7-480b-bafa-c8703306d2f5@gmail.com>
2024-11-13 0:26 ` [syzbot] [hfs?] KMSAN: uninit-value in __hfs_ext_cache_extent (2) syzbot
[not found] <9be1baa3-d2f4-4e20-9f13-c6c12f0813dc@gmail.com>
2024-11-11 21:10 ` syzbot
[not found] <CAN=OONzCeRjbK6TbqenTyjYSpPh4f1-5UmrzeYcW2anq80P_EA@mail.gmail.com>
2024-11-06 6:52 ` syzbot
[not found] <CAN=OONwWNfETusinz2A7yGG2OFtS8Nnn8z9FhUTpPuugHKnMkw@mail.gmail.com>
2024-11-05 21:12 ` syzbot
[not found] <CAN=OONzfDPeFZ-BnRd53psEUgv2-wLFxq299SLLK9UqG_iZ4NA@mail.gmail.com>
2024-11-05 10:25 ` 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] <CAHiZj8j_3jKyqB=_KB9ctK_hYu_gS6nn0VtDokTrnJ=4P9OGWw@mail.gmail.com>
2024-10-02 7:34 ` syzbot
[not found] <CAHiZj8gaK1pvOZzxndtb8KTCMoj=UczhHv6_f6ogbMtOU7HdPQ@mail.gmail.com>
2024-10-01 22:35 ` syzbot
2024-10-01 9:27 syzbot
2024-10-10 13:41 ` Qianqiang Liu
2024-10-10 14:16 ` 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=672ae910.050a0220.2edce.151b.GAE@google.com \
--to=syzbot+d395b0c369e492a17530@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sarvesh20123@gmail.com \
--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.