android_kernel_motorola_sm6375/fs/fuse
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Daniel Rosenberg 4e5cea6bec
UPSTREAM: ANDROID: fuse-bpf: Always call revalidate for backing
If we have a backing dentry, we must call it's revalidate always, or we
may end up using an invalid lower dentry. Revalidate is called for
dentries, not inodes, and the dentry may be negative. This goes against
all of the macro conventions, so we're just calling the backing function
directly.

Signed-off-by: Daniel Rosenberg <drosen@google.com>
Bug: 219958836
Test: fuse_test
Change-Id: Ia28da5bd2ce42b40466c577137d5440d9f2f6600
2026-05-08 21:46:17 +02:00
..
acl.c
backing.c UPSTREAM: ANDROID: fuse-bpf: Always call revalidate for backing 2026-05-08 21:46:17 +02:00
control.c UPSTREAM: ANDROID: fuse-bpf: Use cache and refcount 2026-05-08 21:46:16 +02:00
cuse.c
dax.c
dev.c
dir.c UPSTREAM: ANDROID: fuse-bpf: Always call revalidate for backing 2026-05-08 21:46:17 +02:00
file.c UPSTREAM: ANDROID: fuse-bpf: Fix read_iter 2026-05-08 21:46:16 +02:00
fuse_i.h UPSTREAM: ANDROID: fuse-bpf: Always call revalidate for backing 2026-05-08 21:46:17 +02:00
inode.c UPSTREAM: ANDROID: fuse-bpf: Make inodes with backing_fd reachable 2026-05-08 21:46:17 +02:00
Kconfig
Makefile
OWNERS
passthrough.c BACKPORT: vfs: add vfs_iocb_iter_[read|write] helper functions 2026-05-08 21:46:16 +02:00
readdir.c UPSTREAM: ANDROID: fuse: Don't use readdirplus w/ nodeid 0 2026-05-08 21:46:17 +02:00
virtio_fs.c
xattr.c