summaryrefslogtreecommitdiff
path: root/rust/kernel/alloc/allocator
diff options
context:
space:
mode:
authorMiklos Szeredi <mszeredi@redhat.com>2026-11-09 15:45:55 +0100
committerMiklos Szeredi <mszeredi@redhat.com>2026-11-19 18:25:59 +0100
commitf7e0ed317736fb33d18e0b903743c2d7f9faa92c (patch)
tree713dfbb327627f5d8f4301a8a6f659709865e6a2 /rust/kernel/alloc/allocator
parenta8fdb9d75e7988e637816492ff08d51cff5dabd7 (diff)
fuse: don't mark inode DAX without CONFIG_FS_DAX
fuse_init_inode() installs fuse_dax_aops and sets S_DAX for any regular file whose lookup reply carries FUSE_ATTR_DAX. Without CONFIG_FS_DAX, S_DAX is zero and IS_DAX() is constant false, so all of the checks that keep such inodes away from the page cache are compiled out: the "DAX inode without FOPEN_PASSTHROUGH" rejection in fuse_file_io_open(), the O_TRUNC check in fuse_open(), the truncate check in fuse_do_setattr(), the check in fuse_file_fallocate() and the one in fuse_passthrough_open(). The address space operations are installed regardless, so the inode ends up in caching I/O mode with aops that have neither ->read_folio nor ->readahead, and a buffered read, mmap fault or splice oopses on a NULL callback. Any user able to mount a fuse filesystem can trigger this. Only honor FUSE_ATTR_DAX if DAX can work at all. Fixes: 2fbe4586cff3 ("fuse: add support for opening dax device as backing") Reported-by: Sashiko <sashiko-bot@kernel.org> Closes: https://sashiko.dev/#/bug/linux-bb232f07-d992-4dc6-a6c5-400e98e7133f Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Diffstat (limited to 'rust/kernel/alloc/allocator')
0 files changed, 0 insertions, 0 deletions