From: Florian Weimer <fweimer@redhat.com>
To: fuse-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Recommended version handshake for FUSE clients
Date: Mon, 26 Aug 2024 14:22:24 +0200 [thread overview]
Message-ID: <87seurv5hb.fsf@oldenburg.str.redhat.com> (raw)
I cannot use libfuse, so I'm writing my own mini-wrapper directly on top
of the kernel interface. For the major version handshake, I understand
that I need to reply with version 7 if a later major version is
required. But what to do about the minor version?
Should I use the minimum version that is expected to work (because there
have not been any struct layout changes since)? I think this could end
up problematic if some struct sizes have grown between the known-good
minimum version and the <linux/fuse.h> version, something that a future
<linux/fuse.h> version might bring.
Or should I just send back FUSE_KERNEL_MINOR_VERSION from the system
version of <linux/fuse.h>? I think this assumes that merely increasing
the minor version does not result in behavioral changes (such as
additonal FUSE events being generated that the current code knows
nothing about).
The code only has to run on the system that it was compiled on and
possibly newer kernels. Going back to older kernels is not needed. But
I also expect people using a wide range of kernel header versions to
compile this code.
Or perhaps I should bundle some older version of <linux/fuse.h> with my
sources?
Thanks,
Florian
next reply other threads:[~2024-08-26 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 12:22 Florian Weimer [this message]
2024-08-26 12:26 ` Recommended version handshake for FUSE clients Miklos Szeredi
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=87seurv5hb.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).