From: syzbot <syzbot+803dd716c4310d16ff3a@syzkaller.appspotmail.com>
To: chao@kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] kernel BUG in f2fs_write_end_io
Date: Sat, 11 Oct 2025 05:11:06 -0700 [thread overview]
Message-ID: <68ea495a.050a0220.ac43.0000.GAE@google.com> (raw)
In-Reply-To: <91f995c8-75e3-4b02-a7f1-be266a90b061@kernel.org>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+803dd716c4310d16ff3a@syzkaller.appspotmail.com
Tested-by: syzbot+803dd716c4310d16ff3a@syzkaller.appspotmail.com
Tested on:
commit: 591c8102 allow to sanity check in f2fs_write_end_io
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git bugfix/syzbot
console output: https://syzkaller.appspot.com/x/log.txt?x=17b469e2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9acaa7b581f88665
dashboard link: https://syzkaller.appspot.com/bug?extid=803dd716c4310d16ff3a
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.
next parent reply other threads:[~2025-10-11 12:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <91f995c8-75e3-4b02-a7f1-be266a90b061@kernel.org>
2025-10-11 12:11 ` syzbot [this message]
[not found] <697876e4-0b24-498a-8c4f-184077c3a1bc@kernel.org>
2025-09-01 7:52 ` [syzbot] [f2fs?] kernel BUG in f2fs_write_end_io syzbot
2025-04-02 0:00 syzbot
2025-04-15 14:14 ` syzbot
2025-08-11 11:05 ` Chao Yu
2025-08-11 11:31 ` syzbot
2025-08-11 11:41 ` Chao Yu
2025-08-11 12:10 ` 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=68ea495a.050a0220.ac43.0000.GAE@google.com \
--to=syzbot+803dd716c4310d16ff3a@syzkaller.appspotmail.com \
--cc=chao@kernel.org \
--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