From: syzbot <syzbot+d2125fcb6aa8c4276fd2@syzkaller.appspotmail.com>
To: asmadeus@codewreck.org, brauner@kernel.org,
danielyangkang@gmail.com, dhowells@redhat.com, eadavis@qq.com,
ericvh@kernel.org, jack@suse.cz, jlayton@kernel.org,
linux-afs@lists.infradead.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux_oss@crudebyte.com,
lizhi.xu@windriver.com, lucho@ionkov.net,
marc.dionne@auristor.com, netfs@lists.linux.dev,
pc@manguebit.org, syzkaller-bugs@googlegroups.com,
v9fs@lists.linux.dev, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [fs?] general protection fault in iter_file_splice_write
Date: Tue, 23 Sep 2025 12:59:02 -0700 [thread overview]
Message-ID: <68d2fc06.a70a0220.4f78.000d.GAE@google.com> (raw)
In-Reply-To: <0000000000002fd2de0618de2e65@google.com>
syzbot suspects this issue was fixed by commit:
commit a3de58b12ce074ec05b8741fa28d62ccb1070468
Author: David Howells <dhowells@redhat.com>
Date: Thu Aug 14 21:45:50 2025 +0000
netfs: Fix unbuffered write error handling
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=162dc142580000
start commit: 5189dafa4cf9 Merge tag 'nfsd-6.11-1' of git://git.kernel.o..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=e8a2eef9745ade09
dashboard link: https://syzkaller.appspot.com/bug?extid=d2125fcb6aa8c4276fd2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16828c5d980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=103c7805980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: netfs: Fix unbuffered write error handling
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-09-23 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000002fd2de0618de2e65@google.com>
2024-08-11 22:43 ` [syzbot] [fs?] general protection fault in iter_file_splice_write syzbot
2025-09-23 19:59 ` syzbot [this message]
2025-09-25 12:47 ` David Howells
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=68d2fc06.a70a0220.4f78.000d.GAE@google.com \
--to=syzbot+d2125fcb6aa8c4276fd2@syzkaller.appspotmail.com \
--cc=asmadeus@codewreck.org \
--cc=brauner@kernel.org \
--cc=danielyangkang@gmail.com \
--cc=dhowells@redhat.com \
--cc=eadavis@qq.com \
--cc=ericvh@kernel.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lizhi.xu@windriver.com \
--cc=lucho@ionkov.net \
--cc=marc.dionne@auristor.com \
--cc=netfs@lists.linux.dev \
--cc=pc@manguebit.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=v9fs@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).