fuse: Apply flags2 only when userspace set the FUSE_INIT_EXT
authorBernd Schubert <bschubert@ddn.com>
Fri, 15 Apr 2022 11:53:56 +0000 (13:53 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 27 Jul 2023 06:50:25 +0000 (08:50 +0200)
commit549f5093e9d6d19d21dc4d5a763b7ec294a8af90
treee0b69e497241c75b6d1ce654a670fa262291a1ae
parentaf6d1fc5b8a68c790e3da09ff5dfb61eff63cca0
fuse: Apply flags2 only when userspace set the FUSE_INIT_EXT

commit 3066ff93476c35679cb07a97cce37d9bb07632ff upstream.

This is just a safety precaution to avoid checking flags on memory that was
initialized on the user space side.  libfuse zeroes struct fuse_init_out
outarg, but this is not guranteed to be done in all implementations.
Better is to act on flags and to only apply flags2 when FUSE_INIT_EXT is
set.

There is a risk with this change, though - it might break existing user
space libraries, which are already using flags2 without setting
FUSE_INIT_EXT.

The corresponding libfuse patch is here
https://github.com/libfuse/libfuse/pull/662

Signed-off-by: Bernd Schubert <bschubert@ddn.com>
Fixes: 53db28933e95 ("fuse: extend init flags")
Cc: <stable@vger.kernel.org> # v5.17
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/fuse/inode.c