From: syzbot <syzbot+55c40ae8a0e5f3659f2b@syzkaller.appspotmail.com>
To: eraykrdg1@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] WARNING in ocfs2_unlink
Date: Thu, 23 Oct 2025 19:26:04 -0700 [thread overview]
Message-ID: <68fae3bc.050a0220.346f24.008f.GAE@google.com> (raw)
In-Reply-To: <CAHxJ8O_3H5QQ+x4=kdaXr4ELfqO3PCxGO49Ds1yA7mAcBGBh2g@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+55c40ae8a0e5f3659f2b@syzkaller.appspotmail.com
Tested-by: syzbot+55c40ae8a0e5f3659f2b@syzkaller.appspotmail.com
Tested on:
commit: 6fab32bb MAINTAINERS: add Mark Brown as a linux-next m..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12b4ae7c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a1215729170d20fc
dashboard link: https://syzkaller.appspot.com/bug?extid=55c40ae8a0e5f3659f2b
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=16d1c614580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-10-24 2:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHxJ8O_3H5QQ+x4=kdaXr4ELfqO3PCxGO49Ds1yA7mAcBGBh2g@mail.gmail.com>
2025-10-24 2:26 ` syzbot [this message]
[not found] <CAHxJ8O80C2HWks02cKoSnt6NoiWdWB+sFLpGLX0v9F+QSxLFRw@mail.gmail.com>
2025-11-17 22:34 ` [syzbot] [ocfs2?] WARNING in ocfs2_unlink syzbot
[not found] <CAHxJ8O-1sE7rYwF9MEwc0Py92uZtHjQSf=wcx+MGFSTJ1wXZtQ@mail.gmail.com>
2025-10-25 8:47 ` syzbot
[not found] <CAHxJ8O90xfWT+5st_bkmg39pVsewvchf46ZPCzSzHHcbPUY-iA@mail.gmail.com>
2025-10-24 1:49 ` syzbot
[not found] <CADfthj2Ycc0apak2Y_fpix4SWhLT9Xq89pJ=gCENGrkv1R++hQ@mail.gmail.com>
2025-10-23 9:32 ` syzbot
[not found] <CAHxJ8O-aa8eM1u4J_E6B4Rk6S9fsnLsKdU02+n2FTSdnhDHtvg@mail.gmail.com>
2025-10-22 5:11 ` syzbot
2025-01-14 14:59 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=68fae3bc.050a0220.346f24.008f.GAE@google.com \
--to=syzbot+55c40ae8a0e5f3659f2b@syzkaller.appspotmail.com \
--cc=eraykrdg1@gmail.com \
--cc=linux-kernel@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