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 | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On Tue, Feb 10, 2026 at 8:34 AM Pavel Begunkov <asml.silence@gmail.com> wrote:
Are there any optimizations with user-allocated buffers that wouldn't
be possible with kernel-allocated buffers? For huge pages, can't the
kernel do this as well (eg I see in io_mem_alloc_compound(), it calls
into alloc_pages() with order >... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Tue, 10 Feb 2026 11:39:24 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On Mon, Feb 9, 2026 at 4:53 PM Jens Axboe <axboe@kernel.dk> wrote:
The caller can, but from the caller side they only have access to the
cmd so they would need to do something like
struct io_kiocb *req = cmd_to_iocb_kiocb(ent->cmd);
buf_id = req->buf_index;
which may be kind of ugly with looking inside io-uring inte... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Tue, 10 Feb 2026 14:36:58 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On Mon, Feb 9, 2026 at 4:55 PM Jens Axboe <axboe@kernel.dk> wrote:
Thanks for reviewing the patches. The branch containing the userside
changes on top of these patches is in [1]. I'll make the changes you
pointed out in your other comments as part of v2. Once the discussion
with Pavel is resolved / figured out with th... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Tue, 10 Feb 2026 14:45:53 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On 2/10/26 19:39, Joanne Koong wrote:
...
Yes, there is handful of differences. To name one, 1MB allocation won't
get you a PMD mappable huge page, while user space can allocate 2MB,
register the first 1MB and reuse the rest for other purposes.
If io_create_region() is too strict, let's discuss that in
examples if t... | {
"author": "Pavel Begunkov <asml.silence@gmail.com>",
"date": "Wed, 11 Feb 2026 12:01:35 +0000",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On Tue, Feb 10, 2026 at 04:34:47PM +0000, Pavel Begunkov wrote:
Any pages mapped to userspace can be allocated in the kernel as well.
And I really do like this design, because it means we can have a
buffer ring that is only mapped read-only into userspace. That way
we can still do zero-copy raids if the device requi... | {
"author": "Christoph Hellwig <hch@infradead.org>",
"date": "Wed, 11 Feb 2026 07:45:36 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On Wed, Feb 11, 2026 at 4:01 AM Pavel Begunkov <asml.silence@gmail.com> wrote:
When I originally implemented it, I had it use
io_region_allocate_pages() but this fails because it's allocating way
too much memory at once. For fuse's use case, each buffer is usually
at least 1 MB if not more. Allocating the memory one b... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Wed, 11 Feb 2026 14:06:18 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On Wed, Feb 11, 2026 at 02:06:18PM -0800, Joanne Koong wrote:
I'm arguing exactly against this. For my use case I need a setup
where the kernel controls the allocation fully and guarantees user
processes can only read the memory but never write to it. I'd love
to be able to piggy back than onto your work. | {
"author": "Christoph Hellwig <hch@infradead.org>",
"date": "Thu, 12 Feb 2026 02:07:48 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On 2/11/26 15:45, Christoph Hellwig wrote:
pow2 round ups will waste memory. 1MB allocations will never
become 2MB huge pages. And there is a separate question of
1GB huge pages. The user can be smarter about all placement
decisions.
That's an interesting case. To be clear, user provided memory is
an optional featur... | {
"author": "Pavel Begunkov <asml.silence@gmail.com>",
"date": "Thu, 12 Feb 2026 10:44:44 +0000",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On 2/12/26 10:07, Christoph Hellwig wrote:
IORING_REGISTER_MEM_REGION supports both types of allocations. It can
have a new registration flag for read-only, and then you either make
the bounce avoidance optional or reject binding fuse to unsupported
setups during init. Any arguments against that? I need to go over
Joa... | {
"author": "Pavel Begunkov <asml.silence@gmail.com>",
"date": "Thu, 12 Feb 2026 10:52:29 +0000",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On Thu, Feb 12, 2026 at 2:52 AM Pavel Begunkov <asml.silence@gmail.com> wrote:
By "control the allocation fully" do you mean for your use case, the
allocation/setup isn't triggered by userspace but is initiated by the
kernel (eg user never explicitly registers any kbuf ring, the kernel
just uses the kbuf ring data str... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Thu, 12 Feb 2026 09:29:31 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On Thu, Feb 12, 2026 at 10:44:44AM +0000, Pavel Begunkov wrote:
Sure. But if the application cares that much about TLB pressure
I'd just round up to nice multtiple of PTE levels.
Can you clarify what you mean with 'pbuf'? The only fixed buffer API I
know is io_uring_register_buffers* which always takes user provid... | {
"author": "Christoph Hellwig <hch@infradead.org>",
"date": "Thu, 12 Feb 2026 23:18:55 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On Thu, Feb 12, 2026 at 10:52:29AM +0000, Pavel Begunkov wrote:
IORING_REGISTER_MEM_REGION seems to be all about cqs from both your
commit message and the public documentation. I'm confused.
My use case is not about fuse, but good old block and file system
I/O. | {
"author": "Christoph Hellwig <hch@infradead.org>",
"date": "Thu, 12 Feb 2026 23:21:39 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On Thu, Feb 12, 2026 at 09:29:31AM -0800, Joanne Koong wrote:
The idea is that the application tells the kernel that it wants to use
a fixed buffer pool for reads. Right now the application does this
using io_uring_register_buffers(). The problem with that is that
io_uring_register_buffers ends up just doing a pin o... | {
"author": "Christoph Hellwig <hch@infradead.org>",
"date": "Thu, 12 Feb 2026 23:27:47 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On 2/13/26 07:18, Christoph Hellwig wrote:
Registered, aka fixed, buffers are the ones you pass to
IORING_OP_[READ,WRITE]_FIXED and some other requests. It's normally
created by io_uring_register_buffers*() / IORING_REGISTER_BUFFERS*
with user memory, but there are special cases when it's installed
internally by other... | {
"author": "Pavel Begunkov <asml.silence@gmail.com>",
"date": "Fri, 13 Feb 2026 12:41:07 +0000",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On 2/13/26 07:21, Christoph Hellwig wrote:
Think of it as an area of memory for kernel-user communication. Used
for syscall parameters passing to avoid copy_from_user, but I added
it for a bunch of use cases. We'll hopefully get support at some
point for passing request arguments like struct iovec. BPF patches
use it ... | {
"author": "Pavel Begunkov <asml.silence@gmail.com>",
"date": "Fri, 13 Feb 2026 13:18:54 +0000",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On 2/11/26 22:06, Joanne Koong wrote:
...
Let's fix that then. For now, just work it around by wrapping
into a loop.
Btw, I thought you're going to use it for metadata like some
fuse headers and payloads would be zero copied by installing
it as registered buffers.
...
The main point is disentangling memory allocati... | {
"author": "Pavel Begunkov <asml.silence@gmail.com>",
"date": "Fri, 13 Feb 2026 15:26:50 +0000",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On 2/13/26 07:27, Christoph Hellwig wrote:
There is nothing about registered buffers in this series. And even
if you try to reuse buffer allocation out of it, it'll come with
a circular buffer you'll have no need for. And I'm pretty much
arguing about separating those for io_uring.
--
Pavel Begunkov | {
"author": "Pavel Begunkov <asml.silence@gmail.com>",
"date": "Fri, 13 Feb 2026 15:31:49 +0000",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On 2/13/26 15:31, Pavel Begunkov wrote:
FWIW, the easiest solution is to internally reuse regions for
allocations and mmap()'ing and wrap it into a registered buffer.
It just need to make vmap'ing optional as it won't be needed.
--
Pavel Begunkov | {
"author": "Pavel Begunkov <asml.silence@gmail.com>",
"date": "Fri, 13 Feb 2026 15:48:11 +0000",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On 2/12/26 17:29, Joanne Koong wrote:
No, it's mainly about not keeping payload buffers and rings in the same
object from the io_uring uapi perspective.
1. If it's an io_uring uapi, it shouldn't be fuse specific or with
a bunch of use case specific expectations attached. Why does it
require all buffers to be uniform ... | {
"author": "Pavel Begunkov <asml.silence@gmail.com>",
"date": "Fri, 13 Feb 2026 16:27:44 +0000",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On Fri, Feb 13, 2026 at 7:31 AM Pavel Begunkov <asml.silence@gmail.com> wrote:
I think the circular buffer will be useful for Christoph's use case in
the same way it'll be useful for fuse's. The read payload could be
differently sized across requests, so it's a lot of wasted space to
have to allocate a buffer large en... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 13 Feb 2026 11:09:13 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On Thu, Feb 12, 2026 at 11:27 PM Christoph Hellwig <hch@infradead.org> wrote:
(resending because I hit reply instead of reply-all)
I think we have the exact same use case, except your buffers need to
be read-only. I think your use case benefits from the same memory wins
we'll get with incremental buffer consumption, ... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 13 Feb 2026 11:14:03 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On 2/13/26 20:09, Joanne Koong wrote:
Dunno, what we actually want is requests of multiple sizes. Sharing
buffers across entries sounds like just reducing the ring size - I
personally don't see the point here.
Thanks,
Bernd | {
"author": "Bernd Schubert <bernd@bsbernd.com>",
"date": "Fri, 13 Feb 2026 20:30:32 +0100",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On Fri, Feb 13, 2026 at 11:30 AM Bernd Schubert <bernd@bsbernd.com> wrote:
By "sharing buffers across entries" what I mean is different regions
of the buffer can now be used concurrently by multiple entries.
Thanks,
Joanne | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 13 Feb 2026 11:38:55 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On Fri, Feb 13, 2026 at 4:41 AM Pavel Begunkov <asml.silence@gmail.com> wrote:
The most important part and the whole reason fuse needs the buffer
ring to be kernel-managed is because the kernel needs to control when
buffers get recycled back into the ring. For fuse's use case, the
buffer is used for passing data betwe... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 13 Feb 2026 14:04:06 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On Fri, Feb 13, 2026 at 11:09:13AM -0800, Joanne Koong wrote:
Yes.
Or enable such flexible use cases at all. | {
"author": "Christoph Hellwig <hch@infradead.org>",
"date": "Mon, 16 Feb 2026 21:36:20 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On Fri, Feb 13, 2026 at 11:14:03AM -0800, Joanne Koong wrote:
Yeah.
Yes, tat's what I though. But Pavel seems to disagree? | {
"author": "Christoph Hellwig <hch@infradead.org>",
"date": "Mon, 16 Feb 2026 21:38:48 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On 2/17/26 05:38, Christoph Hellwig wrote:
Provided buffer rings are not useful for storage read/write requests
because they bind to a buffer right away, that's in contrast to some
recv request, where io_uring will first poll the socket to confirm
the data is there, and only then take a buffer from the buffer ring
and... | {
"author": "Pavel Begunkov <asml.silence@gmail.com>",
"date": "Wed, 18 Feb 2026 09:51:07 +0000",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On 2/13/26 22:04, Joanne Koong wrote:
...
Oops, typo. I was asking whether the buffer rings (not buffers) are
supposed to be used with other requests. E.g. submitting a
IORING_OP_RECV with IOSQE_BUFFER_SELECT set and the bgid specifying
your kernel-managed buffer ring.
There are two separate arguments. The first is ... | {
"author": "Pavel Begunkov <asml.silence@gmail.com>",
"date": "Wed, 18 Feb 2026 12:36:43 +0000",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On Wed, Feb 18, 2026 at 4:36 AM Pavel Begunkov <asml.silence@gmail.com> wrote:
Sorry, I submitted v2 last night thinking the conversation on this
thread had died. After reading through your reply, I'll modify v2.
Yes the buffer rings are intended to be used with other io-uring
requests. The ideal scenario is that th... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Wed, 18 Feb 2026 13:43:38 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On 2/18/26 21:43, Joanne Koong wrote:
No worries at all, and sorry I'm a bit slow to reply
You mention OP_READ_FIXED and below agreed not exposing km rings
an io_uring uapi, which makes me believe we're still talking about
different things.
Correct me if I'm wrong. Currently, only fuse cmds use the buffer
ring itse... | {
"author": "Pavel Begunkov <asml.silence@gmail.com>",
"date": "Fri, 20 Feb 2026 12:53:10 +0000",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On Fri, Feb 20, 2026 at 4:53 AM Pavel Begunkov <asml.silence@gmail.com> wrote:
Thanks for clarifying your question. Yes, this would be a useful
optimization in the future for fuse servers with certain workload
characteristics (eg network-backed servers with high concurrency and
unpredictable latencies). I don't think ... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 20 Feb 2026 18:14:28 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On 2/21/26 02:14, Joanne Koong wrote:
...
Sorry, I don't see relevance b/w km rings and what Christoph wants.
I explained why in some sub-thread, but maybe someone can tell
what I'm missing.
Yep, it could be, potentially, it's just the patchset doesn't plumb
it to other requests and uses it within fuse. It's just ca... | {
"author": "Pavel Begunkov <asml.silence@gmail.com>",
"date": "Mon, 23 Feb 2026 20:00:15 +0000",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On Mon, Feb 23, 2026 at 12:00 PM Pavel Begunkov <asml.silence@gmail.com> wrote:
This patchset just represents the most basic foundation. The
optimization patches (eg incremental buffer consumption, plumbing it
to other io-uring requests, etc) were to be follow-up patchsets that
would be on top of this.
It's not real... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Tue, 24 Feb 2026 14:19:56 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Currently, io_uring buffer rings require the application to allocate and
manage the backing buffers. This series introduces kernel-managed buffer
rings, where the kernel allocates and manages the buffers on behalf of
the application.
This is split out from the fuse over io_uring series in [1], which needs the
kernel t... | null | null | null | [PATCH v1 00/11] io_uring: add kernel-managed buffer rings | On Wed, Feb 11, 2026 at 2:06 PM Joanne Koong <joannelkoong@gmail.com> wrote:
I still think the memory for the buffers should be tied to the ring
itself and allocated physically contiguously per buffer. Per-buffer
contiguity will enable the most efficient DMA path for servers to send
read/write data to local storage or... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Thu, 26 Feb 2026 17:12:01 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1YoaHnCmuwQra0XwOxf0aC_PQGby-DT1y_p=YRzotiE-w@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Here are three bug fixes found with Smatch.
Ethan Tidmore (3):
ntfs: Place check before dereference
ntfs: Add missing error code
ntfs: Fix possible deadlock
fs/ntfs/attrib.c | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
--
2.53.0
| null | null | null | [PATCH 0/3] ntfs: Bug fixes for attrib.c | The variable ni has the possiblity of being null and is checked for it
but, only after it was dereferenced in a log message.
Put check before dereference.
Detected by Smatch:
fs/ntfs/attrib.c:2115 ntfs_resident_attr_record_add() warn:
variable dereferenced before check 'ni' (see line 2111)
fs/ntfs/attrib.c:2237 ntfs... | {
"author": "Ethan Tidmore <ethantidmore06@gmail.com>",
"date": "Thu, 26 Feb 2026 10:09:04 -0600",
"is_openbsd": false,
"thread_id": "CAKYAXd_9FHR1WaN7GuKwSBsYeO1gS4m=2n+wz+LSapu4Tp7kCg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Here are three bug fixes found with Smatch.
Ethan Tidmore (3):
ntfs: Place check before dereference
ntfs: Add missing error code
ntfs: Fix possible deadlock
fs/ntfs/attrib.c | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
--
2.53.0
| null | null | null | [PATCH 0/3] ntfs: Bug fixes for attrib.c | If ntfs_attr_iget() fails no error code is assigned to be returned.
Detected by Smatch:
fs/ntfs/attrib.c:2665 ntfs_attr_add() warn:
missing error code 'err'
Signed-off-by: Ethan Tidmore <ethantidmore06@gmail.com>
---
fs/ntfs/attrib.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/ntfs/attrib.c b/fs/ntfs/attr... | {
"author": "Ethan Tidmore <ethantidmore06@gmail.com>",
"date": "Thu, 26 Feb 2026 10:09:05 -0600",
"is_openbsd": false,
"thread_id": "CAKYAXd_9FHR1WaN7GuKwSBsYeO1gS4m=2n+wz+LSapu4Tp7kCg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Here are three bug fixes found with Smatch.
Ethan Tidmore (3):
ntfs: Place check before dereference
ntfs: Add missing error code
ntfs: Fix possible deadlock
fs/ntfs/attrib.c | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
--
2.53.0
| null | null | null | [PATCH 0/3] ntfs: Bug fixes for attrib.c | In the error path for ntfs_attr_map_whole_runlist() the lock is not
released.
Add release for lock.
Detected by Smatch:
fs/ntfs/attrib.c:5197 ntfs_non_resident_attr_collapse_range() warn:
inconsistent returns '&ni->runlist.lock'.
Fixes: 495e90fa33482 ("ntfs: update attrib operations")
Signed-off-by: Ethan Tidmore <e... | {
"author": "Ethan Tidmore <ethantidmore06@gmail.com>",
"date": "Thu, 26 Feb 2026 10:09:06 -0600",
"is_openbsd": false,
"thread_id": "CAKYAXd_9FHR1WaN7GuKwSBsYeO1gS4m=2n+wz+LSapu4Tp7kCg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Here are three bug fixes found with Smatch.
Ethan Tidmore (3):
ntfs: Place check before dereference
ntfs: Add missing error code
ntfs: Fix possible deadlock
fs/ntfs/attrib.c | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
--
2.53.0
| null | null | null | [PATCH 0/3] ntfs: Bug fixes for attrib.c | On Thu, Feb 26, 2026 at 10:09:04AM -0600, Ethan Tidmore wrote:
Looks good to me. Thank for the patch
Reviewed-by: Hyunchul Lee <hyc.lee@gmail.com>
--
Thanks,
Hyunchul | {
"author": "Hyunchul Lee <hyc.lee@gmail.com>",
"date": "Fri, 27 Feb 2026 11:32:14 +0900",
"is_openbsd": false,
"thread_id": "CAKYAXd_9FHR1WaN7GuKwSBsYeO1gS4m=2n+wz+LSapu4Tp7kCg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Here are three bug fixes found with Smatch.
Ethan Tidmore (3):
ntfs: Place check before dereference
ntfs: Add missing error code
ntfs: Fix possible deadlock
fs/ntfs/attrib.c | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
--
2.53.0
| null | null | null | [PATCH 0/3] ntfs: Bug fixes for attrib.c | On Thu, Feb 26, 2026 at 10:09:05AM -0600, Ethan Tidmore wrote:
Looks good to me. Thank for the patch
Reviewed-by: Hyunchul Lee <hyc.lee@gmail.com>
--
Thanks,
Hyunchul | {
"author": "Hyunchul Lee <hyc.lee@gmail.com>",
"date": "Fri, 27 Feb 2026 11:37:24 +0900",
"is_openbsd": false,
"thread_id": "CAKYAXd_9FHR1WaN7GuKwSBsYeO1gS4m=2n+wz+LSapu4Tp7kCg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Here are three bug fixes found with Smatch.
Ethan Tidmore (3):
ntfs: Place check before dereference
ntfs: Add missing error code
ntfs: Fix possible deadlock
fs/ntfs/attrib.c | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
--
2.53.0
| null | null | null | [PATCH 0/3] ntfs: Bug fixes for attrib.c | On Thu, Feb 26, 2026 at 10:09:06AM -0600, Ethan Tidmore wrote:
Looks good to me. Thank for the patch
Reviewed-by: Hyunchul Lee <hyc.lee@gmail.com>
--
Thanks,
Hyunchul | {
"author": "Hyunchul Lee <hyc.lee@gmail.com>",
"date": "Fri, 27 Feb 2026 11:38:39 +0900",
"is_openbsd": false,
"thread_id": "CAKYAXd_9FHR1WaN7GuKwSBsYeO1gS4m=2n+wz+LSapu4Tp7kCg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Here are three bug fixes found with Smatch.
Ethan Tidmore (3):
ntfs: Place check before dereference
ntfs: Add missing error code
ntfs: Fix possible deadlock
fs/ntfs/attrib.c | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
--
2.53.0
| null | null | null | [PATCH 0/3] ntfs: Bug fixes for attrib.c | On Fri, Feb 27, 2026 at 1:09 AM Ethan Tidmore <ethantidmore06@gmail.com> wrote:
Applied them to #ntfs-next.
Thanks! | {
"author": "Namjae Jeon <linkinjeon@kernel.org>",
"date": "Fri, 27 Feb 2026 18:44:49 +0900",
"is_openbsd": false,
"thread_id": "CAKYAXd_9FHR1WaN7GuKwSBsYeO1gS4m=2n+wz+LSapu4Tp7kCg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Christian said [1] to "just do it" when I proposed this, so here we are!
For historical reasons, the inode->i_ino field is an unsigned long,
which means that it's 32 bits on 32 bit architectures. This has caused a
number of filesystems to implement hacks to hash a 64-bit identifier
into a 32-bit field, and deprives us... | null | null | null | [PATCH 00/61] vfs: change inode->i_ino from unsigned long to u64 | On 2026-02-26 10:55, Jeff Layton wrote:
[ Trimming huge CC list. ]
May I recommend shrinking the CC list to the list of people who actually
need to be CC'd on individual changes ? Yes, this is a big task on a 61
patches series, but it's part of the expected work that goes into
submitting a large series like this.
T... | {
"author": "Mathieu Desnoyers <mathieu.desnoyers@efficios.com>",
"date": "Thu, 26 Feb 2026 11:08:16 -0500",
"is_openbsd": false,
"thread_id": "0bc9e485e475a12e1e2c9a73b781308fd94a97a4.camel@ibm.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Christian said [1] to "just do it" when I proposed this, so here we are!
For historical reasons, the inode->i_ino field is an unsigned long,
which means that it's 32 bits on 32 bit architectures. This has caused a
number of filesystems to implement hacks to hash a 64-bit identifier
into a 32-bit field, and deprives us... | null | null | null | [PATCH 00/61] vfs: change inode->i_ino from unsigned long to u64 | On 2026-02-26 10:56, Jeff Layton wrote:
Doing this as a fixup at the end of the series breaks bissectability.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com | {
"author": "Mathieu Desnoyers <mathieu.desnoyers@efficios.com>",
"date": "Thu, 26 Feb 2026 11:11:46 -0500",
"is_openbsd": false,
"thread_id": "0bc9e485e475a12e1e2c9a73b781308fd94a97a4.camel@ibm.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Christian said [1] to "just do it" when I proposed this, so here we are!
For historical reasons, the inode->i_ino field is an unsigned long,
which means that it's 32 bits on 32 bit architectures. This has caused a
number of filesystems to implement hacks to hash a 64-bit identifier
into a 32-bit field, and deprives us... | null | null | null | [PATCH 00/61] vfs: change inode->i_ino from unsigned long to u64 | On 2026-02-26 10:55, Jeff Layton wrote:
Changing this type first without changing its associated format strings
breaks git bisect.
One alternative would be to introduce something like the PRIu64 macro
but for printing inode values. This would allow gradually introducing
the change without breaking the world as you do... | {
"author": "Mathieu Desnoyers <mathieu.desnoyers@efficios.com>",
"date": "Thu, 26 Feb 2026 11:16:50 -0500",
"is_openbsd": false,
"thread_id": "0bc9e485e475a12e1e2c9a73b781308fd94a97a4.camel@ibm.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Christian said [1] to "just do it" when I proposed this, so here we are!
For historical reasons, the inode->i_ino field is an unsigned long,
which means that it's 32 bits on 32 bit architectures. This has caused a
number of filesystems to implement hacks to hash a 64-bit identifier
into a 32-bit field, and deprives us... | null | null | null | [PATCH 00/61] vfs: change inode->i_ino from unsigned long to u64 | On Thu, 2026-02-26 at 11:16 -0500, Mathieu Desnoyers wrote:
True, but it makes all of the format strings even harder to read. After
the conversion, we could go back and eliminate the macro though and it
would keep things more bisectable. I'm not sure what to do about
tracepoints though. I guess we could declare a new ... | {
"author": "Jeff Layton <jlayton@kernel.org>",
"date": "Thu, 26 Feb 2026 11:35:41 -0500",
"is_openbsd": false,
"thread_id": "0bc9e485e475a12e1e2c9a73b781308fd94a97a4.camel@ibm.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Christian said [1] to "just do it" when I proposed this, so here we are!
For historical reasons, the inode->i_ino field is an unsigned long,
which means that it's 32 bits on 32 bit architectures. This has caused a
number of filesystems to implement hacks to hash a 64-bit identifier
into a 32-bit field, and deprives us... | null | null | null | [PATCH 00/61] vfs: change inode->i_ino from unsigned long to u64 | On 2026-02-26 11:35, Jeff Layton wrote:
For tracepoints there are two things: a TP_printk format string (which
would be handled by a new pretty printing macro similar to PRIu64), and
the type used within TP_STRUCT__entry. I don't see why you'd need to
change from ino_t to u64 there. The conversion will happen when you... | {
"author": "Mathieu Desnoyers <mathieu.desnoyers@efficios.com>",
"date": "Thu, 26 Feb 2026 11:40:53 -0500",
"is_openbsd": false,
"thread_id": "0bc9e485e475a12e1e2c9a73b781308fd94a97a4.camel@ibm.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Christian said [1] to "just do it" when I proposed this, so here we are!
For historical reasons, the inode->i_ino field is an unsigned long,
which means that it's 32 bits on 32 bit architectures. This has caused a
number of filesystems to implement hacks to hash a 64-bit identifier
into a 32-bit field, and deprives us... | null | null | null | [PATCH 00/61] vfs: change inode->i_ino from unsigned long to u64 | On Thu, 2026-02-26 at 11:40 -0500, Mathieu Desnoyers wrote:
My worry here is that ino_t is a UAPI type, and I don't think we can
change it there. I think we'll need a new (kernel-internal) typedef
just for this.
Definitely. None of that would be trustworthy in the middle of the
series.
--
Jeff Layton <jlayton@kerne... | {
"author": "Jeff Layton <jlayton@kernel.org>",
"date": "Thu, 26 Feb 2026 11:45:16 -0500",
"is_openbsd": false,
"thread_id": "0bc9e485e475a12e1e2c9a73b781308fd94a97a4.camel@ibm.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Christian said [1] to "just do it" when I proposed this, so here we are!
For historical reasons, the inode->i_ino field is an unsigned long,
which means that it's 32 bits on 32 bit architectures. This has caused a
number of filesystems to implement hacks to hash a 64-bit identifier
into a 32-bit field, and deprives us... | null | null | null | [PATCH 00/61] vfs: change inode->i_ino from unsigned long to u64 | On 2026-02-26 11:45, Jeff Layton wrote:
If ino_t is UAPI then it cannot be changed, but you can introduce a new
kino_t or whatever naming is appropriate.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com | {
"author": "Mathieu Desnoyers <mathieu.desnoyers@efficios.com>",
"date": "Thu, 26 Feb 2026 11:48:18 -0500",
"is_openbsd": false,
"thread_id": "0bc9e485e475a12e1e2c9a73b781308fd94a97a4.camel@ibm.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Christian said [1] to "just do it" when I proposed this, so here we are!
For historical reasons, the inode->i_ino field is an unsigned long,
which means that it's 32 bits on 32 bit architectures. This has caused a
number of filesystems to implement hacks to hash a 64-bit identifier
into a 32-bit field, and deprives us... | null | null | null | [PATCH 00/61] vfs: change inode->i_ino from unsigned long to u64 | On Thu 26-02-26 11:45:16, Jeff Layton wrote:
Yeah, I think defining kino_t in the beginning as unsigned long, convert
everything (including special format string specifier) to it, then switch
it to u64 and finally just 'sed-out' the format string specifier in the
final patch shouldn't be harder than what you do here a... | {
"author": "Jan Kara <jack@suse.cz>",
"date": "Thu, 26 Feb 2026 18:19:20 +0100",
"is_openbsd": false,
"thread_id": "0bc9e485e475a12e1e2c9a73b781308fd94a97a4.camel@ibm.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Christian said [1] to "just do it" when I proposed this, so here we are!
For historical reasons, the inode->i_ino field is an unsigned long,
which means that it's 32 bits on 32 bit architectures. This has caused a
number of filesystems to implement hacks to hash a 64-bit identifier
into a 32-bit field, and deprives us... | null | null | null | [PATCH 00/61] vfs: change inode->i_ino from unsigned long to u64 | On Thu, 2026-02-26 at 18:19 +0100, Jan Kara wrote:
Ok. I'll look at doing it in a way that doesn't break bisectability.
--
Jeff Layton <jlayton@kernel.org> | {
"author": "Jeff Layton <jlayton@kernel.org>",
"date": "Thu, 26 Feb 2026 12:59:31 -0500",
"is_openbsd": false,
"thread_id": "0bc9e485e475a12e1e2c9a73b781308fd94a97a4.camel@ibm.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Christian said [1] to "just do it" when I proposed this, so here we are!
For historical reasons, the inode->i_ino field is an unsigned long,
which means that it's 32 bits on 32 bit architectures. This has caused a
number of filesystems to implement hacks to hash a 64-bit identifier
into a 32-bit field, and deprives us... | null | null | null | [PATCH 00/61] vfs: change inode->i_ino from unsigned long to u64 | On Thu, 26 Feb 2026 11:16:50 -0500
Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:
Or find all the format strings, change to %llu and add (u64) casts.
That should compile and run in both 32bit and 64bit.
At the end you could delete the casts.
David | {
"author": "David Laight <david.laight.linux@gmail.com>",
"date": "Thu, 26 Feb 2026 18:12:52 +0000",
"is_openbsd": false,
"thread_id": "0bc9e485e475a12e1e2c9a73b781308fd94a97a4.camel@ibm.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <john@groves.net>
This patch series is available as a git tag at [0].
Changes v6 -> v7
- Fixed a regression in famfs_interleave_fileofs_to_daxofs() that
was reported by Intel's kernel test robot
- Added a check in __fsdev_dax_direct_access() for negative return
from pgoff_to_phys(), whic... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:30:25 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <john@groves.net>
This function will be used by both device.c and fsdev.c, but both are
loadable modules. Moving to bus.c puts it in core and makes it available
to both.
No code changes - just relocated.
Signed-off-by: John Groves <john@groves.net>
---
drivers/dax/bus.c | 24 +++++++++... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:31:08 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <John@Groves.net>
Both fs/dax.c:dax_folio_put() and drivers/dax/fsdev.c:
fsdev_clear_folio_state() (the latter coming in the next commit after this
one) contain nearly identical code to reset a compound DAX folio back to
order-0 pages. Factor this out into a shared helper function.
The new da... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:31:20 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <john@groves.net>
The new fsdev driver provides pages/folios initialized compatibly with
fsdax - normal rather than devdax-style refcounting, and starting out
with order-0 folios.
When fsdev binds to a daxdev, it is usually (always?) switching from the
devdax mode (device.c), which pre-initia... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:31:35 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <john@groves.net>
Save the kva from memremap because we need it for iomap rw support.
Prior to famfs, there were no iomap users of /dev/dax - so the virtual
address from memremap was not needed.
Signed-off-by: John Groves <john@groves.net>
---
drivers/dax/dax-private.h | 2 ++
drivers/dax/fsdev.c ... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:31:45 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <John@Groves.net>
fsdev: Add dax_operations for use by famfs
- These methods are based on pmem_dax_ops from drivers/nvdimm/pmem.c
- fsdev_dax_direct_access() returns the hpa, pfn and kva. The kva was
newly stored as dev_dax->virt_addr by dev_dax_probe().
- The hpa/pfn are used for mmap (dax... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:31:54 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <John@Groves.net>
Add a new dax_set_ops() function that allows drivers to set the
dax_operations after the dax_device has been allocated. This is needed
for fsdev_dax where the operations need to be set during probe and
cleared during unbind.
The fsdev driver uses devm_add_action_or_reset() f... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:32:03 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <john@groves.net>
The fs_dax_get() function should be called by fs-dax file systems after
opening a fsdev dax device. This adds holder_operations, which provides
a memory failure callback path and effects exclusivity between callers
of fs_dax_get().
fs_dax_get() is specific to fsdev_dax, so i... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:32:12 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <john@groves.net>
famfs needs to look up a dax_device by dev_t when resolving fmap
entries that reference character dax devices.
Signed-off-by: John Groves <john@groves.net>
---
drivers/dax/super.c | 3 ++-
include/linux/dax.h | 1 +
2 files changed, 3 insertions(+), 1 deletion(-)
diff ... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:32:22 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <john@groves.net>
Famfs distinguishes between its on-media and in-memory superblocks. This
reserves the numbers, but they are only used by the user space
components of famfs.
Signed-off-by: John Groves <john@groves.net>
---
include/uapi/linux/magic.h | 2 ++
1 file changed, 2 insertions(+)
diff --... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:32:32 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <john@groves.net>
Virtio_fs now needs to determine if an inode is DAX && not famfs.
This relaces the FUSE_IS_DAX() macro with FUSE_IS_VIRTIO_DAX(),
in preparation for famfs in later commits. The dummy
fuse_file_famfs() macro will be replaced with a working
function.
Reviewed-by: Joanne Koong... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:32:44 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <john@groves.net>
This patch starts the kernel ABI enablement of famfs in fuse.
- Kconfig: Add FUSE_FAMFS_DAX config parameter, to control
compilation of famfs within fuse.
- FUSE_DAX_FMAP flag in INIT request/reply
- fuse_conn->famfs_iomap (enable famfs-mapped files) to denote a
famfs-e... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:32:55 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <john@groves.net>
Upon completion of an OPEN, if we're in famfs-mode we do a GET_FMAP to
retrieve and cache up the file-to-dax map in the kernel. If this
succeeds, read/write/mmap are resolved direct-to-dax with no upcalls.
Signed-off-by: John Groves <john@groves.net>
---
MAINTAINERS ... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:33:04 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <john@groves.net>
On completion of GET_FMAP message/response, setup the full famfs
metadata such that it's possible to handle read/write/mmap directly to
dax. Note that the devdax_iomap plumbing is not in yet...
* Add famfs_kfmap.h: in-memory structures for resolving famfs file maps
(fmaps)... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:33:13 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <john@groves.net>
- The new GET_DAXDEV message/response is added
- The famfs.c:famfs_teardown() function is added as a primary teardown
function for famfs.
- The command it triggered by the update_daxdev_table() call, if there
are any daxdevs in the subject fmap that are not represented in ... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:33:22 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <john@groves.net>
This commit fills in read/write/mmap handling for famfs files. The
dev_dax_iomap interface is used - just like xfs in fs-dax mode.
- Read/write are handled by famfs_fuse_[read|write]_iter() via
dax_iomap_rw() to fsdev_dax.
- Mmap is handled by famfs_fuse_mmap()
- Faults a... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:33:32 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <john@groves.net>
Memory errors are at least somewhat more likely on disaggregated memory
than on-board memory. This commit registers to be notified by fsdev_dax
in the event that a memory failure is detected.
When a file access resolves to a daxdev with memory errors, it will fail
with an ap... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:33:41 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <John@Groves.net>
Famfs is memory-backed; there is no place to write back to, and no
reason to mark pages dirty at all.
Signed-off-by: John Groves <john@groves.net>
---
fs/fuse/famfs.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/fs/fuse/famfs.c b/fs/fuse/famfs.c
inde... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:33:51 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <John@Groves.net>
This describes the fmap metadata - both simple and interleaved
Signed-off-by: John Groves <john@groves.net>
---
fs/fuse/famfs_kfmap.h | 73 +++++++++++++++++++++++++++++++++++++++++++
1 file changed, 73 insertions(+)
diff --git a/fs/fuse/famfs_kfmap.h b/fs/fuse/famfs_kfm... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:34:18 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <john@groves.net>
Add Documentation/filesystems/famfs.rst and update MAINTAINERS
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
Signed-off-by: John Groves <john@groves.net>
---
Do... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:34:29 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <john@groves.net>
This short series adds adds the necessary support for famfs to libfuse.
This series is also a pull request at [1].
Changes v4 -> v5 -> v6 -> v7: none, re-sending due to technical challenges
Changes v3 -> v4
- The patch "add API to set kernel mount options" has been dropped. I fou... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:34:50 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <john@groves.net>
This is copied from include/uapi/linux/fuse.h in 6.19 with no changes.
Signed-off-by: John Groves <john@groves.net>
---
include/fuse_kernel.h | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/include/fuse_kernel.h b/include/fuse_kernel.h
index 94621f6..... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:35:26 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <john@groves.net>
Add FUSE protocol version 7.46 definitions for famfs DAX file mapping:
Capability flag:
- FUSE_DAX_FMAP (bit 43): kernel supports DAX fmap operations
New opcodes:
- FUSE_GET_FMAP (54): retrieve file extent map for DAX mapping
- FUSE_GET_DAXDEV (55): retrieve DAX dev... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:35:37 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <john@groves.net>
Add new FUSE operations and capability for famfs DAX file mapping:
- FUSE_CAP_DAX_FMAP: New capability flag at bit 32 (using want_ext/capable_ext
fields) to indicate kernel and userspace support for DAX fmaps
- GET_FMAP: New operation to retrieve a file map for DAX-mapped... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:35:46 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <john@groves.net>
No change since V2 - re-sending due to technical challenges.
No change since V1 - reposting as V2 to keep this with the related
kernel (dax and fuse) patches and libfuse patches.
This short series adds support and tests to daxctl for famfs[1]. The
famfs kernel patch series, under ... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:36:02 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <John@Groves.net>
Putting a daxdev in famfs mode means binding it to fsdev_dax.ko
(drivers/dax/fsdev.c). Finding a daxdev bound to fsdev_dax means
it is in famfs mode.
The test is added to the destructive test suite since it
modifies device modes.
With devdax, famfs, and system-ram modes, ... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:36:38 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | From: John Groves <John@Groves.net>
- devdax <-> famfs mode switches
- Verify famfs -> system-ram is rejected (must go via devdax)
- Test JSON output shows correct mode
- Test error handling for invalid modes
The test is added to the destructive test suite since it
modifies device modes.
Signed-off-by: Joh... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Sun, 18 Jan 2026 22:36:48 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | On Sun, 18 Jan 2026 22:29:18 +0000
John Groves <john@jagalactic.com> wrote:
Hi John,
I wonder if these new patches sent recently have been reflected on the github repo readme files. It seems it is not, is it? | {
"author": "Alireza Sanaee <alireza.sanaee@huawei.com>",
"date": "Tue, 20 Jan 2026 09:12:17 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | On 26/01/20 09:12AM, Alireza Sanaee wrote:
[ ... ]
Hi Ali,
[5] points to the main famfs user space repo; I haven't updated documentation
there yet. The master branch there works with this patch set, and also
remains compatible with famfs kernels back to 6.8 (both fuse and standalone),
but I recommend this... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Tue, 20 Jan 2026 15:13:08 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | On Sun, 18 Jan 2026 22:36:02 +0000
John Groves <john@jagalactic.com> wrote:
Hi John,
What's the base commit for this set? I seem not be able to apply on ndctl master. Maybe I am missing something.
Thanks,
Alireza | {
"author": "Alireza Sanaee <alireza.sanaee@huawei.com>",
"date": "Tue, 20 Jan 2026 17:01:35 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | On 26/01/20 05:01PM, Alireza Sanaee wrote:
This series is based on the v83 tag, which is sha 4f7a1c6.
John | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Tue, 20 Jan 2026 17:05:38 +0000",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | On Sun, Jan 18, 2026 at 2:35 PM John Groves <john@jagalactic.com> wrote:
This LGTM. We could probably just merge this in already.
Reviewed-by: Joanne Koong <joannelkoong@gmail.com> | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 30 Jan 2026 14:53:13 -0800",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | On Sun, Jan 18, 2026 at 2:33 PM John Groves <john@jagalactic.com> wrote:
Reviewed-by: Joanne Koong <joannelkoong@gmail.com> | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 30 Jan 2026 15:13:20 -0800",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | On Fri, Jan 30, 2026 at 02:53:13PM -0800, Joanne Koong wrote:
This insertion ought to preserve FUSE_NOTIFY_CODE_MAX, right?
--D | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Fri, 30 Jan 2026 16:41:19 -0800",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | On Fri, Jan 30, 2026 at 4:41 PM Darrick J. Wong <djwong@kernel.org> wrote:
FUSE_NOTIFY_CODE_MAX was removed by Miklos in commit 0a0fdb98d16e3.
Thanks,
Joanne | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 30 Jan 2026 17:18:32 -0800",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | On Sun, Jan 18, 2026 at 10:36:02PM +0000, John Groves wrote:
Hi John,
I fired this all up and ran it. It got through all but it's last test
case before failing.
Three things appended:
1) the diff I applied to daxctl-famfs.sh to run the test
2) testlog.txt output of the test
3) RIP: 0010:is_free_buddy_page+0x39/0x60... | {
"author": "Alison Schofield <alison.schofield@intel.com>",
"date": "Mon, 9 Feb 2026 15:13:01 -0800",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | On 26/02/09 03:13PM, Alison Schofield wrote:
[snip]
Thank you Allison! I'm still working to reproduce the BUG you found (and
cover this in my jenkins automation), but I think I have the fix already:
when existing famfs mode (unbinding drivers/dax/fsdev.c), a
fsdev_clear_folio_state() call is needed. I've added that... | {
"author": "John Groves <John@groves.net>",
"date": "Wed, 11 Feb 2026 08:31:18 -0600",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | John Groves wrote:
[snip]
All of the above code is AFAICT exactly the same as the dev_dax driver.
Isn't there a way to make this common?
The rest of the common code is simple enough.
[snip]
I don't understand why this hunk is added here but then removed in a later
patch? Why can't this be placed below? ...
.... | {
"author": "Ira Weiny <ira.weiny@intel.com>",
"date": "Fri, 13 Feb 2026 15:05:38 -0600",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | John Groves wrote:
[snip]
WARN_ON_ONCE. But frankly I'm pretty sure this is impossible to hit given
the probe call, so best remove it. Also yall already used dev_dax->virt_addr
above. And will hand back a bad address to the caller. So...
EFAULT?
Ira
[snip] | {
"author": "Ira Weiny <ira.weiny@intel.com>",
"date": "Fri, 13 Feb 2026 15:23:15 -0600",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | John Groves wrote:
I thought this driver did not support mmap?
None of the above explains exactly why this code is needed. Rather it
just explains what it does.
I'm not 100% clear on why this is needed in the driver and why this is not
a layering violation which is going to bite us later?
Ira | {
"author": "Ira Weiny <ira.weiny@intel.com>",
"date": "Sat, 14 Feb 2026 10:10:15 -0600",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | On 26/02/13 03:05PM, Ira Weiny wrote:
dev_dax_probe() and fsdev_dax_probe() do indeed have some "same code" -
range validity checking and pgmap setup, from the top of probe through
the for loop above. After that they're different. Also, I just did a scan
and the probe function seems like the only remaining common c... | {
"author": "John Groves <John@groves.net>",
"date": "Tue, 17 Feb 2026 11:56:20 -0600",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | On 26/02/13 03:23PM, Ira Weiny wrote:
Good point - dropped it.
This feels like a judgment call, but I'm fine with it.
Changed to -EFAULT
Thanks Ira!
John | {
"author": "John Groves <John@groves.net>",
"date": "Tue, 17 Feb 2026 18:38:59 -0600",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | On 26/02/14 10:10AM, Ira Weiny wrote:
If a daxdev /dev/dax0.0 is in 'famfs' mode (bound to drivers/dax/fsdev.c),
and you open it and try to mmap - you can't - that's true.
This stuff is necessary to support mmap/read/write on famfs files.
I'll update the description to make it clear.
But basically: this is the stu... | {
"author": "John Groves <John@groves.net>",
"date": "Tue, 17 Feb 2026 18:49:59 -0600",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | On 1/18/26 3:32 PM, John Groves wrote:
Don't you need to hold the dev_dax->dev device lock in order to check the driver?
DJ | {
"author": "Dave Jiang <dave.jiang@intel.com>",
"date": "Thu, 19 Feb 2026 09:07:53 -0700",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | On 1/18/26 3:32 PM, John Groves wrote:
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
It's tiny enough that maybe you can just squash it with the commit that you are using it? | {
"author": "Dave Jiang <dave.jiang@intel.com>",
"date": "Thu, 19 Feb 2026 09:18:38 -0700",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | On 1/18/26 3:32 PM, John Groves wrote:
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
squash the defines with usage patch? | {
"author": "Dave Jiang <dave.jiang@intel.com>",
"date": "Thu, 19 Feb 2026 09:21:51 -0700",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | On 1/18/26 3:33 PM, John Groves wrote:
keep the return int on the same line?
Should do the variable declaration when you do the kzalloc(). That way you can avoid any potential use before check issues.
-ENOMEM?
DJ | {
"author": "Dave Jiang <dave.jiang@intel.com>",
"date": "Thu, 19 Feb 2026 10:12:18 -0700",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | On 1/18/26 3:33 PM, John Groves wrote:
declare when it gets allocated
Both checks for nextents can be -ERANGE?
I think you can do:
retain_and_null_ptr(meta);
FIELD_PREP()?
DJ | {
"author": "Dave Jiang <dave.jiang@intel.com>",
"date": "Thu, 19 Feb 2026 11:31:42 -0700",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is a coordinated patch submission for famfs (Fabric-Attached Memory
File System) across three repositories:
1. Linux kernel (cover + 19 patches) - dax fsdev driver + fuse/famfs
integration
2. libfuse (cover + 3 patches) - famfs protocol support for fuse servers
3. ndctl/daxctl (cover + 2 patches... | null | null | null | [PATCH BUNDLE v7] famfs: Fabric-Attached Memory File System | On 1/18/26 3:33 PM, John Groves wrote:
I think if you declare devlist with __free(), you can just return instead of having a goto.
DJ | {
"author": "Dave Jiang <dave.jiang@intel.com>",
"date": "Thu, 19 Feb 2026 11:51:14 -0700",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.