qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: qemu-devel@nongnu.org, virtio-fs@redhat.com
Cc: mszeredi@redhat.com, berrange@redhat.com, dgilbert@redhat.com,
	vgoyal@redhat.com
Subject: [PATCH v6 04/10] virtiofsd: Extend size of fuse_conn_info->capable and ->want fields
Date: Tue,  8 Feb 2022 15:48:07 -0500	[thread overview]
Message-ID: <20220208204813.682906-5-vgoyal@redhat.com> (raw)
In-Reply-To: <20220208204813.682906-1-vgoyal@redhat.com>

->capable keeps track of what capabilities kernel supports and ->wants keep
track of what capabilities filesytem wants.

Right now these fields are 32bit in size. But now fuse has run out of
bits and capabilities can now have bit number which are higher than 31.

That means 32 bit fields are not suffcient anymore. Increase size to 64
bit so that we can add newer capabilities and still be able to use existing
code to check and set the capabilities.

Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
---
 tools/virtiofsd/fuse_common.h   | 4 ++--
 tools/virtiofsd/fuse_lowlevel.c | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/tools/virtiofsd/fuse_common.h b/tools/virtiofsd/fuse_common.h
index 0c2665b977..6f8a988202 100644
--- a/tools/virtiofsd/fuse_common.h
+++ b/tools/virtiofsd/fuse_common.h
@@ -439,7 +439,7 @@ struct fuse_conn_info {
     /**
      * Capability flags that the kernel supports (read-only)
      */
-    unsigned capable;
+    uint64_t capable;
 
     /**
      * Capability flags that the filesystem wants to enable.
@@ -447,7 +447,7 @@ struct fuse_conn_info {
      * libfuse attempts to initialize this field with
      * reasonable default values before calling the init() handler.
      */
-    unsigned want;
+    uint64_t want;
 
     /**
      * Maximum number of pending "background" requests. A
diff --git a/tools/virtiofsd/fuse_lowlevel.c b/tools/virtiofsd/fuse_lowlevel.c
index b6712b763a..d91cd9743a 100644
--- a/tools/virtiofsd/fuse_lowlevel.c
+++ b/tools/virtiofsd/fuse_lowlevel.c
@@ -2069,7 +2069,7 @@ static void do_init(fuse_req_t req, fuse_ino_t nodeid,
     if (se->conn.want & (~se->conn.capable)) {
         fuse_log(FUSE_LOG_ERR,
                  "fuse: error: filesystem requested capabilities "
-                 "0x%x that are not supported by kernel, aborting.\n",
+                 "0x%llx that are not supported by kernel, aborting.\n",
                  se->conn.want & (~se->conn.capable));
         fuse_reply_err(req, EPROTO);
         se->error = -EPROTO;
-- 
2.34.1



  parent reply	other threads:[~2022-02-08 21:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 20:48 [PATCH v6 00/10] virtiofsd: Add support for file security context at file creation Vivek Goyal
2022-02-08 20:48 ` [PATCH v6 01/10] virtiofsd: Fix breakage due to fuse_init_in size change Vivek Goyal
2022-02-08 20:48 ` [PATCH v6 02/10] linux-headers: Update headers to v5.17-rc1 Vivek Goyal
2022-02-08 20:48 ` [PATCH v6 03/10] virtiofsd: Parse extended "struct fuse_init_in" Vivek Goyal
2022-02-14 12:22   ` Dr. David Alan Gilbert
2022-02-08 20:48 ` Vivek Goyal [this message]
2022-02-08 20:48 ` [PATCH v6 05/10] virtiofsd, fuse_lowlevel.c: Add capability to parse security context Vivek Goyal
2022-02-14 13:02   ` Dr. David Alan Gilbert
2022-02-08 20:48 ` [PATCH v6 06/10] virtiofsd: Move core file creation code in separate function Vivek Goyal
2022-02-08 20:48 ` [PATCH v6 07/10] virtiofsd: Add helpers to work with /proc/self/task/tid/attr/fscreate Vivek Goyal
2022-02-08 20:48 ` [PATCH v6 08/10] virtiofsd: Create new file with security context Vivek Goyal
2022-02-08 20:48 ` [PATCH v6 09/10] virtiofsd: Create new file using O_TMPFILE and set " Vivek Goyal
2022-02-08 20:48 ` [PATCH v6 10/10] virtiofsd: Add an option to enable/disable security label Vivek Goyal
2022-02-14 13:32   ` Dr. David Alan Gilbert
2022-02-14 14:10     ` Vivek Goyal
2022-02-16 12:08 ` [PATCH v6 00/10] virtiofsd: Add support for file security context at file creation Dr. David Alan Gilbert

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=20220208204813.682906-5-vgoyal@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=mszeredi@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --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).