From: syzbot <syzbot+af14efe17dfa46173239@syzkaller.appspotmail.com>
To: activprithvi@gmail.com, heming.zhao@suse.com, jlbec@evilplan.org,
joseph.qi@linux.alibaba.com, linux-kernel@vger.kernel.org,
mark@fasheh.com, ocfs2-devel@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] KASAN: slab-use-after-free Read in ocfs2_reserve_suballoc_bits
Date: Sat, 20 Dec 2025 01:17:02 -0800 [thread overview]
Message-ID: <6946698e.a70a0220.207337.012d.GAE@google.com> (raw)
In-Reply-To: <20251220084457.107038-1-activprithvi@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+af14efe17dfa46173239@syzkaller.appspotmail.com
Tested-by: syzbot+af14efe17dfa46173239@syzkaller.appspotmail.com
Tested on:
commit: 36c25451 Merge tag 'powerpc-6.12-4' of git://git.kerne..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=152cd984580000
kernel config: https://syzkaller.appspot.com/x/.config?x=cb22c32016cc7ad7
dashboard link: https://syzkaller.appspot.com/bug?extid=af14efe17dfa46173239
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=169e1b1a580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-12-20 9:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 21:21 [syzbot] [ocfs2?] KASAN: slab-use-after-free Read in ocfs2_reserve_suballoc_bits syzbot
2025-12-20 8:44 ` Syzbot test for ocfs2: Add check for total number of chains in chain list Prithvi Tambewagh
2025-12-20 9:17 ` syzbot [this message]
2026-01-16 6:01 ` [syzbot] [ocfs2?] KASAN: slab-use-after-free Read in ocfs2_reserve_suballoc_bits 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=6946698e.a70a0220.207337.012d.GAE@google.com \
--to=syzbot+af14efe17dfa46173239@syzkaller.appspotmail.com \
--cc=activprithvi@gmail.com \
--cc=heming.zhao@suse.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--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