From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: sungbyeongchan <tjdqudcks0424@naver.com>
Cc: "German Maglione" <gmaglione@redhat.com>,
"Vivek Goyal" <vgoyal@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Miklos Szeredi" <miklos@szeredi.hu>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
virtualization@lists.linux.dev, fuse-devel@lists.linux.dev,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] virtiofs: validate fixed-output response length
Date: Tue, 6 Oct 2026 23:11:14 +0200 [thread overview]
Message-ID: <2026100633-roping-stardust-a6ab@gregkh> (raw)
In-Reply-To: <20261006182408.1301152-1-tjdqudcks0424@naver.com>
On Wed, Oct 07, 2026 at 03:24:08AM +0900, sungbyeongchan wrote:
> A short successful virtiofs response can leave the fixed-output
> portion of the request argument buffer unwritten. The completion path
> nevertheless copies the full declared output to the request destination,
> allowing stale allocator contents to reach callers such as
> fuse_statfs().
>
> Require successful fixed-output responses to contain their complete
> declared output. Continue to permit a shorter final argument only for
> out_argvar requests. Reject positive and internal restart error values,
> require valid error replies to be header-only, and do not copy output
> arguments from error replies.
>
> A header-only FUSE_STATFS success returned stale fields in nine of
> nine calls across three boots. The fixed kernel rejected the short
> response and preserved complete replies, valid error replies, and
> variable-output controls.
>
> Fixes: a62a8ef9d97d ("virtio-fs: add virtiofs filesystem")
> Cc: stable@vger.kernel.org
> Assisted-by: LLM
> Signed-off-by: sungbyeongchan <tjdqudcks0424@naver.com>
Real name please.
> ---
> Changes in v2:
> - Reject positive and internal restart error values.
> - Require error replies to be header-only.
> - Rate-limit malformed-response warnings.
> - Rely on the existing FUSE pr_fmt prefix.
> - Add Cc: stable@vger.kernel.org.
> - Use the reporter identity consistently.
>
> fs/fuse/virtio_fs.c | 43 ++++++++++++++++++++++++++++++++++++++-----
> 1 file changed, 38 insertions(+), 5 deletions(-)
>
> diff --git a/fs/fuse/virtio_fs.c b/fs/fuse/virtio_fs.c
> index f15e516ebcb5c..fffbe08d9114a 100644
> --- a/fs/fuse/virtio_fs.c
> +++ b/fs/fuse/virtio_fs.c
> @@ -4,6 +4,8 @@
> * Copyright (C) 2018 Red Hat, Inc.
> */
>
> +#include "fuse_i.h"
> +
Why is this moved?
> #include <linux/fs.h>
> #include <linux/dax.h>
> #include <linux/pci.h>
> @@ -20,7 +22,6 @@
> #include <linux/cleanup.h>
> #include <linux/uio.h>
> #include "dev.h"
> -#include "fuse_i.h"
> #include "fuse_dev_i.h"
>
> /* Used to help calculate the FUSE connection's max_pages limit for a request's
> @@ -730,6 +731,10 @@ static void copy_args_from_argbuf(struct fuse_args *args, struct fuse_req *req)
> unsigned int num_out;
> unsigned int i;
>
> + /* Error replies contain only the output header. */
> + if (req->out.h.error)
> + goto out;
But no error is returned?
> if (len < sizeof(*oh)) {
> - pr_warn("virtio-fs: response too short (%u)\n", len);
> + pr_warn_ratelimited("response too short (%u)\n", len);
Isn't these ratelimited() changes separate from the original issue here?
That should be a separate patch.
thanks,
greg k-h
next prev parent reply other threads:[~2026-10-06 21:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 12:34 [PATCH] virtiofs: validate fixed-output response length sungbyeongchan
2026-10-04 12:46 ` sashiko-bot
2026-10-04 12:55 ` Greg Kroah-Hartman
2026-10-04 12:56 ` Greg Kroah-Hartman
2026-10-04 13:04 ` Michael S. Tsirkin
2026-10-04 14:48 ` [PATCH v2] " Byeongchan Sung
2026-10-04 14:59 ` sashiko-bot
2026-10-06 18:24 ` sungbyeongchan
2026-10-06 18:36 ` sashiko-bot
2026-10-06 21:11 ` Greg Kroah-Hartman [this message]
2026-10-06 21:27 ` Michael S. Tsirkin
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=2026100633-roping-stardust-a6ab@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=eperezma@redhat.com \
--cc=fuse-devel@lists.linux.dev \
--cc=gmaglione@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mst@redhat.com \
--cc=stable@vger.kernel.org \
--cc=stefanha@redhat.com \
--cc=tjdqudcks0424@naver.com \
--cc=vgoyal@redhat.com \
--cc=virtualization@lists.linux.dev \
/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.