Public bug reported:
Hello,
I just noticed that the backport of this patch was not done for
linux-6.2 and linux-6.3, I guess because there had been a merge
conflict. I think in the mean time these versions are not maintained
anymore, so sending a version that fixes the merge conflict is probably
not going to help.
Issue is that libfuse currently uses a version check instead of testing
for the corresponding feature, which is troublesome with any kind of
feature back port. I.e., if the feature back port increases the version
number, it would enable the "FUSE_EXPIRE_ONLY" although possibly not
back ported. If the back port does not increase the version number, it
might be used by libfuse...
commit 5cadfbd5a11e5495cac217534c5f788168b1afd7
Author: Miklos Szeredi <mszer...@redhat.com>
Date: Mon Mar 27 16:14:49 2023 +0200
fuse: add feature flag for expire-only
Add an init flag idicating whether the FUSE_EXPIRE_ONLY flag of
FUSE_NOTIFY_INVAL_ENTRY is effective.
This is needed for backports of this feature, otherwise the server could
just check the protocol version.
Fixes: 4f8d37020e1f ("fuse: add "expire only" mode to
FUSE_NOTIFY_INVAL_ENTRY")
Cc: <sta...@vger.kernel.org> # v6.2
Signed-off-by: Miklos Szeredi <mszer...@redhat.com>
** Affects: linux-hwe-6.2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2051700
Title:
Missing fuse backport: "fuse: add feature flag for expire-only"
Status in linux-hwe-6.2 package in Ubuntu:
New
Bug description:
Hello,
I just noticed that the backport of this patch was not done for
linux-6.2 and linux-6.3, I guess because there had been a merge
conflict. I think in the mean time these versions are not maintained
anymore, so sending a version that fixes the merge conflict is
probably not going to help.
Issue is that libfuse currently uses a version check instead of
testing for the corresponding feature, which is troublesome with any
kind of feature back port. I.e., if the feature back port increases
the version number, it would enable the "FUSE_EXPIRE_ONLY" although
possibly not back ported. If the back port does not increase the
version number, it might be used by libfuse...
commit 5cadfbd5a11e5495cac217534c5f788168b1afd7
Author: Miklos Szeredi <mszer...@redhat.com>
Date: Mon Mar 27 16:14:49 2023 +0200
fuse: add feature flag for expire-only
Add an init flag idicating whether the FUSE_EXPIRE_ONLY flag of
FUSE_NOTIFY_INVAL_ENTRY is effective.
This is needed for backports of this feature, otherwise the server could
just check the protocol version.
Fixes: 4f8d37020e1f ("fuse: add "expire only" mode to
FUSE_NOTIFY_INVAL_ENTRY")
Cc: <sta...@vger.kernel.org> # v6.2
Signed-off-by: Miklos Szeredi <mszer...@redhat.com>
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2051700/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
