linux-toradex.git/fs/fuse/Makefile, branch master

fuse: create notify.c

2026-06-15T12:06:17+00:00

Move FUSE_NOTIFY_* handling into a separate source file.

Signed-off-by: Miklos Szeredi

fuse: create poll.c

2026-06-15T12:06:17+00:00

Move f_op->poll related functions to the new source file.

Signed-off-by: Miklos Szeredi

fuse: split out filesystem part of request sending

2026-06-15T12:06:17+00:00

Create a new source file: req.c and add the request sending entry
functions:

  __fuse_simple_request()
  fuse_simple_background()
  fuse_simple_notify_reply()

Introduce transport layer sending functions that are called by the
respective fs layer function:

  fuse_chan_send()
  fuse_chan_send_bg()
  fuse_chan_send_notify_reply()

Move calculation of request header fields uid, gid and pid from
fuse_get_req() and fuse_force_creads() to a new helper: fuse_fill_creds().

These fileds are now passed to the transport layer via struct fuse_args.

Signed-off-by: Miklos Szeredi

fuse: move request timeout code to a new source file

2026-06-15T12:06:15+00:00

This marks the first step in cleanly separating the transport layer from
the filesystem layer.

Add "dev.h", which will contain the interface definition for the transport
layer.

Signed-off-by: Miklos Szeredi

fuse: move CREATE_TRACE_POINTS to a separate file

2025-09-25T14:22:18+00:00

Before we start adding new tracepoints for fuse+iomap, move the
tracepoint creation itself to a separate source file so that we don't
have to start pulling iomap dependencies into dev.c just for the iomap
structures.

Signed-off-by: Darrick J. Wong 
Signed-off-by: Miklos Szeredi

fuse: move the backing file idr and code into a new source file

2025-09-25T14:06:02+00:00

iomap support for fuse is also going to want the ability to attach
backing files to a fuse filesystem.  Move the fuse_backing code into a
separate file so that both can use it.

Signed-off-by: Darrick J. Wong 
Reviewed-by: Amir Goldstein 
Signed-off-by: Miklos Szeredi

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

2025-01-24T10:54:08+00:00

This adds basic support for ring SQEs (with opcode=IORING_OP_URING_CMD).
For now only FUSE_IO_URING_CMD_REGISTER is handled to register queue
entries.

Signed-off-by: Bernd Schubert 
Reviewed-by: Pavel Begunkov  # io_uring
Reviewed-by: Luis Henriques 
Signed-off-by: Miklos Szeredi

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

2024-10-25T15:05:49+00:00

Introduce the capability to dynamically configure the max pages limit
(FUSE_MAX_MAX_PAGES) through a sysctl. This allows system administrators
to dynamically set the maximum number of pages that can be used for
servicing requests in fuse.

Previously, this is gated by FUSE_MAX_MAX_PAGES which is statically set
to 256 pages. One result of this is that the buffer size for a write
request 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_limit
fs.fuse.max_pages_limit = 256

$ sysctl -n fs.fuse.max_pages_limit
256

$ echo 1024 | sudo tee /proc/sys/fs/fuse/max_pages_limit
1024

$ sysctl -n fs.fuse.max_pages_limit
1024

$ echo 65536 | sudo tee /proc/sys/fs/fuse/max_pages_limit
tee: /proc/sys/fs/fuse/max_pages_limit: Invalid argument

$ echo 0 | sudo tee /proc/sys/fs/fuse/max_pages_limit
tee: /proc/sys/fs/fuse/max_pages_limit: Invalid argument

$ echo 65535 | sudo tee /proc/sys/fs/fuse/max_pages_limit
65535

$ sysctl -n fs.fuse.max_pages_limit
65535

Signed-off-by: Joanne Koong 
Reviewed-by: Josef Bacik 
Reviewed-by: Sweet Tea Dorminy 
Signed-off-by: Miklos Szeredi

fuse: add simple request tracepoints

2024-08-29T09:43:13+00:00

I've been timing various fuse operations and it's quite annoying to do
with kprobes.  Add two tracepoints for sending and ending fuse requests
to make it easier to debug and time various operations.

Signed-off-by: Josef Bacik 
Reviewed-by: Bernd Schubert 
Signed-off-by: Miklos Szeredi

fuse: introduce FUSE_PASSTHROUGH capability

2024-02-23T16:36:32+00:00

FUSE_PASSTHROUGH capability to passthrough FUSE operations to backing
files will be made available with kernel config CONFIG_FUSE_PASSTHROUGH.

When requesting FUSE_PASSTHROUGH, userspace needs to specify the
max_stack_depth that is allowed for FUSE on top of backing files.

Introduce the flag FOPEN_PASSTHROUGH and backing_id to fuse_open_out
argument that can be used when replying to OPEN request, to setup
passthrough of io operations on the fuse inode to a backing file.

Introduce a refcounted fuse_backing object that will be used to
associate an open backing file with a fuse inode.

Signed-off-by: Amir Goldstein 
Signed-off-by: Miklos Szeredi