diff options
| author | Miklos Szeredi <mszeredi@redhat.com> | 2026-11-10 11:26:55 +0100 |
|---|---|---|
| committer | Miklos Szeredi <mszeredi@redhat.com> | 2026-11-19 18:25:59 +0100 |
| commit | 6704a78171aa20caab2cd16da9ae2ff8edd4bb1d (patch) | |
| tree | f956689c043c4e686ff39415ffcf8cb3838ec0cf /rust | |
| parent | f7e0ed317736fb33d18e0b903743c2d7f9faa92c (diff) | |
fuse: advertise support for DAX mappings
Reuse the FUSE_HAS_INODE_DAX flag, which previously was only used for the
virtiofs case.
The two uses are unrelated: for virtiofs the flag means that host memory
can be mapped directly into the guest, while here it means that the server
may back an inode with a dax device opened via FUSE_DEV_IOC_BACKING_OPEN.
Gate the advertisement on IS_REACHABLE(CONFIG_DEV_DAX_FSDEV), which is
what fuse_backing_open_file() requires before it accepts a dax device as
backing; CONFIG_FS_DAX alone is not sufficient.
Plain fuse servers should check both FUSE_HAS_INODE_DAX and
FUSE_PASSTHROUGH_V2 before enabling passthrough dax support.
Stop advertising FUSE_PASSTHROUGH(_V2) in the virtiofs case, which doesn't
support passthrough mode.
Note: FUSE_HAS_INODE_DAX flag in the INIT reply is ignored, so it's handled
slightly differently from the virtiofs case. This is deliberate. The
server needs to check both FUSE_PASSTHROUGH_V2 and FUSE_HAS_INODE_DAX
before enabling DAX based extent map if it wants to bail or fall back to
plain I/O mode on kernels not supporting this feature. A broken server
that does not check the features yet sets FUSE_ATTR_DAX will result in an
error on open. This is not backward compatible, since this flag was
silently ignored previously, but unlikely to be an issue in real life.
Fixes: 2fbe4586cff3 ("fuse: add support for opening dax device as backing")
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Diffstat (limited to 'rust')
0 files changed, 0 insertions, 0 deletions
