From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: virtio-fs@redhat.com, mszeredi@redhat.com, qemu-devel@nongnu.org,
stefanha@redhat.com
Subject: Re: [PATCH v4 2/9] virtiofsd: Fix breakage due to fuse_init_in size change
Date: Thu, 27 Jan 2022 17:17:38 +0000 [thread overview]
Message-ID: <YfLTsnyhTdylJn+u@work-vm> (raw)
In-Reply-To: <20220124212455.83968-3-vgoyal@redhat.com>
* Vivek Goyal (vgoyal@redhat.com) wrote:
> Kernel version 5.17 has increased the size of "struct fuse_init_in" struct.
> Previously this struct was 16 bytes and now it has been extended to
> 64 bytes in size.
>
> Once qemu headers are updated to latest, it will expect to receive 64 byte
> size struct (for protocol version major 7 and minor > 6). But if guest is
> booting older kernel (older than 5.17), then it still sends older
> fuse_init_in of size 16 bytes. And do_init() fails. It is expecting
> 64 byte struct. And this results in mount of virtiofs failing.
>
> Fix this by parsing 16 bytes only for now. Separate patches will be
> posted which will parse rest of the bytes and enable new functionality.
> Right now we don't support any of the new functionality, so we don't
> lose anything by not parsing bytes beyond 16.
>
> Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
OK, I think we should make this 1/9 and get this in quickly; that way
bisect works.
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
> tools/virtiofsd/fuse_lowlevel.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tools/virtiofsd/fuse_lowlevel.c b/tools/virtiofsd/fuse_lowlevel.c
> index e4679c73ab..ce29a70253 100644
> --- a/tools/virtiofsd/fuse_lowlevel.c
> +++ b/tools/virtiofsd/fuse_lowlevel.c
> @@ -1880,6 +1880,7 @@ static void do_init(fuse_req_t req, fuse_ino_t nodeid,
> struct fuse_mbuf_iter *iter)
> {
> size_t compat_size = offsetof(struct fuse_init_in, max_readahead);
> + size_t compat2_size = offsetof(struct fuse_init_in, flags) + sizeof(uint32_t);
Yeh so that sizeof() is sizeof the flags, so that's the size of the
sturcture upto and including the flags.
> struct fuse_init_in *arg;
> struct fuse_init_out outarg;
> struct fuse_session *se = req->se;
> @@ -1897,7 +1898,7 @@ static void do_init(fuse_req_t req, fuse_ino_t nodeid,
>
> /* ...and now consume the new fields. */
> if (arg->major == 7 && arg->minor >= 6) {
> - if (!fuse_mbuf_iter_advance(iter, sizeof(*arg) - compat_size)) {
> + if (!fuse_mbuf_iter_advance(iter, compat2_size - compat_size)) {
> fuse_reply_err(req, EINVAL);
> return;
> }
> --
> 2.31.1
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2022-01-27 18:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 21:24 [PATCH v4 0/9] virtiofsd: Add support for file security context at creation Vivek Goyal
2022-01-24 21:24 ` [PATCH v4 1/9] linux-headers: Update headers to v5.17-rc1 Vivek Goyal
2022-01-27 17:21 ` Dr. David Alan Gilbert
2022-01-27 18:06 ` Vivek Goyal
2022-01-27 19:42 ` Dr. David Alan Gilbert
2022-01-24 21:24 ` [PATCH v4 2/9] virtiofsd: Fix breakage due to fuse_init_in size change Vivek Goyal
2022-01-27 17:17 ` Dr. David Alan Gilbert [this message]
2022-01-24 21:24 ` [PATCH v4 3/9] virtiofsd: Parse extended "struct fuse_init_in" Vivek Goyal
2022-01-27 17:50 ` Dr. David Alan Gilbert
2022-01-27 18:21 ` Vivek Goyal
2022-01-24 21:24 ` [PATCH v4 4/9] virtiofsd: Extend size of fuse_conn_info->capable and ->want fields Vivek Goyal
2022-01-27 17:53 ` Dr. David Alan Gilbert
2022-01-27 18:31 ` Vivek Goyal
2022-01-24 21:24 ` [PATCH v4 5/9] virtiofsd, fuse_lowlevel.c: Add capability to parse security context Vivek Goyal
2022-01-24 21:24 ` [PATCH v4 6/9] virtiofsd: Move core file creation code in separate function Vivek Goyal
2022-01-27 19:50 ` Dr. David Alan Gilbert
2022-01-24 21:24 ` [PATCH v4 7/9] virtiofsd: Create new file with fscreate set Vivek Goyal
2022-01-24 21:24 ` [PATCH v4 8/9] virtiofsd: Create new file using O_TMPFILE and set security context Vivek Goyal
2022-01-24 21:24 ` [PATCH v4 9/9] virtiofsd: Add an option to enable/disable security label Vivek Goyal
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=YfLTsnyhTdylJn+u@work-vm \
--to=dgilbert@redhat.com \
--cc=mszeredi@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vgoyal@redhat.com \
--cc=virtio-fs@redhat.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 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).