public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+779d072a1067a8b1a917@syzkaller.appspotmail.com>
To: activprithvi@gmail.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?] kernel BUG in ocfs2_populate_inode
Date: Tue, 16 Dec 2025 11:41:04 -0800	[thread overview]
Message-ID: <6941b5d0.a70a0220.25eec0.0007.GAE@google.com> (raw)
In-Reply-To: <20251216185221.31843-1-activprithvi@gmail.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+779d072a1067a8b1a917@syzkaller.appspotmail.com
Tested-by: syzbot+779d072a1067a8b1a917@syzkaller.appspotmail.com

Tested on:

commit:         d76bb1eb Merge tag 'erofs-for-6.15-rc6-fixes' of git:/..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=1479e77c580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b20d1657eb8978a6
dashboard link: https://syzkaller.appspot.com/bug?extid=779d072a1067a8b1a917
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=13c41d92580000

Note: testing is done by a robot and is best-effort only.

      reply	other threads:[~2025-12-16 19:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-24  5:20 [syzbot] [ocfs2?] kernel BUG in ocfs2_populate_inode syzbot
2025-12-16 18:52 ` Syzbot test for ocfs2: handle OCFS2_SUPER_BLOCK_FL flag in system dinode Prithvi Tambewagh
2025-12-16 19:41   ` 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=6941b5d0.a70a0220.25eec0.0007.GAE@google.com \
    --to=syzbot+779d072a1067a8b1a917@syzkaller.appspotmail.com \
    --cc=activprithvi@gmail.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