From: syzbot <syzbot+c37bed40868932d790e9@syzkaller.appspotmail.com>
To: konishi.ryusuke@gmail.com, linux-kernel@vger.kernel.org,
linux-nilfs@vger.kernel.org, slava@dubeyko.com,
syzkaller-bugs@googlegroups.com, wuyankun@uniontech.com
Subject: Re: [syzbot] [nilfs?] BUG: corrupted list in nilfs_lookup_dirty_data_buffers
Date: Thu, 25 Jun 2026 02:49:01 -0700 [thread overview]
Message-ID: <6a3cf98d.ac7367b4.6675.0000.GAE@google.com> (raw)
In-Reply-To: <20260625091400.270398-1-wuyankun@uniontech.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+c37bed40868932d790e9@syzkaller.appspotmail.com
Tested-by: syzbot+c37bed40868932d790e9@syzkaller.appspotmail.com
Tested on:
commit: ab9de95c Merge tag 'rust-7.2-2' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=134eecde580000
kernel config: https://syzkaller.appspot.com/x/.config?x=3c3d59be33cf7e9a
dashboard link: https://syzkaller.appspot.com/bug?extid=c37bed40868932d790e9
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=17c5db7a580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2026-06-25 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 19:59 [syzbot] [nilfs?] BUG: corrupted list in nilfs_lookup_dirty_data_buffers syzbot
2026-06-25 0:29 ` Forwarded: " syzbot
2026-06-25 9:14 ` [PATCH] nilfs2: prevent double insertion of b_assoc_buffers in dirty buffer lookup wuyankun
2026-06-25 9:49 ` syzbot [this message]
[not found] <DJHPELGP8OYI.2D0QFGTG12F29@gmail.com>
2026-06-25 1:04 ` [syzbot] [nilfs?] BUG: corrupted list in nilfs_lookup_dirty_data_buffers 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=6a3cf98d.ac7367b4.6675.0000.GAE@google.com \
--to=syzbot+c37bed40868932d790e9@syzkaller.appspotmail.com \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=slava@dubeyko.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wuyankun@uniontech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.