public inbox for nvdimm@lists.linux.dev
 help / color / mirror / Atom feed
From: syzbot <syzbot+31b8fb02cb8a25bd5e78@syzkaller.appspotmail.com>
To: hsiangkao@linux.alibaba.com, linux-erofs@lists.ozlabs.org,
	 linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	 nvdimm@lists.linux.dev, syzkaller-bugs@googlegroups.com,
	xiang@kernel.org
Subject: Re: [syzbot] [erofs?] WARNING in get_next_unlocked_entry
Date: Thu, 20 Nov 2025 18:06:03 -0800	[thread overview]
Message-ID: <691fc90b.a70a0220.d98e3.003a.GAE@google.com> (raw)
In-Reply-To: <1939a99d-c1d2-4b98-93c3-1951db367b3f@linux.alibaba.com>

Hello,

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

Reported-by: syzbot+31b8fb02cb8a25bd5e78@syzkaller.appspotmail.com
Tested-by: syzbot+31b8fb02cb8a25bd5e78@syzkaller.appspotmail.com

Tested on:

commit:         3027b141 erofs: correct FSDAX detection
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git dev-test
console output: https://syzkaller.appspot.com/x/log.txt?x=16e2597c580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=a1db0fea040c2a9f
dashboard link: https://syzkaller.appspot.com/bug?extid=31b8fb02cb8a25bd5e78
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

      reply	other threads:[~2025-11-21  2:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 10:33 [syzbot] [erofs?] WARNING in get_next_unlocked_entry syzbot
2025-11-21  1:44 ` Gao Xiang
2025-11-21  2:06   ` 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=691fc90b.a70a0220.d98e3.003a.GAE@google.com \
    --to=syzbot+31b8fb02cb8a25bd5e78@syzkaller.appspotmail.com \
    --cc=hsiangkao@linux.alibaba.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=xiang@kernel.org \
    /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