public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: syzbot <syzbot+d2125fcb6aa8c4276fd2@syzkaller.appspotmail.com>
Cc: dhowells@redhat.com, asmadeus@codewreck.org, brauner@kernel.org,
	danielyangkang@gmail.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: Thu, 25 Sep 2025 13:47:55 +0100	[thread overview]
Message-ID: <935794.1758804475@warthog.procyon.org.uk> (raw)
In-Reply-To: <68d2fc06.a70a0220.4f78.000d.GAE@google.com>

#syz fix: netfs: Fix unbuffered write error handling


  reply	other threads:[~2025-09-25 12:48 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-20  8:06 [syzbot] [fs?] general protection fault in iter_file_splice_write syzbot
2024-05-22  5:21 ` Edward Adam Davis
2024-05-22  5:45   ` syzbot
2024-05-22 10:37 ` Edward Adam Davis
2024-05-22 10:57   ` syzbot
2024-05-22 11:30 ` Edward Adam Davis
2024-05-22 11:56   ` syzbot
2024-05-22 12:49 ` Edward Adam Davis
2024-05-22 13:13   ` syzbot
2024-05-22 13:29 ` Edward Adam Davis
2024-05-22 13:54   ` syzbot
2024-05-22 14:05 ` Edward Adam Davis
2024-05-22 14:30   ` syzbot
2024-05-23  8:33 ` [syzbot] " syzbot
2024-05-23  9:23 ` syzbot
2024-05-23 12:33 ` Edward Adam Davis
2024-05-23 12:58   ` syzbot
2024-05-23 14:13 ` Edward Adam Davis
2024-05-23 14:37   ` syzbot
2024-05-24  0:52 ` [syzbot] " syzbot
2024-05-24  1:30 ` syzbot
2024-05-24  2:07 ` syzbot
2024-05-24  3:51 ` syzbot
2024-05-24  5:35 ` [PATCH] netfs: if extracting pages from user iterator fails return 0 Lizhi Xu
2024-08-11 22:43 ` [syzbot] [fs?] general protection fault in iter_file_splice_write syzbot
2025-09-23 19:59 ` syzbot
2025-09-25 12:47   ` David Howells [this message]
     [not found] <20240523083332.761304-1-lizhi.xu@windriver.com>
2024-05-23  8:58 ` syzbot
     [not found] <20240523092352.1279292-1-lizhi.xu@windriver.com>
2024-05-23  9:36 ` syzbot
     [not found] <20240524005225.2834298-1-lizhi.xu@windriver.com>
2024-05-24  1:15 ` syzbot
     [not found] <20240524012956.3069071-1-lizhi.xu@windriver.com>
2024-05-24  1:51 ` syzbot
     [not found] <20240524020717.1126466-1-lizhi.xu@windriver.com>
2024-05-24  2:31 ` syzbot
     [not found] <20240524035136.1561347-1-lizhi.xu@windriver.com>
2024-05-24  4:16 ` 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=935794.1758804475@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=asmadeus@codewreck.org \
    --cc=brauner@kernel.org \
    --cc=danielyangkang@gmail.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=syzbot+d2125fcb6aa8c4276fd2@syzkaller.appspotmail.com \
    --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