From 191c0565a15564c6fb4e1c985e9a1862d8ba3698 Mon Sep 17 00:00:00 2001 From: Stefano Duo Date: Mon, 13 Jul 2020 08:03:44 +0000 Subject: sys/linux/fs_fuse.txt: define FUSE request id as a resource Currently fuse_in.unique and fuse_out.unique are not linked by any dependency chain. This causes the majority of the replies to the kernel to be dropped because not referring to a previously sent request. By defining them as a resource, we push the fuzzer in the right direction (i.e., try to respond using a previously issued unique value). The read syscall has been updated accordingly, it now expects and parses a fuse_in header and some additional data. --- sys/linux/fs_fuse.txt.const | 1 + 1 file changed, 1 insertion(+) (limited to 'sys/linux/fs_fuse.txt.const') diff --git a/sys/linux/fs_fuse.txt.const b/sys/linux/fs_fuse.txt.const index 408de1c12..13044a2de 100644 --- a/sys/linux/fs_fuse.txt.const +++ b/sys/linux/fs_fuse.txt.const @@ -26,6 +26,7 @@ FUSE_IOCTL_RETRY = 4 FUSE_KERNEL_MINOR_VERSION = 31 FUSE_KERNEL_VERSION = 7 FUSE_MAX_PAGES = 4194304 +FUSE_MIN_READ_BUFFER = 8192 FUSE_NOTIFY_DELETE = 6 FUSE_NOTIFY_INVAL_ENTRY = 3 FUSE_NOTIFY_INVAL_INODE = 2 -- cgit mrf-deployment