Miklos Szeredi deee089a22 fuse: zero initialize inode private data ...

[ Upstream commit 3ca1b31118 ]

This is slightly tricky, since the VFS uses non-zeroing allocation to
preserve some fields that are left in a consistent state.

Reported-by: Chunsheng Luo <luochunsheng@ustc.edu>
Closes: https://lore.kernel.org/all/20250818083224.229-1-luochunsheng@ustc.edu/
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>

2025-11-13 15:34:15 -05:00

..

acl.c

…

control.c

…

cuse.c

…

dax.c

…

dev.c

fuse: fix possibly missing fuse_copy_finish() call in fuse_notify()

2025-10-19 16:33:49 +02:00

dir.c

fuse: fix race between concurrent setattrs from multiple nodes

2025-07-06 11:01:32 +02:00

file.c

fuse: fix livelock in synchronous file put from fuseblk workers

2025-10-19 16:33:50 +02:00

fuse_i.h

…

fuse_trace.h

…

inode.c

fuse: zero initialize inode private data

2025-11-13 15:34:15 -05:00

ioctl.c

…

iomode.c

…

Kconfig

…

Makefile

…

passthrough.c

fuse: do not allow mapping a non-regular backing file

2025-09-19 16:35:46 +02:00

readdir.c

…

virtio_fs.c

virtiofs: add filesystem context source name check

2025-04-25 10:47:55 +02:00

xattr.c

…