From: syzbot <syzbot+af14efe17dfa46173239@syzkaller.appspotmail.com>
To: activprithvi@gmail.com, akpm@linux-foundation.org,
david.hunter.linux@gmail.com, dmantipov@yandex.ru,
heming.zhao@suse.com, jlbec@evilplan.org,
joseph.qi@linux.alibaba.com, khalid@kernel.org,
linux-kernel-mentees@lists.linux.dev,
linux-kernel@vger.kernel.org, mark@fasheh.com,
ocfs2-devel@lists.linux.dev, skhan@linuxfoundation.org,
stable@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] KASAN: slab-use-after-free Read in ocfs2_reserve_suballoc_bits
Date: Thu, 15 Jan 2026 22:01:02 -0800 [thread overview]
Message-ID: <6969d41e.050a0220.58bed.003e.GAE@google.com> (raw)
In-Reply-To: <67117fd9.050a0220.10f4f4.0004.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit e1c70505ee8158c1108340d9cd67182ade93af4a
Author: Dmitry Antipov <dmantipov@yandex.ru>
Date: Thu Oct 30 15:30:02 2025 +0000
ocfs2: add extra consistency checks for chain allocator dinodes
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=140a0852580000
start commit: 36c254515dc6 Merge tag 'powerpc-6.12-4' of git://git.kerne..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=7a3fccdd0bb995
dashboard link: https://syzkaller.appspot.com/bug?extid=af14efe17dfa46173239
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13444727980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11861440580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: ocfs2: add extra consistency checks for chain allocator dinodes
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2026-01-16 6:01 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <67117fd9.050a0220.10f4f4.0004.GAE@google.com>]
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=6969d41e.050a0220.58bed.003e.GAE@google.com \
--to=syzbot+af14efe17dfa46173239@syzkaller.appspotmail.com \
--cc=activprithvi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david.hunter.linux@gmail.com \
--cc=dmantipov@yandex.ru \
--cc=heming.zhao@suse.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=khalid@kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox