From: syzbot <syzbot+b2b14916b77acf8626d7@syzkaller.appspotmail.com>
To: konishi.ryusuke@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [nilfs?] WARNING in nilfs_btree_propagate (2)
Date: Wed, 11 Dec 2024 04:43:05 -0800 [thread overview]
Message-ID: <675988d9.050a0220.1ac542.000c.GAE@google.com> (raw)
In-Reply-To: <20241211.203019.1906828475608694378.konishi.ryusuke@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+b2b14916b77acf8626d7@syzkaller.appspotmail.com
Tested-by: syzbot+b2b14916b77acf8626d7@syzkaller.appspotmail.com
Tested on:
commit: f92f4749 Merge tag 'clk-fixes-for-linus' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=135db3e8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=5a0b1b189561bf60
dashboard link: https://syzkaller.appspot.com/bug?extid=b2b14916b77acf8626d7
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=13a5c20f980000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-12-11 12:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 17:29 syzbot
2024-12-11 11:30 ` Ryusuke Konishi
2024-12-11 12:43 ` syzbot [this message]
2025-01-07 20:00 ` [PATCH 0/2] nilfs2: protect busy buffer heads from being force-cleared Ryusuke Konishi
2025-01-07 20:00 ` [PATCH 1/2] nilfs2: do not force clear folio if buffer is referenced Ryusuke Konishi
2025-01-07 20:00 ` [PATCH 2/2] nilfs2: protect access to buffers with no active references Ryusuke Konishi
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=675988d9.050a0220.1ac542.000c.GAE@google.com \
--to=syzbot+b2b14916b77acf8626d7@syzkaller.appspotmail.com \
--cc=konishi.ryusuke@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
Powered by JetHome