From: syzbot <syzbot+b4444e3c972a7a124187@syzkaller.appspotmail.com>
To: chao@kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] KASAN: use-after-free Read in f2fs_write_end_io (2)
Date: Wed, 07 Jan 2026 01:10:02 -0800 [thread overview]
Message-ID: <695e22ea.050a0220.1c677c.035b.GAE@google.com> (raw)
In-Reply-To: <250918c3-c700-436f-a103-a081d8f2f9a7@kernel.org>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+b4444e3c972a7a124187@syzkaller.appspotmail.com
Tested-by: syzbot+b4444e3c972a7a124187@syzkaller.appspotmail.com
Tested on:
commit: 5f1756b5 f2fs: fix to avoid UAF 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=16f42922580000
kernel config: https://syzkaller.appspot.com/x/.config?x=513255d80ab78f2b
dashboard link: https://syzkaller.appspot.com/bug?extid=b4444e3c972a7a124187
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:[~2026-01-07 9:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <250918c3-c700-436f-a103-a081d8f2f9a7@kernel.org>
2026-01-07 9:10 ` syzbot [this message]
[not found] <8b7dffa7-08b4-4705-8c6e-e73f6784dc43@kernel.org>
2026-01-07 7:00 ` [syzbot] [f2fs?] KASAN: use-after-free Read in f2fs_write_end_io (2) syzbot
2025-12-22 4:08 syzbot
2026-01-07 2:04 ` Chao Yu
2026-01-07 2:19 ` syzbot
2026-01-07 9:50 ` Chao Yu
2026-01-07 10:05 ` syzbot
2026-01-07 10:59 ` Chao Yu
2026-01-07 11:14 ` 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=695e22ea.050a0220.1c677c.035b.GAE@google.com \
--to=syzbot+b4444e3c972a7a124187@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