From: syzbot <syzbot+4a2376bc62e59406c414@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org,
almaz.alexandrovich@paragon-software.com, dvyukov@google.com,
eadavis@sina.com, hughd@google.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com, tintinm2017@gmail.com,
twuufnxlz@gmail.com
Subject: Re: [syzbot] [hfs?] [mm?] KASAN: slab-out-of-bounds Read in generic_perform_write
Date: Sun, 04 May 2025 02:52:03 -0700 [thread overview]
Message-ID: <681738c3.050a0220.11da1b.002e.GAE@google.com> (raw)
In-Reply-To: <000000000000820e380606161640@google.com>
syzbot suspects this issue was fixed by commit:
commit b432163ebd15a0fb74051949cb61456d6c55ccbd
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Thu Jan 30 14:03:41 2025 +0000
fs/ntfs3: Update inode->i_mapping->a_ops on compression state
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=115c5b68580000
start commit: fc033cf25e61 Linux 6.13-rc5
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=ba7cde9482d6bb6
dashboard link: https://syzkaller.appspot.com/bug?extid=4a2376bc62e59406c414
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1654aac4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13ff26df980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs/ntfs3: Update inode->i_mapping->a_ops on compression state
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-05-04 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000820e380606161640@google.com>
2023-09-26 10:24 ` [PATCH] fs/hfsplus: expand s_vhdr_buf size to avoid slab oob Edward AD
2024-07-04 14:05 ` Dmitry Vyukov
2025-05-04 9:52 ` syzbot [this message]
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=681738c3.050a0220.11da1b.002e.GAE@google.com \
--to=syzbot+4a2376bc62e59406c414@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=dvyukov@google.com \
--cc=eadavis@sina.com \
--cc=hughd@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tintinm2017@gmail.com \
--cc=twuufnxlz@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox