data_type large_stringclasses 3
values | source large_stringclasses 29
values | code large_stringlengths 98 49.4M | filepath large_stringlengths 5 161 ⌀ | message large_stringclasses 234
values | commit large_stringclasses 234
values | subject large_stringclasses 418
values | critique large_stringlengths 101 1.26M ⌀ | metadata dict |
|---|---|---|---|---|---|---|---|---|
lkml_critique | linux-fsdevel | Hi,
syzbot reported an issue with corrupted HFS+ images where the b-tree
allocation bitmap indicates that the header node (Node 0) is free. Node 0
must always be allocated as it contains the b-tree header record and the
allocation bitmap itself. Violating this invariant leads to allocator
corruption, which cascades in... | null | null | null | [PATCH v4 0/2] hfsplus: validate btree bitmap during mount and handle corruption gracefully | On Thu, 2026-02-26 at 14:42 +0530, Shardul Bankar wrote:
Frankly speaking, it could be enough to share only cnid. But if you would like
to be really nice and to share the tree's name, then I prefer to see an array of
constant strings where you can use cnid as an index. And macro or static inline
method that can c... | {
"author": "Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>",
"date": "Thu, 26 Feb 2026 23:29:26 +0000",
"is_openbsd": false,
"thread_id": "66941e77b76d1930a759a843783f1c68bb3089a8.camel@ibm.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Hi,
syzbot reported an issue with corrupted HFS+ images where the b-tree
allocation bitmap indicates that the header node (Node 0) is free. Node 0
must always be allocated as it contains the b-tree header record and the
allocation bitmap itself. Violating this invariant leads to allocator
corruption, which cascades in... | null | null | null | [PATCH v4 0/2] hfsplus: validate btree bitmap during mount and handle corruption gracefully | On Thu, 2026-02-26 at 14:42 +0530, Shardul Bankar wrote:
I think we don't need in off, len, page_idx arguments here. I suggest slightly
different interface:
u8 hfs_bmap_get_map_byte(struct hfs_bnode *node, u32 bit_index);
int hfs_bmap_set_map_byte(struct hfs_bnode *node, u32 bit_index, u8 byte);
In this case... | {
"author": "Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>",
"date": "Thu, 26 Feb 2026 23:50:46 +0000",
"is_openbsd": false,
"thread_id": "66941e77b76d1930a759a843783f1c68bb3089a8.camel@ibm.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Refactor the logic in io_register_pbuf_ring() into generic helpers:
- io_validate_buf_reg(): Validate user input and buffer registration
parameters
- io_alloc_new_buffer_list(): Allocate and initialize a new buffer
list for the given buffer group ID
- io_setup_pbuf_ring(): Sets up the physical buffer ring region an... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:20 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Use the more generic name io_unregister_buf_ring() as this function will
be used for unregistering both provided buffer rings and kernel-managed
buffer rings.
This is a preparatory change for upcoming kernel-managed buffer ring
support.
Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
---
io_uring/kbuf.c | 2... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:21 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Add support for kernel-managed buffer rings (kmbuf rings), which allow
the kernel to allocate and manage the backing buffers for a buffer
ring, rather than requiring the application to provide and manage them.
This introduces two new registration opcodes:
- IORING_REGISTER_KMBUF_RING: Register a kernel-managed buffer ... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:22 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Add support for mmapping kernel-managed buffer rings (kmbuf) to
userspace, allowing applications to access the kernel-allocated buffers.
Similar to application-provided buffer rings (pbuf), kmbuf rings use the
buffer group ID encoded in the mmap offset to identify which buffer ring
to map. The implementation follows t... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:23 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Allow kernel-managed buffers to be selected. This requires modifying the
io_br_sel struct to separate the fields for address and val, since a
kernel address cannot be distinguished from a negative val when error
checking.
Auto-commit any selected kernel-managed buffer.
Signed-off-by: Joanne Koong <joannelkoong@gmail.... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:24 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Add kernel APIs to pin and unpin buffer rings, preventing userspace from
unregistering a buffer ring while it is pinned by the kernel.
This provides a mechanism for kernel subsystems to safely access buffer
ring contents while ensuring the buffer ring remains valid. A pinned
buffer ring cannot be unregistered until ex... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:25 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Add an interface for buffers to be recycled back into a kernel-managed
buffer ring.
This is a preparatory patch for fuse over io-uring.
Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
---
include/linux/io_uring/cmd.h | 11 +++++++++
io_uring/kbuf.c | 44 ++++++++++++++++++++++++++++++++++++
2 files... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:26 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Add two new helpers, io_uring_fixed_index_get() and
io_uring_fixed_index_put(). io_uring_fixed_index_get() constructs an
iter for a fixed buffer at a given index and acquires a refcount on
the underlying node. io_uring_fixed_index_put() decrements this
refcount. The caller is responsible for ensuring
io_uring_fixed_ind... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:27 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | io_uring_is_kmbuf_ring() returns true if there is a kernel-managed
buffer ring at the specified buffer group.
This is a preparatory patch for upcoming fuse kernel-managed buffer
support, which needs to ensure the buffer ring registered by the server
is a kernel-managed buffer ring.
Signed-off-by: Joanne Koong <joanne... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:28 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Export io_ring_buffer_select() so that it may be used by callers who
pass in a pinned bufring without needing to grab the io_uring mutex.
This is a preparatory patch that will be needed by fuse io-uring, which
will need to select a buffer from a kernel-managed bufring while the
uring mutex may already be held by in-pr... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:29 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Return the id of the selected buffer in io_buffer_select(). This is
needed for kernel-managed buffer rings to later recycle the selected
buffer.
Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
---
include/linux/io_uring/cmd.h | 2 +-
include/linux/io_uring_types.h | 2 ++
io_uring/kbuf.c | 7 +++... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:30 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | When uring_cmd operations select a buffer, the completion queue entry
should indicate which buffer was selected.
Set IORING_CQE_F_BUFFER on the completed entry and encode the buffer
index if a buffer was selected.
This will be needed for fuse, which needs to relay to userspace which
selected buffer contains the data.... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:31 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Simplify the logic for getting the next fuse request.
Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
Reviewed-by: Bernd Schubert <bschubert@ddn.com>
---
fs/fuse/dev_uring.c | 78 ++++++++++++++++-----------------------------
1 file changed, 28 insertions(+), 50 deletions(-)
diff --git a/fs/fuse/dev_uring.c b/f... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:32 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Move header copying to ring logic into a new copy_header_to_ring()
function. This consolidates error handling.
Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
Reviewed-by: Bernd Schubert <bschubert@ddn.com>
---
fs/fuse/dev_uring.c | 39 +++++++++++++++++++++------------------
1 file changed, 21 insertions(+), 18... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:33 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Move header copying from ring logic into a new copy_header_from_ring()
function. This consolidates error handling.
Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
---
fs/fuse/dev_uring.c | 24 ++++++++++++++++++------
1 file changed, 18 insertions(+), 6 deletions(-)
diff --git a/fs/fuse/dev_uring.c b/fs/fuse/de... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:34 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Use enum types to identify which part of the header needs to be copied.
This improves the interface and will simplify both kernel-space and
user-space header addresses when kernel-managed buffer rings are added.
Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
Reviewed-by: Bernd Schubert <bschubert@ddn.com>
---
f... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:35 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Add a new helper function setup_fuse_copy_state() to contain the logic
for setting up the copy state for payload copying.
Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
Reviewed-by: Bernd Schubert <bschubert@ddn.com>
---
fs/fuse/dev_uring.c | 38 ++++++++++++++++++++++++--------------
1 file changed, 24 inserti... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:36 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | This is a preparatory patch needed to support kernel-managed ring
buffers in fuse-over-io-uring. For kernel-managed ring buffers, we get
the vmapped address of the buffer which we can directly use.
Currently, buffer copying in fuse only supports extracting underlying
pages from an iov iter and kmapping them. This comm... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:37 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Currently, io_buffer_register_bvec() takes in a request. In preparation
for supporting kernel-populated buffers in fuse io-uring (which will
need to register bvecs directly, not through a struct request), rename
this to io_buffer_register_request().
A subsequent patch will commandeer the "io_buffer_register_bvec()"
fu... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:39 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Add io-uring kernel-managed buffer ring capability for fuse daemons
communicating through the io-uring interface.
This has two benefits:
a) eliminates the overhead of pinning/unpinning user pages and
translating virtual addresses for every server-kernel interaction
b) reduces the amount of memory needed for the buffe... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:38 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Split the main initialization logic in io_buffer_register_request() into
a helper function.
This is a preparatory patch for supporting kernel-populated buffers in
fuse io-uring, which will be reusing this logic.
Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
Reviewed-by: Caleb Sander Mateos <csander@purestorage... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:40 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | This is a preparatory patch for supporting kernel-populated buffers in
fuse io-uring, which does not need a release callback.
Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
Reviewed-by: Caleb Sander Mateos <csander@purestorage.com>
---
io_uring/rsrc.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
dif... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:41 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Add io_buffer_register_bvec() for registering a bvec array.
This is a preparatory patch for fuse-over-io-uring zero-copy.
Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
Reviewed-by: Caleb Sander Mateos <csander@purestorage.com>
---
include/linux/io_uring/cmd.h | 12 ++++++++++++
io_uring/rsrc.c | ... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:42 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Implement zero-copy data transfer for fuse over io-uring, eliminating
memory copies between kernel and userspace for read/write operations.
This is only allowed on privileged servers and requires the server to
preregister the following:
a) a sparse buffer corresponding to the queue depth
b) a fixed buffer at index que... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:43 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Add documentation for fuse over io-uring usage of kernel-managed
bufrings and zero-copy.
Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
---
.../filesystems/fuse/fuse-io-uring.rst | 59 ++++++++++++++++++-
1 file changed, 58 insertions(+), 1 deletion(-)
diff --git a/Documentation/filesystems/fuse/fuse-io... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 16 Jan 2026 15:30:44 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Hi Joanne,
kernel test robot noticed the following build warnings:
[auto build test WARNING on axboe/for-next]
[also build test WARNING on mszeredi-fuse/for-next linus/master v6.19-rc5 next-20260116]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Sat, 17 Jan 2026 13:28:38 +0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On Fri, Jan 16, 2026 at 3:31 PM Joanne Koong <joannelkoong@gmail.com> wrote:
How is this possible?
Other than that,
Reviewed-by: Caleb Sander Mateos <csander@purestorage.com> | {
"author": "Caleb Sander Mateos <csander@purestorage.com>",
"date": "Thu, 22 Jan 2026 13:02:25 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On Thu, Jan 22, 2026 at 1:02 PM Caleb Sander Mateos
<csander@purestorage.com> wrote:
You're right, this null check is unnecessary. I'll drop it.
Thank you for reviewing the patches, Caleb. | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Tue, 27 Jan 2026 12:05:46 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On Fri, Jan 16, 2026 at 3:31 PM Joanne Koong <joannelkoong@gmail.com> wrote:
Could anyone on the fuse side review the fuse changes in patches 19 and 24?
Thanks,
Joanne | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Tue, 27 Jan 2026 12:12:11 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On 1/27/26 21:12, Joanne Koong wrote:
I will really do this week, getting persistently other "urgent" work :/
Sorry for late reviews,
Bernd | {
"author": "Bernd Schubert <bernd@bsbernd.com>",
"date": "Tue, 27 Jan 2026 23:44:18 +0100",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On Tue, Jan 27, 2026 at 2:44 PM Bernd Schubert <bernd@bsbernd.com> wrote:
No worries, thank you Bernd! | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Tue, 27 Jan 2026 15:27:13 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On 1/17/26 00:30, Joanne Koong wrote:
I'm confused here, how cs->len will get initialized. So far that was
done from fuse_copy_fill?
Thanks,
Bernd | {
"author": "Bernd Schubert <bschubert@ddn.com>",
"date": "Wed, 28 Jan 2026 00:39:41 +0100",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On Tue, Jan 27, 2026 at 3:40 PM Bernd Schubert <bschubert@ddn.com> wrote:
With kaddrs, cs->len is initialized when the copy state is set up (in
setup_fuse_copy_state()) before we do any copying to/from the ring.
The changes for that are in the later patch that adds the ringbuffer
logic ("fuse: add io-uring kernel-mana... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Tue, 27 Jan 2026 16:23:50 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On 1/28/26 01:23, Joanne Koong wrote:
Maybe we could add a sanity check into fuse_copy_do() or even into
fuse_copy_fill in the cs->is_kaddr condition that cs->len is > 0?
Otherwise looks good.
Reviewed-by: Bernd Schubert <bernd@bsbernd.com> | {
"author": "Bernd Schubert <bernd@bsbernd.com>",
"date": "Wed, 28 Jan 2026 22:14:43 +0100",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On 1/17/26 00:30, Joanne Koong wrote:
I won't manage to review everything of this patch today, but just
noticed this. There is already an unused flags, why don't you use that?
I had edded it exactly for such things.
Thanks,
Bernd | {
"author": "Bernd Schubert <bernd@bsbernd.com>",
"date": "Wed, 28 Jan 2026 22:44:01 +0100",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On Wed, Jan 28, 2026 at 1:44 PM Bernd Schubert <bernd@bsbernd.com> wrote:
Oh nice, I missed seeing that. I'll just use that flags variable then.
Thanks,
Joanne | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Wed, 28 Jan 2026 17:15:18 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On Wed, Jan 28, 2026 at 1:14 PM Bernd Schubert <bernd@bsbernd.com> wrote:
I will add a WARN_ON for this in the next version. Thanks for reviewing this.
Thanks,
Joanne | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Wed, 28 Jan 2026 17:16:43 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On 1/17/26 00:30, Joanne Koong wrote:
I'm just looking at the fuse part and I'm actually not sure what the
"buf_group" parameter is. I guess it is a the buffer group set up by
userspace? Does io-uring have some documentation like fuse has under
Documentation/filesystems/fuse/?
Thanks,
Bernd | {
"author": "Bernd Schubert <bernd@bsbernd.com>",
"date": "Tue, 3 Feb 2026 19:52:42 +0100",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On 1/17/26 00:30, Joanne Koong wrote:
Would you mind to add the actual liburing call for this? I think it
would be helpful for anyone who wants to implement it. | {
"author": "Bernd Schubert <bernd@bsbernd.com>",
"date": "Tue, 3 Feb 2026 19:56:04 +0100",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On Tue, Feb 3, 2026 at 10:52 AM Bernd Schubert <bernd@bsbernd.com> wrote:
Hi Bernd,
Yes, buf_group is the id of the buffer group set up by userspace. I
don't see anything documentation related for it under Documentation/,
I think the closest equivalent is the man page for the buffer
registration API in [1] where it s... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Thu, 5 Feb 2026 11:37:21 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On Tue, Feb 3, 2026 at 10:44 AM Bernd Schubert <bernd@bsbernd.com> wrote:
A buffer shouldn't be recycled back into the bufring if the bufring
has already been unregistered. I'll add a WARN_ON to make this more
clear. For the fuse case, this is ensured by the kmbuf ring pin which
prevents unregistration.
Thanks,
Joann... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Thu, 5 Feb 2026 11:47:46 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On Tue, Feb 3, 2026 at 10:56 AM Bernd Schubert <bernd@bsbernd.com> wrote:
Good idea, I think what might be even more helpful is to refer them to
the libfuse lib/lowlevel_fuse.c file for reference on how to set this
up. Then they could just copy/paste the code directly from libfuse if
they're trying to do something sim... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Thu, 5 Feb 2026 12:30:50 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On 2/5/26 20:47, Joanne Koong wrote:
It is a bit confusing, because all the other conditions first check if
"bl" isn't a null pointer, this one here is the only exception, I think.
Thanks,
Bernd | {
"author": "Bernd Schubert <bschubert@ddn.com>",
"date": "Thu, 5 Feb 2026 21:42:46 +0100",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On Fri, Jan 16, 2026 at 03:30:19PM -0800, Joanne Koong wrote:
Can you split that series out as it also has other applications
and smaller series might be easier to review? | {
"author": "Christoph Hellwig <hch@infradead.org>",
"date": "Thu, 5 Feb 2026 23:42:21 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On Fri, Jan 16, 2026 at 03:30:22PM -0800, Joanne Koong wrote:
Do you have a man page or other documentation for the uapi somewhere?
Probably more a comment for patch 1, but wouldn't it make sense
to combine copy from user and vaidation into a single helper?
Return the buffer list from io_alloc_new_buffer_list or a... | {
"author": "Christoph Hellwig <hch@infradead.org>",
"date": "Thu, 5 Feb 2026 23:53:54 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | Joanne Koong <joannelkoong@gmail.com>:
Is it true that these kbufs solve same problem splice originally meant for?
I. e. is it true that kbuf is modern uring-based replacement for splice?
Linus said in 2006 in https://lore.kernel.org/all/Pine.LNX.4.64.0603300853190.27203@g5.osdl.org/ :
So, kbuf is modern version of... | {
"author": "Askar Safin <safinaskar@gmail.com>",
"date": "Fri, 6 Feb 2026 16:39:50 +0300",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On Thu, Feb 5, 2026 at 11:42 PM Christoph Hellwig <hch@infradead.org> wrote:
I'll split this out and send it by itself.
Thanks,
Joanne | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 6 Feb 2026 16:24:22 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On Thu, Feb 5, 2026 at 11:53 PM Christoph Hellwig <hch@infradead.org> wrote:
No, but I will tidy up the liburing side changes I have for this and
add the documentation to liburing/man.
I'll rename this function to io_copy_and_validate_buf_reg() and move
the copying into that.
Sounds good, I'll make this change.
T... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 6 Feb 2026 16:59:57 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On Fri, Feb 6, 2026 at 5:40 AM Askar Safin <safinaskar@gmail.com> wrote:
I don't think this is related to kmbufs. Zero-copying is done through
registered buffers (eg userspace registers sparse buffers for the ring
ahead of time and then on the kernel side, those sparse buffers can be
filled out by the kernel to point ... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 6 Feb 2026 17:22:34 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On Sat, Feb 7, 2026 at 4:22 AM Joanne Koong <joannelkoong@gmail.com> wrote:
Thank you for your answer.
Please, don't CC me when sending future versions of this patchset.
--
Askar Safin | {
"author": "Askar Safin <safinaskar@gmail.com>",
"date": "Sat, 7 Feb 2026 19:13:10 +0300",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On Sat, Feb 7, 2026 at 8:13 AM Askar Safin <safinaskar@gmail.com> wrote:
For context, your email address was cc-ed because you had left a
comment [1] on v1 of this patchset series. I'll make sure to remove
you from the cc list going forward.
Thanks,
Joanne
[1] https://lore.kernel.org/linux-fsdevel/20251213075246.164... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Mon, 9 Feb 2026 09:31:47 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On 1/28/26 22:44, Bernd Schubert wrote:
Hello Joanne,
couldn't it call fuse_uring_headers_cleanup() before the
fuse_uring_get_next_fuse_req()? I find it a bit confusing that it firsts
gets the next request and then cleans up the buffer from the previous
request.
As I understand it, the the patch basically adds the ... | {
"author": "Bernd Schubert <bernd@bsbernd.com>",
"date": "Wed, 25 Feb 2026 18:55:44 +0100",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On Wed, Feb 25, 2026 at 9:55 AM Bernd Schubert <bernd@bsbernd.com> wrote:
Hi Bernd,
Thanks for taking a look.
The fuse_uring_headers_cleanup() call has to happen after the
fuse_uring_get_next_fuse_req() call because
fuse_uring_get_next_fuse_req() copies payload to the header, so we
can't yet relinquish the refcount ... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Wed, 25 Feb 2026 15:42:31 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On 2/26/26 00:42, Joanne Koong wrote:
I only found time right now and already super late (or early) here.
I guess that is fuse_uring_copy_to_ring -> copy_header_to_ring, but why
can it then call fuse_uring_headers_cleanup() ->
io_uring_fixed_index_put(). I.e. doesn't it put buffer it just copied
to? Why not the seque... | {
"author": "Bernd Schubert <bernd@bsbernd.com>",
"date": "Thu, 26 Feb 2026 19:21:07 +0100",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This series adds buffer ring and zero-copy capabilities to fuse over io-uring.
This requires adding a new kernel-managed buf (kmbuf) ring type to io-uring
where the buffers are provided and managed by the kernel instead of by
userspace.
On the io-uring side, the kmbuf interface is basically identical to pbufs.
They di... | null | null | null | [PATCH v4 00/25] fuse/io-uring: add kernel-managed buffer rings and zero-copy | On Thu, Feb 26, 2026 at 10:21 AM Bernd Schubert <bernd@bsbernd.com> wrote:
The headers buffer is the same buffer for the request that's being
committed and the next request that is fetched (just like how the ent
is the same ent for the request that's committed and the next fetched
request). Because of this we can just... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Thu, 26 Feb 2026 12:58:20 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZQC=tE8z+D1rSnNijkMhXDPEZaB_9WL9NPZyKmG2=NSQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | In the discussion about open+getattr here [1] Bernd and Miklos talked
about the need for a compound command in fuse that could send multiple
commands to a fuse server.
This can be used to reduce the number of switches from user to kernel
space but also to define atomic operations that the fuse server can
process as on... | null | null | null | [PATCH v6 0/3] fuse: compound commands | From: Horst Birthelmer <hbirthelmer@ddn.com>
For a FUSE_COMPOUND we add a small header that informs the
fuse server how much buffer memory the kernel has for the result.
This will make the interpretation in libfuse easier,
since we can preallocate the whole result and work on the return
buffer.
Then we append the requ... | {
"author": "Horst Birthelmer <horst@birthelmer.com>",
"date": "Thu, 26 Feb 2026 17:43:53 +0100",
"is_openbsd": false,
"thread_id": "CAJfpegvPxgPs_AYhqUjgak_P9BLTKAjn9FLNO6pAtFjx-YyN1Q@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | In the discussion about open+getattr here [1] Bernd and Miklos talked
about the need for a compound command in fuse that could send multiple
commands to a fuse server.
This can be used to reduce the number of switches from user to kernel
space but also to define atomic operations that the fuse server can
process as on... | null | null | null | [PATCH v6 0/3] fuse: compound commands | From: Horst Birthelmer <hbirthelmer@ddn.com>
The discussion about compound commands in fuse was
started over an argument to add a new operation that
will open a file and return its attributes in the same operation.
Here is a demonstration of that use case with compound commands.
Signed-off-by: Horst Birthelmer <hbir... | {
"author": "Horst Birthelmer <horst@birthelmer.com>",
"date": "Thu, 26 Feb 2026 17:43:55 +0100",
"is_openbsd": false,
"thread_id": "CAJfpegvPxgPs_AYhqUjgak_P9BLTKAjn9FLNO6pAtFjx-YyN1Q@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | In the discussion about open+getattr here [1] Bernd and Miklos talked
about the need for a compound command in fuse that could send multiple
commands to a fuse server.
This can be used to reduce the number of switches from user to kernel
space but also to define atomic operations that the fuse server can
process as on... | null | null | null | [PATCH v6 0/3] fuse: compound commands | From: Horst Birthelmer <hbirthelmer@ddn.com>
create fuse_getattr_args_fill() and fuse_open_args_fill() to fill in
the parameters for the open and getattr calls.
This is in preparation for implementing open+getattr and does not
represent any functional change.
Suggested-by: Joanne Koong <joannelkoong@gmail.com>
Signe... | {
"author": "Horst Birthelmer <horst@birthelmer.com>",
"date": "Thu, 26 Feb 2026 17:43:54 +0100",
"is_openbsd": false,
"thread_id": "CAJfpegvPxgPs_AYhqUjgak_P9BLTKAjn9FLNO6pAtFjx-YyN1Q@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | In the discussion about open+getattr here [1] Bernd and Miklos talked
about the need for a compound command in fuse that could send multiple
commands to a fuse server.
This can be used to reduce the number of switches from user to kernel
space but also to define atomic operations that the fuse server can
process as on... | null | null | null | [PATCH v6 0/3] fuse: compound commands | On Thu, Feb 26, 2026 at 8:43 AM Horst Birthelmer <horst@birthelmer.com> wrote:
Do you think it makes sense to move this chunk of logic into
fuse_open_args_fill() since this logic has to be done in
fuse_send_open() as well?
It looks like this logic is shared between here and the non-compound
open path, maybe a bit be... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Thu, 26 Feb 2026 11:12:00 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegvPxgPs_AYhqUjgak_P9BLTKAjn9FLNO6pAtFjx-YyN1Q@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | In the discussion about open+getattr here [1] Bernd and Miklos talked
about the need for a compound command in fuse that could send multiple
commands to a fuse server.
This can be used to reduce the number of switches from user to kernel
space but also to define atomic operations that the fuse server can
process as on... | null | null | null | [PATCH v6 0/3] fuse: compound commands | On Thu, Feb 26, 2026 at 8:43 AM Horst Birthelmer <horst@birthelmer.com> wrote:
Can you explain why this is needed? The caller has all the information
up front, so why can't it just set this information before calling
fuse_compoudn_send() instead of needing this to be done in the
->op_converters callback?
imo it's li... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Thu, 26 Feb 2026 15:05:00 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegvPxgPs_AYhqUjgak_P9BLTKAjn9FLNO6pAtFjx-YyN1Q@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | In the discussion about open+getattr here [1] Bernd and Miklos talked
about the need for a compound command in fuse that could send multiple
commands to a fuse server.
This can be used to reduce the number of switches from user to kernel
space but also to define atomic operations that the fuse server can
process as on... | null | null | null | [PATCH v6 0/3] fuse: compound commands | On Thu, Feb 26, 2026 at 11:12:00AM -0800, Joanne Koong wrote:
Yes, I think that makes sense and would be beneficial to other requests in
other compounds that will be constructed with that function.
Will do that.
You are right, we had the conversation and other people joined, so I
changed this code but to something... | {
"author": "Horst Birthelmer <horst@birthelmer.de>",
"date": "Fri, 27 Feb 2026 08:48:04 +0100",
"is_openbsd": false,
"thread_id": "CAJfpegvPxgPs_AYhqUjgak_P9BLTKAjn9FLNO6pAtFjx-YyN1Q@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | In the discussion about open+getattr here [1] Bernd and Miklos talked
about the need for a compound command in fuse that could send multiple
commands to a fuse server.
This can be used to reduce the number of switches from user to kernel
space but also to define atomic operations that the fuse server can
process as on... | null | null | null | [PATCH v6 0/3] fuse: compound commands | On Thu, 26 Feb 2026 at 17:43, Horst Birthelmer <horst@birthelmer.com> wrote:
WARN_ON()
This could be done *much* simpler with lists. Just add a 'struct
list_head list' member to struct fuse_args and pass a 'struct
list_head *compound' to fuse_compound_add(). No need for
fuse_compound_alloc/free().
Alternatively ... | {
"author": "Miklos Szeredi <miklos@szeredi.hu>",
"date": "Fri, 27 Feb 2026 10:45:36 +0100",
"is_openbsd": false,
"thread_id": "CAJfpegvPxgPs_AYhqUjgak_P9BLTKAjn9FLNO6pAtFjx-YyN1Q@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | In the discussion about open+getattr here [1] Bernd and Miklos talked
about the need for a compound command in fuse that could send multiple
commands to a fuse server.
This can be used to reduce the number of switches from user to kernel
space but also to define atomic operations that the fuse server can
process as on... | null | null | null | [PATCH v6 0/3] fuse: compound commands | On Fri, Feb 27, 2026 at 10:45:36AM +0100, Miklos Szeredi wrote:
Will have another go at this.
This was my way of dealing with the interdependencies.
The automatic sequencialization will call this for every request.
So we can copy and manipulate the args for the next request.
No need for any other flags then. We can ... | {
"author": "Horst Birthelmer <horst@birthelmer.de>",
"date": "Fri, 27 Feb 2026 11:48:23 +0100",
"is_openbsd": false,
"thread_id": "CAJfpegvPxgPs_AYhqUjgak_P9BLTKAjn9FLNO6pAtFjx-YyN1Q@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | In the discussion about open+getattr here [1] Bernd and Miklos talked
about the need for a compound command in fuse that could send multiple
commands to a fuse server.
This can be used to reduce the number of switches from user to kernel
space but also to define atomic operations that the fuse server can
process as on... | null | null | null | [PATCH v6 0/3] fuse: compound commands | On Fri, 27 Feb 2026 at 11:48, Horst Birthelmer <horst@birthelmer.de> wrote:
Dependencies need to be handled by the kernel and libfuse as well.
Makes no sense to have two separate mechanisms for handling
dependencies, so the kernel should use the same flags.
- LOOKUP + GETATTR[L]
- MKOBJ + (SETXATTR[L] (only for po... | {
"author": "Miklos Szeredi <miklos@szeredi.hu>",
"date": "Fri, 27 Feb 2026 12:29:00 +0100",
"is_openbsd": false,
"thread_id": "CAJfpegvPxgPs_AYhqUjgak_P9BLTKAjn9FLNO6pAtFjx-YyN1Q@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | In the discussion about open+getattr here [1] Bernd and Miklos talked
about the need for a compound command in fuse that could send multiple
commands to a fuse server.
This can be used to reduce the number of switches from user to kernel
space but also to define atomic operations that the fuse server can
process as on... | null | null | null | [PATCH v6 0/3] fuse: compound commands | On Fri, Feb 27, 2026 at 12:29:00PM +0100, Miklos Szeredi wrote:
OK, got it.
I really am greateful for this list. Helps me a lot, since I was looking at this from the
perspective of the fuse server, which truns out to be different.
I naively thought that fuse_atomic_open() was actually there to do an atomic open ..... | {
"author": "Horst Birthelmer <horst@birthelmer.de>",
"date": "Fri, 27 Feb 2026 12:37:52 +0100",
"is_openbsd": false,
"thread_id": "CAJfpegvPxgPs_AYhqUjgak_P9BLTKAjn9FLNO6pAtFjx-YyN1Q@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | In the discussion about open+getattr here [1] Bernd and Miklos talked
about the need for a compound command in fuse that could send multiple
commands to a fuse server.
This can be used to reduce the number of switches from user to kernel
space but also to define atomic operations that the fuse server can
process as on... | null | null | null | [PATCH v6 0/3] fuse: compound commands | On Fri, 27 Feb 2026 at 12:37, Horst Birthelmer <horst@birthelmer.de> wrote:
Yes, it helps with atomicity relative to operations on other clients
in a distributed fs.
For a local fs it does not make a difference in terms of correctness,
but with compounds it could improve performance compared to separate
lookup + mkn... | {
"author": "Miklos Szeredi <miklos@szeredi.hu>",
"date": "Fri, 27 Feb 2026 12:58:12 +0100",
"is_openbsd": false,
"thread_id": "CAJfpegvPxgPs_AYhqUjgak_P9BLTKAjn9FLNO6pAtFjx-YyN1Q@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | On 26 Feb 2026, at 15:34, Bas van Dijk wrote:
> #regzbot introduced: 7460b470a131f985a70302a322617121efdd7caa
>
> Hey folks,
>
> We discovered madvise(MADV_REMOVE) on a 4KiB range within a
> huge-page-backed MAP_SHARED memfd region corrupts nearby pages.
>
> Using the reproducible test in
> https://github.com/dfinity/... | null | null | null | Re: [REGRESSION] madvise(MADV_REMOVE) corrupts pages in THP-backed
MAP_SHARED memfd (bisected to 7460b470a131) | On 26 Feb 2026, at 15:49, Zi Yan wrote:
Can you also share your kernel config file? I just ran the reproducer and
could not trigger the corruption.
Thanks.
Best Regards,
Yan, Zi | {
"author": "Zi Yan <ziy@nvidia.com>",
"date": "Thu, 26 Feb 2026 16:06:16 -0500",
"is_openbsd": false,
"thread_id": "CAKNNEtwZzt3xWh_b1pn4X4FG+cq6FLOP5rR4+G=WUsjHsJRjaA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | On 26 Feb 2026, at 15:34, Bas van Dijk wrote:
> #regzbot introduced: 7460b470a131f985a70302a322617121efdd7caa
>
> Hey folks,
>
> We discovered madvise(MADV_REMOVE) on a 4KiB range within a
> huge-page-backed MAP_SHARED memfd region corrupts nearby pages.
>
> Using the reproducible test in
> https://github.com/dfinity/... | null | null | null | Re: [REGRESSION] madvise(MADV_REMOVE) corrupts pages in THP-backed
MAP_SHARED memfd (bisected to 7460b470a131) | On Thu, Feb 26, 2026 at 10:06 PM Zi Yan <ziy@nvidia.com> wrote:
Sure, I just ran `nix build
.#linux_6_14_first_bad_7460b470a131.configfile -o kernel.config` which
produced:
https://github.com/dfinity/thp-madv-remove-test/blob/master/kernel.config | {
"author": "Bas van Dijk <bas@dfinity.org>",
"date": "Thu, 26 Feb 2026 22:16:25 +0100",
"is_openbsd": false,
"thread_id": "CAKNNEtwZzt3xWh_b1pn4X4FG+cq6FLOP5rR4+G=WUsjHsJRjaA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Ye Bin <yebin10@huawei.com>
In order to better analyze the issue of file system uninstallation caused
by kernel module opening files, it is necessary to perform dentry recycling
on a single file system. But now, apart from global dentry recycling, it is
not supported to do dentry recycling on a single file syste... | null | null | null | [PATCH v3 0/3] add support for drop_caches for individual filesystem | From: Ye Bin <yebin10@huawei.com>
Add instructions for 'drop_fs_caches sysctl' sysctl in 'vm.rst'.
Signed-off-by: Ye Bin <yebin10@huawei.com>
---
Documentation/admin-guide/sysctl/vm.rst | 44 +++++++++++++++++++++++++
1 file changed, 44 insertions(+)
diff --git a/Documentation/admin-guide/sysctl/vm.rst b/Documentat... | {
"author": "Ye Bin <yebin@huaweicloud.com>",
"date": "Fri, 27 Feb 2026 10:55:48 +0800",
"is_openbsd": false,
"thread_id": "20260227025548.2252380-3-yebin@huaweicloud.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Ye Bin <yebin10@huawei.com>
In order to better analyze the issue of file system uninstallation caused
by kernel module opening files, it is necessary to perform dentry recycling
on a single file system. But now, apart from global dentry recycling, it is
not supported to do dentry recycling on a single file syste... | null | null | null | [PATCH v3 0/3] add support for drop_caches for individual filesystem | From: Ye Bin <yebin10@huawei.com>
In order to better analyze the issue of file system uninstallation caused
by kernel module opening files, it is necessary to perform dentry recycling
on a single file system. But now, apart from global dentry recycling, it is
not supported to do dentry recycling on a single file syste... | {
"author": "Ye Bin <yebin@huaweicloud.com>",
"date": "Fri, 27 Feb 2026 10:55:47 +0800",
"is_openbsd": false,
"thread_id": "20260227025548.2252380-3-yebin@huaweicloud.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Ye Bin <yebin10@huawei.com>
In order to better analyze the issue of file system uninstallation caused
by kernel module opening files, it is necessary to perform dentry recycling
on a single file system. But now, apart from global dentry recycling, it is
not supported to do dentry recycling on a single file syste... | null | null | null | [PATCH v3 0/3] add support for drop_caches for individual filesystem | From: Ye Bin <yebin10@huawei.com>
This patch is prepare for support drop_caches for specify file system.
Signed-off-by: Ye Bin <yebin10@huawei.com>
---
include/linux/mm.h | 1 +
mm/internal.h | 3 +++
mm/shrinker.c | 4 ++--
mm/vmscan.c | 50 ++++++++++++++++++++++++++++++++++++++++++++++
4 files... | {
"author": "Ye Bin <yebin@huaweicloud.com>",
"date": "Fri, 27 Feb 2026 10:55:46 +0800",
"is_openbsd": false,
"thread_id": "20260227025548.2252380-3-yebin@huaweicloud.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Ye Bin <yebin10@huawei.com>
In order to better analyze the issue of file system uninstallation caused
by kernel module opening files, it is necessary to perform dentry recycling
on a single file system. But now, apart from global dentry recycling, it is
not supported to do dentry recycling on a single file syste... | null | null | null | [PATCH v3 0/3] add support for drop_caches for individual filesystem | Would shrinker-debugfs satisfy your needs (See Documentation/admin-guide/mm/shrinker_debugfs.rst)?
Thanks,
Muchun | {
"author": "Muchun Song <muchun.song@linux.dev>",
"date": "Fri, 27 Feb 2026 11:31:14 +0800",
"is_openbsd": false,
"thread_id": "20260227025548.2252380-3-yebin@huaweicloud.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Ye Bin <yebin10@huawei.com>
In order to better analyze the issue of file system uninstallation caused
by kernel module opening files, it is necessary to perform dentry recycling
on a single file system. But now, apart from global dentry recycling, it is
not supported to do dentry recycling on a single file syste... | null | null | null | [PATCH v3 0/3] add support for drop_caches for individual filesystem | On 2026/2/27 11:31, Muchun Song wrote:
Thank you for the reminder. The reclamation of dentries and nodes can
meet my needs. However, the reclamation of the page cache alone does not
satisfy my requirements. I have reviewed the code of
shrinker_debugfs_scan_write() and found that it does not support batch
deletion o... | {
"author": "\"yebin (H)\" <yebin10@huawei.com>",
"date": "Fri, 27 Feb 2026 14:39:22 +0800",
"is_openbsd": false,
"thread_id": "20260227025548.2252380-3-yebin@huaweicloud.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Ye Bin <yebin10@huawei.com>
In order to better analyze the issue of file system uninstallation caused
by kernel module opening files, it is necessary to perform dentry recycling
on a single file system. But now, apart from global dentry recycling, it is
not supported to do dentry recycling on a single file syste... | null | null | null | [PATCH v3 0/3] add support for drop_caches for individual filesystem | On 2/27/26 2:39 PM, yebin (H) wrote:
Using shrinker-debugfs allows users to specify the size of a single
reclaim cycle (nr_to_scan), which controls the strength of each reclaim
cycle to adapt to different workloads. Can the new drop_fs_caches
support a similar approach?
Thanks,
Qi | {
"author": "Qi Zheng <qi.zheng@linux.dev>",
"date": "Fri, 27 Feb 2026 14:50:17 +0800",
"is_openbsd": false,
"thread_id": "20260227025548.2252380-3-yebin@huaweicloud.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Ye Bin <yebin10@huawei.com>
In order to better analyze the issue of file system uninstallation caused
by kernel module opening files, it is necessary to perform dentry recycling
on a single file system. But now, apart from global dentry recycling, it is
not supported to do dentry recycling on a single file syste... | null | null | null | [PATCH v3 0/3] add support for drop_caches for individual filesystem | I don't really like that you're implementing another mechanism with duplicate
functionality. If you'd like, you could write a script to iterate through them
and execute it that way—I don't think that would be particularly inconvenient,
would it? If the iteration operation of memcg is indeed quite cumbersome, I
think ex... | {
"author": "Muchun Song <muchun.song@linux.dev>",
"date": "Fri, 27 Feb 2026 14:55:04 +0800",
"is_openbsd": false,
"thread_id": "20260227025548.2252380-3-yebin@huaweicloud.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Ye Bin <yebin10@huawei.com>
In order to better analyze the issue of file system uninstallation caused
by kernel module opening files, it is necessary to perform dentry recycling
on a single file system. But now, apart from global dentry recycling, it is
not supported to do dentry recycling on a single file syste... | null | null | null | [PATCH v3 0/3] add support for drop_caches for individual filesystem | On 2026/2/27 14:50, Qi Zheng wrote:
"drop_fs_caches" is similar to "drop_caches," but it only operates on
the specified file system. It does not support specifying the number of
pages to scan (nr_to_scan). | {
"author": "\"yebin (H)\" <yebin10@huawei.com>",
"date": "Fri, 27 Feb 2026 15:18:31 +0800",
"is_openbsd": false,
"thread_id": "20260227025548.2252380-3-yebin@huaweicloud.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Ye Bin <yebin10@huawei.com>
In order to better analyze the issue of file system uninstallation caused
by kernel module opening files, it is necessary to perform dentry recycling
on a single file system. But now, apart from global dentry recycling, it is
not supported to do dentry recycling on a single file syste... | null | null | null | [PATCH v3 0/3] add support for drop_caches for individual filesystem | On 2026/2/27 14:55, Muchun Song wrote:
The shrinker_debugfs can be extended to support node/memcg/fs
granularity reclamation, similar to the extended function of echo " 0 -
X" > count /echo " - 0 X" > count /echo " - - X" > count. This only
solves the problem of reclaiming dentries/inode based on a single file
syst... | {
"author": "\"yebin (H)\" <yebin10@huawei.com>",
"date": "Fri, 27 Feb 2026 15:32:18 +0800",
"is_openbsd": false,
"thread_id": "20260227025548.2252380-3-yebin@huaweicloud.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Ye Bin <yebin10@huawei.com>
In order to better analyze the issue of file system uninstallation caused
by kernel module opening files, it is necessary to perform dentry recycling
on a single file system. But now, apart from global dentry recycling, it is
not supported to do dentry recycling on a single file syste... | null | null | null | [PATCH v3 0/3] add support for drop_caches for individual filesystem | If the inode is evicted, the page cache is evicted as well. It cannot evict page
cache alone. Why you want to evict cache alone? | {
"author": "Muchun Song <muchun.song@linux.dev>",
"date": "Fri, 27 Feb 2026 15:45:02 +0800",
"is_openbsd": false,
"thread_id": "20260227025548.2252380-3-yebin@huaweicloud.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Ye Bin <yebin10@huawei.com>
In order to better analyze the issue of file system uninstallation caused
by kernel module opening files, it is necessary to perform dentry recycling
on a single file system. But now, apart from global dentry recycling, it is
not supported to do dentry recycling on a single file syste... | null | null | null | [PATCH v3 0/3] add support for drop_caches for individual filesystem | On 2026/2/27 15:45, Muchun Song wrote:
The condition for dentry/inode to be reclaimed is that there are no
references to them. Therefore, relying on inode reclamation for page
cache reclamation has limitations. Additionally, there is currently no
usage statistics for the page cache based on a single file system. By
com... | {
"author": "\"yebin (H)\" <yebin10@huawei.com>",
"date": "Fri, 27 Feb 2026 16:17:24 +0800",
"is_openbsd": false,
"thread_id": "20260227025548.2252380-3-yebin@huaweicloud.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Ye Bin <yebin10@huawei.com>
In order to better analyze the issue of file system uninstallation caused
by kernel module opening files, it is necessary to perform dentry recycling
on a single file system. But now, apart from global dentry recycling, it is
not supported to do dentry recycling on a single file syste... | null | null | null | [PATCH v3 0/3] add support for drop_caches for individual filesystem | What limit?
I'm curious why dropping inodes doesn't show a noticeable difference
in page cache usage before and after? | {
"author": "Muchun Song <muchun.song@linux.dev>",
"date": "Fri, 27 Feb 2026 16:27:13 +0800",
"is_openbsd": false,
"thread_id": "20260227025548.2252380-3-yebin@huaweicloud.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Ye Bin <yebin10@huawei.com>
In order to better analyze the issue of file system uninstallation caused
by kernel module opening files, it is necessary to perform dentry recycling
on a single file system. But now, apart from global dentry recycling, it is
not supported to do dentry recycling on a single file syste... | null | null | null | [PATCH v3 0/3] add support for drop_caches for individual filesystem | On 2026/2/27 16:27, Muchun Song wrote:
If the file is occupied, the page cache cannot be reclaimed through
inode reclamation. | {
"author": "\"yebin (H)\" <yebin10@huawei.com>",
"date": "Fri, 27 Feb 2026 17:02:59 +0800",
"is_openbsd": false,
"thread_id": "20260227025548.2252380-3-yebin@huaweicloud.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
Following on from
https://lore.kernel.org/linux-nfs/20251021-zypressen-bazillus-545a44af57fd@brauner/T/#m0ba197d75b7921d994cf284f3cef3a62abb11aaa
I'm attempting to implement enough support in the Linux VFS to
enable file services like NFSD and ksmbd (and user space
equivale... | null | null | null | [PATCH v8 00/17] Subject: Exposing case folding behavior | From: Chuck Lever <chuck.lever@oracle.com>
fileattr_fill_xflags() and fileattr_fill_flags() zero the entire
file_kattr struct before populating select fields. This behavior
prevents callers from setting flags in fa->fsx_xflags before
calling these helpers; the zeroing clears any pre-set values.
As Darrick Wong observ... | {
"author": "Chuck Lever <cel@kernel.org>",
"date": "Tue, 17 Feb 2026 16:47:25 -0500",
"is_openbsd": false,
"thread_id": "ua7rmlnvbfiadpxeynekbabwqebhcop3rhaxji7s3mgnwzhhtd@frz77j6wm2eg.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
Following on from
https://lore.kernel.org/linux-nfs/20251021-zypressen-bazillus-545a44af57fd@brauner/T/#m0ba197d75b7921d994cf284f3cef3a62abb11aaa
I'm attempting to implement enough support in the Linux VFS to
enable file services like NFSD and ksmbd (and user space
equivale... | null | null | null | [PATCH v8 00/17] Subject: Exposing case folding behavior | From: Chuck Lever <chuck.lever@oracle.com>
Enable upper layers such as NFSD to retrieve case sensitivity
information from file systems by adding FS_XFLAG_CASEFOLD and
FS_XFLAG_CASENONPRESERVING flags.
Filesystems report case-insensitive or case-nonpreserving behavior
by setting these flags directly in fa->fsx_xflags.... | {
"author": "Chuck Lever <cel@kernel.org>",
"date": "Tue, 17 Feb 2026 16:47:26 -0500",
"is_openbsd": false,
"thread_id": "ua7rmlnvbfiadpxeynekbabwqebhcop3rhaxji7s3mgnwzhhtd@frz77j6wm2eg.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
Following on from
https://lore.kernel.org/linux-nfs/20251021-zypressen-bazillus-545a44af57fd@brauner/T/#m0ba197d75b7921d994cf284f3cef3a62abb11aaa
I'm attempting to implement enough support in the Linux VFS to
enable file services like NFSD and ksmbd (and user space
equivale... | null | null | null | [PATCH v8 00/17] Subject: Exposing case folding behavior | From: Chuck Lever <chuck.lever@oracle.com>
Report FAT's case sensitivity behavior via the FS_XFLAG_CASEFOLD
and FS_XFLAG_CASENONPRESERVING flags. FAT filesystems are
case-insensitive by default.
MSDOS supports a 'nocase' mount option that enables case-sensitive
behavior; check this option when reporting case sensitiv... | {
"author": "Chuck Lever <cel@kernel.org>",
"date": "Tue, 17 Feb 2026 16:47:27 -0500",
"is_openbsd": false,
"thread_id": "ua7rmlnvbfiadpxeynekbabwqebhcop3rhaxji7s3mgnwzhhtd@frz77j6wm2eg.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
Following on from
https://lore.kernel.org/linux-nfs/20251021-zypressen-bazillus-545a44af57fd@brauner/T/#m0ba197d75b7921d994cf284f3cef3a62abb11aaa
I'm attempting to implement enough support in the Linux VFS to
enable file services like NFSD and ksmbd (and user space
equivale... | null | null | null | [PATCH v8 00/17] Subject: Exposing case folding behavior | From: Chuck Lever <chuck.lever@oracle.com>
Report exFAT's case sensitivity behavior via the FS_XFLAG_CASEFOLD
flag. exFAT is always case-insensitive (using an upcase table for
comparison) and always preserves case at rest.
Acked-by: Namjae Jeon <linkinjeon@kernel.org>
Signed-off-by: Chuck Lever <chuck.lever@oracle.co... | {
"author": "Chuck Lever <cel@kernel.org>",
"date": "Tue, 17 Feb 2026 16:47:28 -0500",
"is_openbsd": false,
"thread_id": "ua7rmlnvbfiadpxeynekbabwqebhcop3rhaxji7s3mgnwzhhtd@frz77j6wm2eg.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
Following on from
https://lore.kernel.org/linux-nfs/20251021-zypressen-bazillus-545a44af57fd@brauner/T/#m0ba197d75b7921d994cf284f3cef3a62abb11aaa
I'm attempting to implement enough support in the Linux VFS to
enable file services like NFSD and ksmbd (and user space
equivale... | null | null | null | [PATCH v8 00/17] Subject: Exposing case folding behavior | From: Chuck Lever <chuck.lever@oracle.com>
Report NTFS case sensitivity behavior via the FS_XFLAG_CASEFOLD
flag. NTFS always preserves case at rest.
Case sensitivity depends on mount options: with "nocase", NTFS
is case-insensitive; otherwise it is case-sensitive.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
... | {
"author": "Chuck Lever <cel@kernel.org>",
"date": "Tue, 17 Feb 2026 16:47:29 -0500",
"is_openbsd": false,
"thread_id": "ua7rmlnvbfiadpxeynekbabwqebhcop3rhaxji7s3mgnwzhhtd@frz77j6wm2eg.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
Following on from
https://lore.kernel.org/linux-nfs/20251021-zypressen-bazillus-545a44af57fd@brauner/T/#m0ba197d75b7921d994cf284f3cef3a62abb11aaa
I'm attempting to implement enough support in the Linux VFS to
enable file services like NFSD and ksmbd (and user space
equivale... | null | null | null | [PATCH v8 00/17] Subject: Exposing case folding behavior | From: Chuck Lever <chuck.lever@oracle.com>
Report HFS case sensitivity behavior via the FS_XFLAG_CASEFOLD
flag. HFS is always case-insensitive (using Mac OS Roman case
folding) and always preserves case at rest.
Reviewed-by: Viacheslav Dubeyko <slava@dubeyko.com>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
--... | {
"author": "Chuck Lever <cel@kernel.org>",
"date": "Tue, 17 Feb 2026 16:47:30 -0500",
"is_openbsd": false,
"thread_id": "ua7rmlnvbfiadpxeynekbabwqebhcop3rhaxji7s3mgnwzhhtd@frz77j6wm2eg.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
Following on from
https://lore.kernel.org/linux-nfs/20251021-zypressen-bazillus-545a44af57fd@brauner/T/#m0ba197d75b7921d994cf284f3cef3a62abb11aaa
I'm attempting to implement enough support in the Linux VFS to
enable file services like NFSD and ksmbd (and user space
equivale... | null | null | null | [PATCH v8 00/17] Subject: Exposing case folding behavior | From: Chuck Lever <chuck.lever@oracle.com>
Add case sensitivity reporting to the existing hfsplus_fileattr_get()
function via the FS_XFLAG_CASEFOLD flag. HFS+ always preserves case
at rest.
Case sensitivity depends on how the volume was formatted: HFSX
volumes may be either case-sensitive or case-insensitive, indicat... | {
"author": "Chuck Lever <cel@kernel.org>",
"date": "Tue, 17 Feb 2026 16:47:31 -0500",
"is_openbsd": false,
"thread_id": "ua7rmlnvbfiadpxeynekbabwqebhcop3rhaxji7s3mgnwzhhtd@frz77j6wm2eg.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
Following on from
https://lore.kernel.org/linux-nfs/20251021-zypressen-bazillus-545a44af57fd@brauner/T/#m0ba197d75b7921d994cf284f3cef3a62abb11aaa
I'm attempting to implement enough support in the Linux VFS to
enable file services like NFSD and ksmbd (and user space
equivale... | null | null | null | [PATCH v8 00/17] Subject: Exposing case folding behavior | From: Chuck Lever <chuck.lever@oracle.com>
Report ext4's case sensitivity behavior via the FS_XFLAG_CASEFOLD
flag. ext4 always preserves case at rest.
Case sensitivity is a per-directory setting in ext4. If the queried
inode is a casefolded directory, report case-insensitive; otherwise
report case-sensitive (standard... | {
"author": "Chuck Lever <cel@kernel.org>",
"date": "Tue, 17 Feb 2026 16:47:32 -0500",
"is_openbsd": false,
"thread_id": "ua7rmlnvbfiadpxeynekbabwqebhcop3rhaxji7s3mgnwzhhtd@frz77j6wm2eg.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
Following on from
https://lore.kernel.org/linux-nfs/20251021-zypressen-bazillus-545a44af57fd@brauner/T/#m0ba197d75b7921d994cf284f3cef3a62abb11aaa
I'm attempting to implement enough support in the Linux VFS to
enable file services like NFSD and ksmbd (and user space
equivale... | null | null | null | [PATCH v8 00/17] Subject: Exposing case folding behavior | From: Chuck Lever <chuck.lever@oracle.com>
Upper layers such as NFSD need to query whether a filesystem is
case-sensitive. Report case sensitivity via the FS_XFLAG_CASEFOLD
flag in xfs_fileattr_get(). XFS always preserves case. XFS is
case-sensitive by default, but supports ASCII case-insensitive
lookups when formatte... | {
"author": "Chuck Lever <cel@kernel.org>",
"date": "Tue, 17 Feb 2026 16:47:33 -0500",
"is_openbsd": false,
"thread_id": "ua7rmlnvbfiadpxeynekbabwqebhcop3rhaxji7s3mgnwzhhtd@frz77j6wm2eg.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
Following on from
https://lore.kernel.org/linux-nfs/20251021-zypressen-bazillus-545a44af57fd@brauner/T/#m0ba197d75b7921d994cf284f3cef3a62abb11aaa
I'm attempting to implement enough support in the Linux VFS to
enable file services like NFSD and ksmbd (and user space
equivale... | null | null | null | [PATCH v8 00/17] Subject: Exposing case folding behavior | From: Chuck Lever <chuck.lever@oracle.com>
Upper layers such as NFSD need a way to query whether a filesystem
handles filenames in a case-sensitive manner. Report CIFS/SMB case
handling behavior via the FS_XFLAG_CASEFOLD flag.
CIFS servers (typically Windows or Samba) are usually case-insensitive
but case-preserving,... | {
"author": "Chuck Lever <cel@kernel.org>",
"date": "Tue, 17 Feb 2026 16:47:34 -0500",
"is_openbsd": false,
"thread_id": "ua7rmlnvbfiadpxeynekbabwqebhcop3rhaxji7s3mgnwzhhtd@frz77j6wm2eg.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
Following on from
https://lore.kernel.org/linux-nfs/20251021-zypressen-bazillus-545a44af57fd@brauner/T/#m0ba197d75b7921d994cf284f3cef3a62abb11aaa
I'm attempting to implement enough support in the Linux VFS to
enable file services like NFSD and ksmbd (and user space
equivale... | null | null | null | [PATCH v8 00/17] Subject: Exposing case folding behavior | From: Chuck Lever <chuck.lever@oracle.com>
An NFS server re-exporting an NFS mount point needs to report the
case sensitivity behavior of the underlying filesystem to its
clients. Without this, re-export servers cannot accurately convey
case handling semantics, potentially causing client applications to
make incorrect... | {
"author": "Chuck Lever <cel@kernel.org>",
"date": "Tue, 17 Feb 2026 16:47:35 -0500",
"is_openbsd": false,
"thread_id": "ua7rmlnvbfiadpxeynekbabwqebhcop3rhaxji7s3mgnwzhhtd@frz77j6wm2eg.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
Following on from
https://lore.kernel.org/linux-nfs/20251021-zypressen-bazillus-545a44af57fd@brauner/T/#m0ba197d75b7921d994cf284f3cef3a62abb11aaa
I'm attempting to implement enough support in the Linux VFS to
enable file services like NFSD and ksmbd (and user space
equivale... | null | null | null | [PATCH v8 00/17] Subject: Exposing case folding behavior | From: Chuck Lever <chuck.lever@oracle.com>
NFS and other remote filesystem protocols need to determine
whether a local filesystem performs case-insensitive lookups
so they can provide correct semantics to clients. Without
this information, f2fs exports cannot properly advertise
their filename case behavior.
Report f2... | {
"author": "Chuck Lever <cel@kernel.org>",
"date": "Tue, 17 Feb 2026 16:47:36 -0500",
"is_openbsd": false,
"thread_id": "ua7rmlnvbfiadpxeynekbabwqebhcop3rhaxji7s3mgnwzhhtd@frz77j6wm2eg.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
Following on from
https://lore.kernel.org/linux-nfs/20251021-zypressen-bazillus-545a44af57fd@brauner/T/#m0ba197d75b7921d994cf284f3cef3a62abb11aaa
I'm attempting to implement enough support in the Linux VFS to
enable file services like NFSD and ksmbd (and user space
equivale... | null | null | null | [PATCH v8 00/17] Subject: Exposing case folding behavior | From: Chuck Lever <chuck.lever@oracle.com>
Upper layers such as NFSD need a way to query whether a
filesystem handles filenames in a case-sensitive manner. Report
VirtualBox shared folder case handling behavior via the
FS_XFLAG_CASEFOLD flag.
The case sensitivity property is queried from the VirtualBox host
service a... | {
"author": "Chuck Lever <cel@kernel.org>",
"date": "Tue, 17 Feb 2026 16:47:37 -0500",
"is_openbsd": false,
"thread_id": "ua7rmlnvbfiadpxeynekbabwqebhcop3rhaxji7s3mgnwzhhtd@frz77j6wm2eg.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
Following on from
https://lore.kernel.org/linux-nfs/20251021-zypressen-bazillus-545a44af57fd@brauner/T/#m0ba197d75b7921d994cf284f3cef3a62abb11aaa
I'm attempting to implement enough support in the Linux VFS to
enable file services like NFSD and ksmbd (and user space
equivale... | null | null | null | [PATCH v8 00/17] Subject: Exposing case folding behavior | From: Chuck Lever <chuck.lever@oracle.com>
Upper layers such as NFSD need a way to query whether a
filesystem handles filenames in a case-sensitive manner so
they can provide correct semantics to remote clients. Without
this information, NFS exports of ISO 9660 filesystems cannot
properly advertise their filename case... | {
"author": "Chuck Lever <cel@kernel.org>",
"date": "Tue, 17 Feb 2026 16:47:38 -0500",
"is_openbsd": false,
"thread_id": "ua7rmlnvbfiadpxeynekbabwqebhcop3rhaxji7s3mgnwzhhtd@frz77j6wm2eg.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
Following on from
https://lore.kernel.org/linux-nfs/20251021-zypressen-bazillus-545a44af57fd@brauner/T/#m0ba197d75b7921d994cf284f3cef3a62abb11aaa
I'm attempting to implement enough support in the Linux VFS to
enable file services like NFSD and ksmbd (and user space
equivale... | null | null | null | [PATCH v8 00/17] Subject: Exposing case folding behavior | From: Chuck Lever <chuck.lever@oracle.com>
The hard-coded MSDOS_SUPER_MAGIC check in nfsd3_proc_pathconf()
only recognizes FAT filesystems as case-insensitive. Modern
filesystems like F2FS, exFAT, and CIFS support case-insensitive
directories, but NFSv3 clients cannot discover this capability.
Query the export's actu... | {
"author": "Chuck Lever <cel@kernel.org>",
"date": "Tue, 17 Feb 2026 16:47:39 -0500",
"is_openbsd": false,
"thread_id": "ua7rmlnvbfiadpxeynekbabwqebhcop3rhaxji7s3mgnwzhhtd@frz77j6wm2eg.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
Following on from
https://lore.kernel.org/linux-nfs/20251021-zypressen-bazillus-545a44af57fd@brauner/T/#m0ba197d75b7921d994cf284f3cef3a62abb11aaa
I'm attempting to implement enough support in the Linux VFS to
enable file services like NFSD and ksmbd (and user space
equivale... | null | null | null | [PATCH v8 00/17] Subject: Exposing case folding behavior | From: Chuck Lever <chuck.lever@oracle.com>
NFSD currently provides NFSv4 clients with hard-coded responses
indicating all exported filesystems are case-sensitive and
case-preserving. This is incorrect for case-insensitive filesystems
and ext4 directories with casefold enabled.
Query the underlying filesystem's actual... | {
"author": "Chuck Lever <cel@kernel.org>",
"date": "Tue, 17 Feb 2026 16:47:40 -0500",
"is_openbsd": false,
"thread_id": "ua7rmlnvbfiadpxeynekbabwqebhcop3rhaxji7s3mgnwzhhtd@frz77j6wm2eg.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
Following on from
https://lore.kernel.org/linux-nfs/20251021-zypressen-bazillus-545a44af57fd@brauner/T/#m0ba197d75b7921d994cf284f3cef3a62abb11aaa
I'm attempting to implement enough support in the Linux VFS to
enable file services like NFSD and ksmbd (and user space
equivale... | null | null | null | [PATCH v8 00/17] Subject: Exposing case folding behavior | From: Chuck Lever <chuck.lever@oracle.com>
ksmbd hard-codes FILE_CASE_SENSITIVE_SEARCH and
FILE_CASE_PRESERVED_NAMES in FS_ATTRIBUTE_INFORMATION responses,
incorrectly indicating all exports are case-sensitive. This breaks
clients accessing case-insensitive filesystems like exFAT or
ext4/f2fs directories with casefold... | {
"author": "Chuck Lever <cel@kernel.org>",
"date": "Tue, 17 Feb 2026 16:47:41 -0500",
"is_openbsd": false,
"thread_id": "ua7rmlnvbfiadpxeynekbabwqebhcop3rhaxji7s3mgnwzhhtd@frz77j6wm2eg.mbox.gz"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.