Changes in Makefile

24fe962c - fuse: {io-uring} Handle SQEs - register commands

Mon, 20 Jan 2025 01:28:59 +0000

fuse: {io-uring} Handle SQEs - register commandsThis adds basic support for ring SQEs (with opcode=IORING_OP_URING_CMD).For now only FUSE_IO_URING_CMD_REGISTER is handled to register queueentries.Signed-off-by: Bernd Schubert Reviewed-by: Pavel Begunkov # io_uringReviewed-by: Luis Henriques Signed-off-by: Miklos Szeredi List of files: /linux-6.15/fs/fuse/Makefile

2b3933b1 - fuse: enable dynamic configuration of fuse max pages limit (FUSE_MAX_MAX_PAGES)

Mon, 23 Sep 2024 17:13:11 +0000

fuse: enable dynamic configuration of fuse max pages limit (FUSE_MAX_MAX_PAGES)Introduce the capability to dynamically configure the max pages limit(FUSE_MAX_MAX_PAGES) through a sysctl. This allows system administratorsto dynamically set the maximum number of pages that can be used forservicing requests in fuse.Previously, this is gated by FUSE_MAX_MAX_PAGES which is statically setto 256 pages. One result of this is that the buffer size for a writerequest is limited to 1 MiB on a 4k-page system.The default value for this sysctl is the original limit (256 pages).$ sysctl -a | grep max_pages_limitfs.fuse.max_pages_limit = 256$ sysctl -n fs.fuse.max_pages_limit256$ echo 1024 | sudo tee /proc/sys/fs/fuse/max_pages_limit1024$ sysctl -n fs.fuse.max_pages_limit1024$ echo 65536 | sudo tee /proc/sys/fs/fuse/max_pages_limittee: /proc/sys/fs/fuse/max_pages_limit: Invalid argument$ echo 0 | sudo tee /proc/sys/fs/fuse/max_pages_limittee: /proc/sys/fs/fuse/max_pages_limit: Invalid argument$ echo 65535 | sudo tee /proc/sys/fs/fuse/max_pages_limit65535$ sysctl -n fs.fuse.max_pages_limit65535Signed-off-by: Joanne Koong Reviewed-by: Josef Bacik Reviewed-by: Sweet Tea Dorminy Signed-off-by: Miklos Szeredi List of files: /linux-6.15/fs/fuse/Makefile

396b209e - fuse: add simple request tracepoints

Wed, 03 Jul 2024 14:38:42 +0000

fuse: add simple request tracepointsI've been timing various fuse operations and it's quite annoying to dowith kprobes. Add two tracepoints for sending and ending fuse requeststo make it easier to debug and time various operations.Signed-off-by: Josef Bacik Reviewed-by: Bernd Schubert Signed-off-by: Miklos Szeredi List of files: /linux-6.15/fs/fuse/Makefile

7dc4e97a - fuse: introduce FUSE_PASSTHROUGH capability

Fri, 09 Feb 2024 14:57:17 +0000

fuse: introduce FUSE_PASSTHROUGH capabilityFUSE_PASSTHROUGH capability to passthrough FUSE operations to backingfiles will be made available with kernel config CONFIG_FUSE_PASSTHROUGH.When requesting FUSE_PASSTHROUGH, userspace needs to specify themax_stack_depth that is allowed for FUSE on top of backing files.Introduce the flag FOPEN_PASSTHROUGH and backing_id to fuse_open_outargument that can be used when replying to OPEN request, to setuppassthrough of io operations on the fuse inode to a backing file.Introduce a refcounted fuse_backing object that will be used toassociate an open backing file with a fuse inode.Signed-off-by: Amir Goldstein Signed-off-by: Miklos Szeredi List of files: /linux-6.15/fs/fuse/Makefile

cb098dd2 - fuse: introduce inode io modes

Thu, 01 Feb 2024 14:26:15 +0000

fuse: introduce inode io modesThe fuse inode io mode is determined by the mode of its open files/mmapsand parallel dio opens and expressed in the value of fi->iocachectr: > 0 - caching io: files open in caching mode or mmap on direct_io file < 0 - parallel dio: direct io mode with parallel dio writes enabled== 0 - direct io: no files open in caching mode and no files mmapedNote that iocachectr value of 0 might become positive or negative,while non-parallel dio is getting processed.direct_io mmap uses page cache, so first mmap will mark the file asff->io_opened and increment fi->iocachectr to enter the caching io mode.If the server opens the file in caching mode while it is already openfor parallel dio or vice versa the open fails.This allows executing parallel dio when inode is not in caching modeand no mmaps have been performed on the inode in question.Signed-off-by: Bernd Schubert Signed-off-by: Amir Goldstein Signed-off-by: Miklos Szeredi List of files: /linux-6.15/fs/fuse/Makefile

9ac29fd3 - fuse: move ioctl to separate source file

Wed, 07 Apr 2021 12:36:45 +0000

fuse: move ioctl to separate source fileNext patch will expand ioctl code and fuse/file.c is large enough as it is.Signed-off-by: Miklos Szeredi List of files: /linux-6.15/fs/fuse/Makefile

1dd53957 - virtiofs: add a mount option to enable dax

Wed, 19 Aug 2020 22:19:47 +0000

virtiofs: add a mount option to enable daxAdd a mount option to allow using dax with virtio_fs.Signed-off-by: Vivek Goyal Signed-off-by: Miklos Szeredi List of files: /linux-6.15/fs/fuse/Makefile

112e7237 - virtio-fs: Change module name to virtiofs.ko

Fri, 11 Oct 2019 18:18:26 +0000

virtio-fs: Change module name to virtiofs.koWe have been calling it virtio_fs and even file name is virtio_fs.c. Modulename is virtio_fs.ko but when registering file system user is supposed tospecify filesystem type as "virtiofs".Masayoshi Mizuma reported that he specified filesytem type as "virtio_fs"and got this warning on console. ------------[ cut here ]------------ request_module fs-virtio_fs succeeded, but still no fs? WARNING: CPU: 1 PID: 1234 at fs/filesystems.c:274 get_fs_type+0x12c/0x138 Modules linked in: ... virtio_fs fuse virtio_net net_failover ... CPU: 1 PID: 1234 Comm: mount Not tainted 5.4.0-rc1 #1So looks like kernel could find the module virtio_fs.ko but could not findfilesystem type after that.It probably is better to rename module name to virtiofs.ko so that abovewarning goes away in case user ends up specifying wrong fs name.Reported-by: Masayoshi Mizuma Suggested-by: Stefan Hajnoczi Signed-off-by: Vivek Goyal Tested-by: Masayoshi Mizuma Reviewed-by: Stefan Hajnoczi Signed-off-by: Miklos Szeredi List of files: /linux-6.15/fs/fuse/Makefile

a62a8ef9 - virtio-fs: add virtiofs filesystem

Tue, 12 Jun 2018 08:41:17 +0000

virtio-fs: add virtiofs filesystemAdd a basic file system module for virtio-fs. This does not yet containshared data support between host and guest or metadata coherency speedups.However it is already significantly faster than virtio-9p.Design Overview===============With the goal of designing something with better performance and local filesystem semantics, a bunch of ideas were proposed. - Use fuse protocol (instead of 9p) for communication between guest and host. Guest kernel will be fuse client and a fuse server will run on host to serve the requests. - For data access inside guest, mmap portion of file in QEMU address space and guest accesses this memory using dax. That way guest page cache is bypassed and there is only one copy of data (on host). This will also enable mmap(MAP_SHARED) between guests. - For metadata coherency, there is a shared memory region which contains version number associated with metadata and any guest changing metadata updates version number and other guests refresh metadata on next access. This is yet to be implemented.How virtio-fs differs from existing approaches==============================================The unique idea behind virtio-fs is to take advantage of the co-location ofthe virtual machine and hypervisor to avoid communication (vmexits).DAX allows file contents to be accessed without communication with thehypervisor. The shared memory region for metadata avoids communication inthe common case where metadata is unchanged.By replacing expensive communication with cheaper shared memory accesses,we expect to achieve better performance than approaches based on networkfile system protocols. In addition, this also makes it easier to achievelocal file system semantics (coherency).These techniques are not applicable to network file system protocols sincethe communications channel is bypassed by taking advantage of shared memoryon a local machine. This is why we decided to build virtio-fs rather thanfocus on 9P or NFS.Caching Modes=============Like virtio-9p, different caching modes are supported which determine thecoherency level as well. The “cache=FOO” and “writeback” options controlthe level of coherence between the guest and host filesystems. - cache=none metadata, data and pathname lookup are not cached in guest. They are always fetched from host and any changes are immediately pushed to host. - cache=always metadata, data and pathname lookup are cached in guest and never expire. - cache=auto metadata and pathname lookup cache expires after a configured amount of time (default is 1 second). Data is cached while the file is open (close to open consistency). - writeback/no_writeback These options control the writeback strategy. If writeback is disabled, then normal writes will immediately be synchronized with the host fs. If writeback is enabled, then writes may be cached in the guest until the file is closed or an fsync(2) performed. This option has no effect on mmap-ed writes or writes going through the DAX mechanism.Signed-off-by: Stefan Hajnoczi Signed-off-by: Vivek Goyal Acked-by: Michael S. Tsirkin Signed-off-by: Miklos Szeredi List of files: /linux-6.15/fs/fuse/Makefile

ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig

Sun, 19 May 2019 12:07:45 +0000

treewide: Add SPDX license identifier - Makefile/KconfigAdd SPDX license identifiers to all Make/Kconfig files which: - Have no license information of any formThese files fall under the project license, GPL v2 only. The resulting SPDXlicense identifier is: GPL-2.0-onlySigned-off-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/fs/fuse/Makefile

d123d8e1 - fuse: split out readdir.c

Fri, 28 Sep 2018 14:43:23 +0000

fuse: split out readdir.cDirectory reading code is about to grow larger, so split it out from dir.cinto a new source file.Signed-off-by: Miklos Szeredi List of files: /linux-6.15/fs/fuse/Makefile

60bcc88a - fuse: Add posix ACL support

Mon, 29 Aug 2016 13:46:37 +0000

fuse: Add posix ACL supportAdd a new INIT flag, FUSE_POSIX_ACL, for negotiating ACL support withuserspace. When it is set in the INIT response, ACL support will beenabled. ACL support also implies "default_permissions".When ACL support is enabled, the kernel will cache and have responsibilityfor enforcing ACLs. ACL xattrs will be passed to userspace, which isresponsible for updating the ACLs in the filesystem, keeping the file modein sync, and inheritance of default ACLs when new filesystem nodes arecreated.Signed-off-by: Seth Forshee Signed-off-by: Miklos Szeredi List of files: /linux-6.15/fs/fuse/Makefile

703c7362 - fuse: Use generic xattr ops

Mon, 29 Aug 2016 13:46:36 +0000

fuse: Use generic xattr opsIn preparation for posix acl support, rework fuse to use xattr handlers andthe generic setxattr/getxattr/listxattr callbacks. Split the xattr codeout into it's own file, and promote symbols to module-global scope asneeded.Functionally these changes have no impact, as fuse still uses a singlehandler for all xattrs which uses the old callbacks.Signed-off-by: Seth Forshee Signed-off-by: Miklos Szeredi List of files: /linux-6.15/fs/fuse/Makefile

151060ac - CUSE: implement CUSE - Character device in Userspace

Tue, 14 Apr 2009 01:54:54 +0000

CUSE: implement CUSE - Character device in UserspaceCUSE enables implementing character devices in userspace. With recentadditions of ioctl and poll support, FUSE already has most of what'snecessary to implement character devices. All CUSE has to do isbonding all those components - FUSE, chardev and the driver model -nicely.When client opens /dev/cuse, kernel starts conversation withCUSE_INIT. The client tells CUSE which device it wants to create. Asthe previous patch made fuse_file usable without associatedfuse_inode, CUSE doesn't create super block or inodes. It attachesfuse_file to cdev file->private_data during open and set ff->fi toNULL. The rest of the operation is almost identical to FUSE direct IOcase.Each CUSE device has a corresponding directory /sys/class/cuse/DEVNAME(which is symlink to /sys/devices/virtual/class/DEVNAME ifSYSFS_DEPRECATED is turned off) which hosts "waiting" and "abort"among other things. Those two files have the same meaning as the FUSEcontrol files.The only notable lacking feature compared to in-kernel implementationis mmap support.Signed-off-by: Tejun Heo Signed-off-by: Miklos Szeredi List of files: /linux-6.15/fs/fuse/Makefile

bafa9654 - [PATCH] fuse: add control filesystem

Sun, 25 Jun 2006 12:48:51 +0000

[PATCH] fuse: add control filesystemAdd a control filesystem to fuse, replacing the attributes currently exportedthrough sysfs. An empty directory '/sys/fs/fuse/connections' is still createdin sysfs, and mounting the control filesystem here provides backwardcompatibility.Advantages of the control filesystem over the previous solution: - allows the object directory and the attributes to be owned by the filesystem owner, hence letting unpriviled users abort the filesystem connection - does not suffer from module unload race[akpm@osdl.org: fix this fs for recent dhowells depredations][akpm@osdl.org: fix 64-bit printk warnings]Signed-off-by: Miklos Szeredi Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/fs/fuse/Makefile

b6aeaded - [PATCH] FUSE - file operations

Fri, 09 Sep 2005 20:10:30 +0000

[PATCH] FUSE - file operationsThis patch adds the file operations of FUSE.The following operations are added: o open o flush o release o fsync o readpage o commit_writeSigned-off-by: Miklos Szeredi Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/fs/fuse/Makefile

e5e5558e - [PATCH] FUSE - read-only operations

Fri, 09 Sep 2005 20:10:28 +0000

[PATCH] FUSE - read-only operationsThis patch adds the read-only filesystem operations of FUSE.This contains the following files: o dir.c - directory, symlink and file-inode operationsThe following operations are added: o lookup o getattr o readlink o follow_link o directory open o readdir o directory release o permission o dentry revalidate o statfsSigned-off-by: Miklos Szeredi Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/fs/fuse/Makefile

334f485d - [PATCH] FUSE - device functions

Fri, 09 Sep 2005 20:10:27 +0000

[PATCH] FUSE - device functionsThis adds the FUSE device handling functions.This contains the following files: o dev.c - fuse device operations (read, write, release, poll) - registers misc device - support for sending requests to userspaceSigned-off-by: Miklos Szeredi Signed-off-by: Adrian Bunk Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/fs/fuse/Makefile

d8a5ba45 - [PATCH] FUSE - core

Fri, 09 Sep 2005 20:10:26 +0000

[PATCH] FUSE - coreThis patch adds FUSE core.This contains the following files: o inode.c - superblock operations (alloc_inode, destroy_inode, read_inode, clear_inode, put_super, show_options) - registers FUSE filesystem o fuse_i.h - private header fileRequirements============ The most important difference between orinary filesystems and FUSE is the fact, that the filesystem data/metadata is provided by a userspace process run with the privileges of the mount "owner" instead of the kernel, or some remote entity usually running with elevated privileges. The security implication of this is that a non-privileged user must not be able to use this capability to compromise the system. Obvious requirements arising from this are: - mount owner should not be able to get elevated privileges with the help of the mounted filesystem - mount owner should not be able to induce undesired behavior in other users' or the super user's processes - mount owner should not get illegitimate access to information from other users' and the super user's processes These are currently ensured with the following constraints: 1) mount is only allowed to directory or file which the mount owner can modify without limitation (write access + no sticky bit for directories) 2) nosuid,nodev mount options are forced 3) any process running with fsuid different from the owner is denied all access to the filesystem 1) and 2) are ensured by the "fusermount" mount utility which is a setuid root application doing the actual mount operation. 3) is ensured by a check in the permission() method in kernel I started thinking about doing 3) in a different way because Christoph H. made a big deal out of it, saying that FUSE is unacceptable into mainline in this form. The suggested use of private namespaces would be OK, but in their current form have many limitations that make their use impractical (as discussed in this thread). Suggested improvements that would address these limitations: - implement shared subtrees - allow a process to join an existing namespace (make namespaces first-class objects) - implement the namespace creation/joining in a PAM module With all that in place the check of owner against current->fsuid may be removed from the FUSE kernel module, without compromising the security requirements. Suid programs still interesting questions, since they get access even to the private namespace causing some information leak (exact order/timing of filesystem operations performed), giving some ptrace-like capabilities to unprivileged users. BTW this problem is not strictly limited to the namespace approach, since suid programs setting fsuid and accessing users' files will succeed with the current approach too.Signed-off-by: Miklos Szeredi Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/fs/fuse/Makefile