From: syzbot <syzbot+4af46ee83100e99bce09@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 (2)
Date: Sun, 17 May 2026 02:26:04 -0700 [thread overview]
Message-ID: <6a0989ac.050a0220.f80e4.0009.GAE@google.com> (raw)
In-Reply-To: <9e7cbcac-0387-4938-b4f5-aee3f19890a5@kernel.org>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
lost connection to test machine
Tested on:
commit: 3b3d051f f2fs: fix to pass folio->index to f2fs_sanity..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git syzbot
console output: https://syzkaller.appspot.com/x/log.txt?x=15389fce580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f2e8ebfec4636d32
dashboard link: https://syzkaller.appspot.com/bug?extid=4af46ee83100e99bce09
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
Note: no patches were applied.
next parent reply other threads:[~2026-05-17 9:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9e7cbcac-0387-4938-b4f5-aee3f19890a5@kernel.org>
2026-05-17 9:26 ` syzbot [this message]
[not found] <57d86974-d80f-4628-8788-e15b0c2ec8f1@kernel.org>
2026-05-17 6:07 ` [syzbot] [f2fs?] kernel BUG in f2fs_write_end_io (2) syzbot
[not found] <fb082ccd-f05a-45cb-95e5-990cb9628e36@kernel.org>
2026-05-17 3:40 ` syzbot
[not found] <20260515015523.14962-1-kartikey406@gmail.com>
2026-05-15 2:37 ` syzbot
[not found] <20260515005957.13243-1-kartikey406@gmail.com>
2026-05-15 1:37 ` syzbot
[not found] <20260514233543.9626-1-kartikey406@gmail.com>
2026-05-15 0:07 ` syzbot
2026-05-14 20:19 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=6a0989ac.050a0220.f80e4.0009.GAE@google.com \
--to=syzbot+4af46ee83100e99bce09@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 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.