From: Stefan Hajnoczi <stefanha@gmail.com>
To: Li Wang <liwang@kylinos.cn>
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>,
virtualization@lists.linux.dev, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] virtiofs: Verify that server properly follows FUSE protocol
Date: Fri, 20 Mar 2026 11:00:05 -0400 [thread overview]
Message-ID: <CAJSP0QXErw8yDeCnOgK6jco1-yDpS5x73vQLMtrj7oy7JxNEFg@mail.gmail.com> (raw)
In-Reply-To: <20260319025609.10721-1-liwang@kylinos.cn>
On Wed, Mar 18, 2026 at 10:58 PM Li Wang <liwang@kylinos.cn> wrote:
>
> Verify that server properly follows FUSE protocol, by checking
> oh.uniq and oh.len.
>
> Signed-off-by: Li Wang <liwang@kylinos.cn>
> ---
> fs/fuse/virtio_fs.c | 27 ++++++++++++++++++++++++++-
> 1 file changed, 26 insertions(+), 1 deletion(-)
Earlier patch series addressing this:
- https://lore.kernel.org/all/20251028200311.40372-1-brajeshpatil11@gmail.com/
- https://lore.kernel.org/all/20260216073158.75151-1-ytohnuki@amazon.com/
The second one was applied and I think your version conflicts with it.
Please take a look and let us know whether you want to drop your patch
or send a v2 rebased on Miklos latest tree
(https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git).
Thanks,
Stefan
>
> diff --git a/fs/fuse/virtio_fs.c b/fs/fuse/virtio_fs.c
> index 057e65b51b99..c30f6f58664c 100644
> --- a/fs/fuse/virtio_fs.c
> +++ b/fs/fuse/virtio_fs.c
> @@ -768,10 +768,34 @@ static void virtio_fs_request_complete(struct fuse_req *req,
> struct folio *folio;
>
> /*
> - * TODO verify that server properly follows FUSE protocol
> + * Verify that server properly follows FUSE protocol
> * (oh.uniq, oh.len)
> */
> args = req->args;
> + if (test_bit(FR_ISREPLY, &req->flags)) {
> + struct fuse_out_header *oh = &req->out.h;
> +
> + if (unlikely(oh->unique != req->in.h.unique)) {
> + pr_warn_ratelimited("virtio-fs: bad reply unique %llu (expected %llu)\n",
> + oh->unique, req->in.h.unique);
> + oh->error = -EIO;
> + oh->len = sizeof(*oh);
> + goto out;
> + }
> + unsigned int num_out = args->out_numargs - args->out_pages;
> + unsigned int cap = sizeof(req->out.h);
> +
> + cap += fuse_len_args(num_out, args->out_args);
> + if (args->out_pages)
> + cap += args->out_args[args->out_numargs - 1].size;
> + if (unlikely(oh->len < sizeof(*oh) || oh->len > cap)) {
> + pr_warn_ratelimited("virtio-fs: bad reply len %u (cap %u)\n",
> + oh->len, cap);
> + oh->error = -EIO;
> + oh->len = sizeof(*oh);
> + goto out;
> + }
> + }
> copy_args_from_argbuf(args, req);
>
> if (args->out_pages && args->page_zeroing) {
> @@ -790,6 +814,7 @@ static void virtio_fs_request_complete(struct fuse_req *req,
> }
> }
>
> +out:
> clear_bit(FR_SENT, &req->flags);
>
> fuse_request_end(req);
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2026-03-20 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 2:56 [PATCH] virtiofs: Verify that server properly follows FUSE protocol Li Wang
2026-03-20 15:00 ` Stefan Hajnoczi [this message]
2026-03-23 1:58 ` Li Wang
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=CAJSP0QXErw8yDeCnOgK6jco1-yDpS5x73vQLMtrj7oy7JxNEFg@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=eperezma@redhat.com \
--cc=gmaglione@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=liwang@kylinos.cn \
--cc=miklos@szeredi.hu \
--cc=stefanha@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox