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 | 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:34 PM, John Groves wrote:
s/shard/share/?
"reduction in read amplification"?
s/poison and/poison, and/
DJ | {
"author": "Dave Jiang <dave.jiang@intel.com>",
"date": "Thu, 19 Feb 2026 14:39:32 -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:36 PM, John Groves wrote:
Wonder if a common bash function can be created for this and put in "common"
check_kmod_available()?
DJ | {
"author": "Dave Jiang <dave.jiang@intel.com>",
"date": "Thu, 19 Feb 2026 15:02:57 -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 | John Groves <john@jagalactic.com> writes:
I'm implementing something similar for guest_memfd and was going to
reuse __split_folio_to_order(). Would you consider using the
__split_folio_to_order() function?
I see that dax_folio_reset_order() needs to set f->share to 0 though,
which is a union with index, and __split_... | {
"author": "Ackerley Tng <ackerleytng@google.com>",
"date": "Mon, 23 Feb 2026 19:00:16 -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/19 11:31AM, Dave Jiang wrote:
Done, thanks!
Done, Thx
Ah, I didn't know that one!
Done
Another new one to me!
Done.
Thanks Dave!
[snip] | {
"author": "John Groves <John@groves.net>",
"date": "Wed, 25 Feb 2026 15:30: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 | On 26/02/19 02:39PM, Dave Jiang wrote:
Actually shard is correct here - talking about splitting data sets
into shards...
Good eye - thanks. Done.
Done, thanks!
John | {
"author": "John Groves <John@groves.net>",
"date": "Wed, 25 Feb 2026 18:29:17 -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/19 09:07AM, Dave Jiang wrote:
Derp. Thanks for catching that Dave!
I believe it's fixed for v8, which is probably coming early next week.
John
[snip] | {
"author": "John Groves <John@groves.net>",
"date": "Thu, 26 Feb 2026 17:20:43 -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 Sun, Jan 18, 2026 at 10:36:38PM +0000, John Groves wrote:
Make it clear that it is added in a separate patch. (and assume you
can drop the destructive part too.)
The precedence check (ram->famfs->devdax->unknown) now happens in multiple
places. How about adding a daxctl_dev_get_mode() helper to centralize that.
... | {
"author": "Alison Schofield <alison.schofield@intel.com>",
"date": "Thu, 26 Feb 2026 18:00:41 -0800",
"is_openbsd": false,
"thread_id": "0100019bd34040d9-0b6e9e4c-ecd4-464d-ab9d-88a251215442-000000@email.amazonses.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Not caching negative dentries can result in poor performance for
workloads that repeatedly look up non-existent paths. Each such
lookup triggers a full 9P transaction with the server, adding
unnecessary overhead.
A typical example is source compilation, where multiple cc1 processes
are spawned and repeatedly search fo... | null | null | null | [PATCH v3 1/4] 9p: Cache negative dentries for lookup performance | This patchset introduces several performance optimizations for the 9p
filesystem when used with cache=loose option (exclusive or read only
mounts). These improvements particularly target workloads with frequent
lookups of non-existent paths and repeated symlink resolutions.
The very state of the art benchmark consisti... | {
"author": "Remi Pommarel <repk@triplefau.lt>",
"date": "Fri, 27 Feb 2026 08:56:51 +0100",
"is_openbsd": false,
"thread_id": "59d4509e1015eb664bc2b5e59e1d5cf11ab95656.1772178819.git.repk@triplefau.lt.mbox.gz"
} |
lkml_critique | linux-fsdevel | Not caching negative dentries can result in poor performance for
workloads that repeatedly look up non-existent paths. Each such
lookup triggers a full 9P transaction with the server, adding
unnecessary overhead.
A typical example is source compilation, where multiple cc1 processes
are spawned and repeatedly search fo... | null | null | null | [PATCH v3 1/4] 9p: Cache negative dentries for lookup performance | Currently, when cache=loose is enabled, file reads are cached in the
page cache, but symlink reads are not. This patch allows the results
of p9_client_readlink() to be stored in the page cache, eliminating
the need for repeated 9P transactions on subsequent symlink accesses.
This change improves performance for worklo... | {
"author": "Remi Pommarel <repk@triplefau.lt>",
"date": "Fri, 27 Feb 2026 08:56:55 +0100",
"is_openbsd": false,
"thread_id": "59d4509e1015eb664bc2b5e59e1d5cf11ab95656.1772178819.git.repk@triplefau.lt.mbox.gz"
} |
lkml_critique | linux-fsdevel | Not caching negative dentries can result in poor performance for
workloads that repeatedly look up non-existent paths. Each such
lookup triggers a full 9P transaction with the server, adding
unnecessary overhead.
A typical example is source compilation, where multiple cc1 processes
are spawned and repeatedly search fo... | null | null | null | [PATCH v3 1/4] 9p: Cache negative dentries for lookup performance | Introduce a new mount option, ndentrycache, for v9fs that allows users
to specify how long negative dentries are retained in the cache. The
retention time can be set in milliseconds (e.g. ndentrycache=10000 for
a 10secs retention time), or negative entries can be kept until the
buffer cache management removes them by u... | {
"author": "Remi Pommarel <repk@triplefau.lt>",
"date": "Fri, 27 Feb 2026 08:56:53 +0100",
"is_openbsd": false,
"thread_id": "59d4509e1015eb664bc2b5e59e1d5cf11ab95656.1772178819.git.repk@triplefau.lt.mbox.gz"
} |
lkml_critique | linux-fsdevel | Not caching negative dentries can result in poor performance for
workloads that repeatedly look up non-existent paths. Each such
lookup triggers a full 9P transaction with the server, adding
unnecessary overhead.
A typical example is source compilation, where multiple cc1 processes
are spawned and repeatedly search fo... | null | null | null | [PATCH v3 1/4] 9p: Cache negative dentries for lookup performance | For cache=loose mounts, set the default negative dentry cache retention
time to 24 hours.
Signed-off-by: Remi Pommarel <repk@triplefau.lt>
---
fs/9p/v9fs.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/fs/9p/v9fs.c b/fs/9p/v9fs.c
index a26bd9070786..d14f6eda94d6 100644
--- a/fs/9p/v9fs.c
+++ b/fs/9p... | {
"author": "Remi Pommarel <repk@triplefau.lt>",
"date": "Fri, 27 Feb 2026 08:56:54 +0100",
"is_openbsd": false,
"thread_id": "59d4509e1015eb664bc2b5e59e1d5cf11ab95656.1772178819.git.repk@triplefau.lt.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Darrick J. Wong <djwong@kernel.org>
Filesystems should never provide a delayed allocation mapping to
writeback; they're supposed to allocate the space before replying.
This can lead to weird IO errors and crashes in the block layer if the
filesystem is being malicious, or if it hadn't set iomap->dev because
it's... | null | null | null | [PATCH] iomap: reject delalloc mappings during writeback | On Thu, Feb 26, 2026 at 10:00:58AM -0800, Darrick J. Wong wrote:
Maybe switch to to explicitly listing the acceptable types and rejecting
the rest instead?
diff --git a/fs/iomap/ioend.c b/fs/iomap/ioend.c
index e4d57cb969f1..2dd49677905f 100644
--- a/fs/iomap/ioend.c
+++ b/fs/iomap/ioend.c
@@ -169,17 +169,18 @@ ssize... | {
"author": "Christoph Hellwig <hch@infradead.org>",
"date": "Thu, 26 Feb 2026 13:29:37 -0800",
"is_openbsd": false,
"thread_id": "20260226233357.GG13853@frogsfrogsfrogs.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Darrick J. Wong <djwong@kernel.org>
Filesystems should never provide a delayed allocation mapping to
writeback; they're supposed to allocate the space before replying.
This can lead to weird IO errors and crashes in the block layer if the
filesystem is being malicious, or if it hadn't set iomap->dev because
it's... | null | null | null | [PATCH] iomap: reject delalloc mappings during writeback | On Thu, Feb 26, 2026 at 01:29:37PM -0800, Christoph Hellwig wrote:
Yeah, that's a better solution, particularly if we ever add a new
mapping type.
--D | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Thu, 26 Feb 2026 15:33:57 -0800",
"is_openbsd": false,
"thread_id": "20260226233357.GG13853@frogsfrogsfrogs.mbox.gz"
} |
lkml_critique | linux-fsdevel | Split the logic to see if a bio needs integrity metadata from
bio_integrity_prep into a reusable helper than can be called from
file system code.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin K. Petersen... | null | null | null | [PATCH 01/16] block: factor out a bio_integrity_action helper | Hi all,
this series adds support to generate and verify integrity information
(aka T10 PI) in the file system, instead of the automatic below the
covers support that is currently used.
There two reasons for this:
a) to increase the protection enveloped. Right now this is just a
minor step from the bottom of ... | {
"author": "Christoph Hellwig <hch@lst.de>",
"date": "Mon, 23 Feb 2026 05:20:00 -0800",
"is_openbsd": false,
"thread_id": "449fd474-0b61-42ff-afbe-56b728d69262@paragon-software.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Split the logic to see if a bio needs integrity metadata from
bio_integrity_prep into a reusable helper than can be called from
file system code.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin K. Petersen... | null | null | null | [PATCH 01/16] block: factor out a bio_integrity_action helper | Add a helper to set the seed and check flag based on useful defaults
from the profile.
Note that this includes a small behavior change, as we now only set the
seed if any action is set, which is fine as nothing will look at it
otherwise.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@... | {
"author": "Christoph Hellwig <hch@lst.de>",
"date": "Mon, 23 Feb 2026 05:20:02 -0800",
"is_openbsd": false,
"thread_id": "449fd474-0b61-42ff-afbe-56b728d69262@paragon-software.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Split the logic to see if a bio needs integrity metadata from
bio_integrity_prep into a reusable helper than can be called from
file system code.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin K. Petersen... | null | null | null | [PATCH 01/16] block: factor out a bio_integrity_action helper | Factor out a helper to see if the block device has an integrity checksum
from bdev_stable_writes so that it can be reused for other checks.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin K. Petersen <mart... | {
"author": "Christoph Hellwig <hch@lst.de>",
"date": "Mon, 23 Feb 2026 05:20:03 -0800",
"is_openbsd": false,
"thread_id": "449fd474-0b61-42ff-afbe-56b728d69262@paragon-software.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Split the logic to see if a bio needs integrity metadata from
bio_integrity_prep into a reusable helper than can be called from
file system code.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin K. Petersen... | null | null | null | [PATCH 01/16] block: factor out a bio_integrity_action helper | Return the status from verify instead of directly stashing it in the bio,
and rename the helpers to use the usual bio_ prefix for things operating
on a bio.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin ... | {
"author": "Christoph Hellwig <hch@lst.de>",
"date": "Mon, 23 Feb 2026 05:20:04 -0800",
"is_openbsd": false,
"thread_id": "449fd474-0b61-42ff-afbe-56b728d69262@paragon-software.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Split the logic to see if a bio needs integrity metadata from
bio_integrity_prep into a reusable helper than can be called from
file system code.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin K. Petersen... | null | null | null | [PATCH 01/16] block: factor out a bio_integrity_action helper | File systems that generate integrity will need this, so move it out
of the block private or blk-mq specific headers.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>... | {
"author": "Christoph Hellwig <hch@lst.de>",
"date": "Mon, 23 Feb 2026 05:20:05 -0800",
"is_openbsd": false,
"thread_id": "449fd474-0b61-42ff-afbe-56b728d69262@paragon-software.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Split the logic to see if a bio needs integrity metadata from
bio_integrity_prep into a reusable helper than can be called from
file system code.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin K. Petersen... | null | null | null | [PATCH 01/16] block: factor out a bio_integrity_action helper | Add a set of helpers for file system initiated integrity information.
These include mempool backed allocations and verifying based on a passed
in sector and size which is often available from file system completion
routines.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
R... | {
"author": "Christoph Hellwig <hch@lst.de>",
"date": "Mon, 23 Feb 2026 05:20:06 -0800",
"is_openbsd": false,
"thread_id": "449fd474-0b61-42ff-afbe-56b728d69262@paragon-software.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Split the logic to see if a bio needs integrity metadata from
bio_integrity_prep into a reusable helper than can be called from
file system code.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin K. Petersen... | null | null | null | [PATCH 01/16] block: factor out a bio_integrity_action helper | Allow the file system to limit the size processed in a single
bounce operation. This is needed when generating integrity data
so that the size of a single integrity segment can't overflow.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@... | {
"author": "Christoph Hellwig <hch@lst.de>",
"date": "Mon, 23 Feb 2026 05:20:07 -0800",
"is_openbsd": false,
"thread_id": "449fd474-0b61-42ff-afbe-56b728d69262@paragon-software.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Split the logic to see if a bio needs integrity metadata from
bio_integrity_prep into a reusable helper than can be called from
file system code.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin K. Petersen... | null | null | null | [PATCH 01/16] block: factor out a bio_integrity_action helper | Split out the logic to allocate a new bio and only keep the fast path
that adds more data to an existing bio in iomap_bio_read_folio_range.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
Tested-by: Anuj Gupta <anuj20.g@samsung.com>
---
fs/iomap/bio.c | 69 ++++++++++++... | {
"author": "Christoph Hellwig <hch@lst.de>",
"date": "Mon, 23 Feb 2026 05:20:08 -0800",
"is_openbsd": false,
"thread_id": "449fd474-0b61-42ff-afbe-56b728d69262@paragon-software.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Split the logic to see if a bio needs integrity metadata from
bio_integrity_prep into a reusable helper than can be called from
file system code.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin K. Petersen... | null | null | null | [PATCH 01/16] block: factor out a bio_integrity_action helper | This provides additional context for file systems.
Rename the fuse instance to match the method name while we're at it.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
Tested-by: Anuj Gupta <anuj20.g@samsung.com>
---
fs/fuse/file.c | 5 +++--
fs/iomap/bio.c ... | {
"author": "Christoph Hellwig <hch@lst.de>",
"date": "Mon, 23 Feb 2026 05:20:09 -0800",
"is_openbsd": false,
"thread_id": "449fd474-0b61-42ff-afbe-56b728d69262@paragon-software.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Split the logic to see if a bio needs integrity metadata from
bio_integrity_prep into a reusable helper than can be called from
file system code.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin K. Petersen... | null | null | null | [PATCH 01/16] block: factor out a bio_integrity_action helper | Move the NULL check into the callers to simplify the callees.
Fuse was missing this before, but has a constant read_ctx that is
never NULL or changed, so no change here either.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
Tested-by: Anuj Gupta <anuj20.g@samsung.com>... | {
"author": "Christoph Hellwig <hch@lst.de>",
"date": "Mon, 23 Feb 2026 05:20:10 -0800",
"is_openbsd": false,
"thread_id": "449fd474-0b61-42ff-afbe-56b728d69262@paragon-software.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Split the logic to see if a bio needs integrity metadata from
bio_integrity_prep into a reusable helper than can be called from
file system code.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin K. Petersen... | null | null | null | [PATCH 01/16] block: factor out a bio_integrity_action helper | File systems such as btrfs have additional operations with bios such as
verifying data checksums. Allow file systems to hook into submission
of the bio to allow for this processing by replacing the direct
submit_bio call in iomap_read_alloc_bio with a call into ->submit_read
and exporting iomap_read_alloc_bio. Also a... | {
"author": "Christoph Hellwig <hch@lst.de>",
"date": "Mon, 23 Feb 2026 05:20:11 -0800",
"is_openbsd": false,
"thread_id": "449fd474-0b61-42ff-afbe-56b728d69262@paragon-software.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Split the logic to see if a bio needs integrity metadata from
bio_integrity_prep into a reusable helper than can be called from
file system code.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin K. Petersen... | null | null | null | [PATCH 01/16] block: factor out a bio_integrity_action helper | ntfs3 copied the iomap code without attribution or talking to the
maintainers, to hook into the bio completion for (unexplained) zeroing.
Fix this by just overriding the bio completion handler in the submit
handler.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
fs/ntfs3/inode.c | 51 +++--------------------------... | {
"author": "Christoph Hellwig <hch@lst.de>",
"date": "Mon, 23 Feb 2026 05:20:12 -0800",
"is_openbsd": false,
"thread_id": "449fd474-0b61-42ff-afbe-56b728d69262@paragon-software.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Split the logic to see if a bio needs integrity metadata from
bio_integrity_prep into a reusable helper than can be called from
file system code.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin K. Petersen... | null | null | null | [PATCH 01/16] block: factor out a bio_integrity_action helper | Optionally allocate the bio from the bioset provided in
iomap_read_folio_ops. If no bioset is provided, fs_bio_set is still
used, which is the standard bioset for file systems.
Based on a patch from Goldwyn Rodrigues <rgoldwyn@suse.com>.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: "Darrick J. Wong" <d... | {
"author": "Christoph Hellwig <hch@lst.de>",
"date": "Mon, 23 Feb 2026 05:20:13 -0800",
"is_openbsd": false,
"thread_id": "449fd474-0b61-42ff-afbe-56b728d69262@paragon-software.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Split the logic to see if a bio needs integrity metadata from
bio_integrity_prep into a reusable helper than can be called from
file system code.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin K. Petersen... | null | null | null | [PATCH 01/16] block: factor out a bio_integrity_action helper | Support using the ioend structure to defer I/O completion for
buffered reads by calling into the buffered read I/O completion
handler from iomap_finish_ioend.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
Tested-by: Anuj Gupta <anuj20.g@samsung.com>
---
fs/iomap/bio.... | {
"author": "Christoph Hellwig <hch@lst.de>",
"date": "Mon, 23 Feb 2026 05:20:14 -0800",
"is_openbsd": false,
"thread_id": "449fd474-0b61-42ff-afbe-56b728d69262@paragon-software.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Split the logic to see if a bio needs integrity metadata from
bio_integrity_prep into a reusable helper than can be called from
file system code.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin K. Petersen... | null | null | null | [PATCH 01/16] block: factor out a bio_integrity_action helper | Add support for generating / verifying protection information in iomap.
This is done by hooking into the bio submission and then using the
generic PI helpers. Compared to just using the block layer auto PI
this extends the protection envelope and also prepares for eventually
passing through PI from userspace at least ... | {
"author": "Christoph Hellwig <hch@lst.de>",
"date": "Mon, 23 Feb 2026 05:20:15 -0800",
"is_openbsd": false,
"thread_id": "449fd474-0b61-42ff-afbe-56b728d69262@paragon-software.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Split the logic to see if a bio needs integrity metadata from
bio_integrity_prep into a reusable helper than can be called from
file system code.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin K. Petersen... | null | null | null | [PATCH 01/16] block: factor out a bio_integrity_action helper | Add support for generating / verifying protection information in the file
system. This is largely done by simply setting the IOMAP_F_INTEGRITY
flag and letting iomap do all of the work. XFS just has to ensure that
the data read completions for integrity data are run from user context.
For zoned writeback, XFS also h... | {
"author": "Christoph Hellwig <hch@lst.de>",
"date": "Mon, 23 Feb 2026 05:20:16 -0800",
"is_openbsd": false,
"thread_id": "449fd474-0b61-42ff-afbe-56b728d69262@paragon-software.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Split the logic to see if a bio needs integrity metadata from
bio_integrity_prep into a reusable helper than can be called from
file system code.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin K. Petersen... | null | null | null | [PATCH 01/16] block: factor out a bio_integrity_action helper | On Mon, Feb 23, 2026 at 05:20:12AM -0800, Christoph Hellwig wrote:
Well they /did/ attribute it...
...extremely poorly, by not recording their reasons for copy-pasting the
code.
Yeah, identical to iomap_bio_read_folio_range except for setting
bi_end_io.
Don't copy-paste stuff.
Reviewed-by: "Darrick J. Wong" <djwo... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 08:27:39 -0800",
"is_openbsd": false,
"thread_id": "449fd474-0b61-42ff-afbe-56b728d69262@paragon-software.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Split the logic to see if a bio needs integrity metadata from
bio_integrity_prep into a reusable helper than can be called from
file system code.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin K. Petersen... | null | null | null | [PATCH 01/16] block: factor out a bio_integrity_action helper | On 2/23/26 14:20, Christoph Hellwig wrote:
Hello,
Thanks for the note. The iomap helper was copied because
`iomap_bio_read_folio_range` is defined `static` in iomap/bio.c and thus
not available for reuse; that prevented using the exported helpers in this
tree.
If I’m mistaken, please let me know.
Regards,
Konstant... | {
"author": "Konstantin Komarov <almaz.alexandrovich@paragon-software.com>",
"date": "Fri, 27 Feb 2026 14:46:08 +0100",
"is_openbsd": false,
"thread_id": "449fd474-0b61-42ff-afbe-56b728d69262@paragon-software.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | [Fixed lsf-pc address typo]
On Mon, Feb 2, 2026 at 2:51 PM Miklos Szeredi <miklos@szeredi.hu> wrote:
All important topics which I am sure will be discussed on a FUSE BoF.
I think that at least one question of interest to the wider fs audience is
Can any of the above improvements be used to help phase out some
of th... | {
"author": "Amir Goldstein <amir73il@gmail.com>",
"date": "Mon, 2 Feb 2026 17:14:37 +0100",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Mon, 2 Feb 2026 at 17:14, Amir Goldstein <amir73il@gmail.com> wrote:
I see your point. Maybe the BPF one could be useful as a cross track
discussion, though I'm not sure the fuse side of the design is mature
enough for that. Joanne, you did some experiments with that, no?
I think the major show stopper is tha... | {
"author": "Miklos Szeredi <miklos@szeredi.hu>",
"date": "Tue, 3 Feb 2026 08:55:26 +0100",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Tue 03-02-26 08:55:26, Miklos Szeredi via Lsf-pc wrote:
There's some interest from people doing vfs maintenance work (as it has
potential to save their work) and it is actually a reasonable task for
someone wanting to get acquainted with filesystem development work. So I
think there are chances of some progress. Fo... | {
"author": "Jan Kara <jack@suse.cz>",
"date": "Tue, 3 Feb 2026 10:19:30 +0100",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Tue, Feb 3, 2026 at 11:15 AM Luis Henriques <luis@igalia.com> wrote:
We are likely going to do a FUSE BoF, likely Wed afternoon,
so we can have an internal schedule for that.
Restartability and stable FUSE handles is one of the requirements
to replace an existing fs if that fs is NFS exportrable.
Thanks,
Amir. | {
"author": "Amir Goldstein <amir73il@gmail.com>",
"date": "Tue, 3 Feb 2026 11:20:12 +0100",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Tue, Feb 3, 2026 at 10:19 AM Jan Kara <jack@suse.cz> wrote:
I think that the concept of a VFS emulator is wrong to apply here.
A VFS emulator would be needed for running the latest uptodate fs driver.
If we want to fork a kernel driver at a point in time and make it into
a FUSE server,
we need a one time conversio... | {
"author": "Amir Goldstein <amir73il@gmail.com>",
"date": "Tue, 3 Feb 2026 11:31:24 +0100",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Mon, Feb 2, 2026 at 2:51 PM Miklos Szeredi <miklos@szeredi.hu> wrote:
- Let server explicitly declare NFS export support
We could couple that with LOOKUP_HANDLE, because I think there are very few
servers out there that truly provide stable NFS handles with current
FUSE protocol.
Thanks,
Amir. | {
"author": "Amir Goldstein <amir73il@gmail.com>",
"date": "Tue, 3 Feb 2026 11:36:29 +0100",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Tue, Feb 03 2026, Amir Goldstein wrote:
Great, thanks Amir. So I'll just assume these topics will be pushed into
the BoF. It looks like it will be a very interesting afternoon! ;-)
Cheers,
--
Luís | {
"author": "Luis Henriques <luis@igalia.com>",
"date": "Tue, 03 Feb 2026 10:38:49 +0000",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Mon, Feb 02 2026, Amir Goldstein wrote:
I wonder if the topic I proposed separately (on restarting FUSE servers)
should also be merged into this list. It's already a very comprehensive
list, so I'm not sure it's worth having a separate topic if most of it
will (likely) be touched here already.
What do you think?... | {
"author": "Luis Henriques <luis@igalia.com>",
"date": "Tue, 03 Feb 2026 10:15:05 +0000",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On 26/02/02 02:51PM, Miklos Szeredi wrote:
I plan to attend, and have been on the fence about whether a proper famfs
session is needed. I'm open to ideas on that, but would certainly
participate in this sort of overview session too.
JG | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Tue, 3 Feb 2026 17:13:36 +0000",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Mon, Feb 2, 2026 at 11:55 PM Miklos Szeredi <miklos@szeredi.hu> wrote:
Two other items I'd like to add to the potential discussion list are:
* leveraging io-uring multishot for batching fuse writeback and
readahead requests, ie maximizing the throughput per roundtrip context
switch [1]
* settling how load distrib... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Wed, 4 Feb 2026 01:22:02 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Wed, Feb 4, 2026 at 10:22 AM Joanne Koong <joannelkoong@gmail.com> wrote:
I think that for phasing out unmaintained filesystems performance
is really the last concern if a concern at all (call it a nudge).
Yeh, this is a fun exercise. fat could be a good candidate.
I'd do it myself if I find the time.
If anyone s... | {
"author": "Amir Goldstein <amir73il@gmail.com>",
"date": "Wed, 4 Feb 2026 11:37:52 +0100",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Wed 04-02-26 01:22:02, Joanne Koong wrote:
I'm not sure which filesystems Amir had exactly in mind but in my opinion
FAT is used widely enough to not be a primary target of this effort. It
would be rather filesystems like (random selection) bfs, adfs, vboxfs,
minix, efs, freevxfs, etc. The user base of these is ver... | {
"author": "Jan Kara <jack@suse.cz>",
"date": "Wed, 4 Feb 2026 11:43:05 +0100",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Mon, Feb 02, 2026 at 02:51:04PM +0100, Miklos Szeredi wrote:
FYI, I took a semi-break from fuse-iomap for 7.0 because I was too busy
working on xfs_healer, but I was planning to repost the patchbomb with
many many cleanups and reorganizations (thanks Joanne!) as soon as
possible after Linus tags 7.0-rc1.
I don't t... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Wed, 4 Feb 2026 11:06:49 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Wed, Feb 04, 2026 at 11:06:49AM -0800, Darrick J. Wong wrote:
Just convince Bernd ... ;-)
This really sounds like a good topic for an afternoon and in person the
bandwith for passing ideas is higher.
I'd be really interested in what those architectural shifts are. It is
clearly a lot more than the passage above.
... | {
"author": "Horst Birthelmer <horst@birthelmer.de>",
"date": "Wed, 4 Feb 2026 20:38:27 +0100",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On 2/4/26 10:22, Joanne Koong wrote:
Coincidentally I looked into this today because we had totally
imbalanced queues when this was activated - slip through in the queue
assignment, should be fixed in our branches. v4 basically has all your
comment addressed, our branch(es) have 3 bug fixes now to what I thought
would... | {
"author": "Bernd Schubert <bernd@bsbernd.com>",
"date": "Wed, 4 Feb 2026 21:47:59 +0100",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On 2/4/26 20:06, Darrick J. Wong wrote:
To be honest, I'm rather lost with your patch bomb - in which order do I
need to review what? And what can be merged without?
Regarding libfuse patches - certainly helpful if you also post them
here, but I don't want to create PRs out of your series, which then
might fail the PR... | {
"author": "Bernd Schubert <bernd@bsbernd.com>",
"date": "Wed, 4 Feb 2026 21:58:51 +0100",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On 2026/2/5 03:06, Darrick J. Wong wrote:
...
Just a side note: As a filesystem for containers, I have to say here
again one of the goal of EROFS is to allow unprivileged non-root-ns
mounts for container users because again I've seen no on-disk layout
security risk especially for the uncompressed layout format and
c... | {
"author": "Gao Xiang <hsiangkao@linux.alibaba.com>",
"date": "Thu, 5 Feb 2026 06:50:28 +0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On 2026/2/5 03:06, Darrick J. Wong wrote:
...
For this part: as far as I can tell, no one NAKed vfs BPF hooks,
and I had the similar idea two years ago:
https://lore.kernel.org/r/CAOQ4uxjCebxGxkguAh9s4_Vg7QHM=oBoV0LUPZpb+0pcm3z1bw@mail.gmail.com
We have some fanotify BPF hook ideas, e.g. to make lazy pulling
more e... | {
"author": "Gao Xiang <hsiangkao@linux.alibaba.com>",
"date": "Thu, 5 Feb 2026 07:19:05 +0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On 26/02/04 11:06AM, Darrick J. Wong wrote:
[ ... ]
Um, *yeah*. Although a significant part of that time was on me, because
getting it ported into fuse was kinda hard, my users and I are hoping we
can get this upstreamed fairly soon now. I'm hoping that after the 6.19
merge window dust settles we can negotiate an... | {
"author": "=?UTF-8?Q?John_Groves?= <john@jagalactic.com>",
"date": "Thu, 5 Feb 2026 03:33:27 +0000",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Thu, Feb 5, 2026 at 4:33 AM John Groves <john@jagalactic.com> wrote:
I think that the work on famfs is setting an example, and I very much
hope it will be a good example, of how improving existing infrastructure
(FUSE) is a better contribution than adding another fs to the pile.
I acknowledge that doing the latter... | {
"author": "Amir Goldstein <amir73il@gmail.com>",
"date": "Thu, 5 Feb 2026 10:27:52 +0100",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Thu, Feb 05, 2026 at 06:50:28AM +0800, Gao Xiang wrote:
<nod> I haven't forgotten. For readonly root fses erofs is probably the
best we're going to get, and it's less clunky than fuse. There's less
of a firewall due to !microkernel but I'd wager that most immutable
distros will find erofs a good enough balance be... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Thu, 5 Feb 2026 21:38:35 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Wed, Feb 04, 2026 at 09:58:51PM +0100, Bernd Schubert wrote:
If there are any fixes they're usually at the beginning.
At the moment you actually /have/ merged everything that can be. :)
The rest relies on kernel patches that aren't upstream.
I can generate pull requests for the libfuse things, no problem. The
... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Thu, 5 Feb 2026 21:47:38 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Thu, Feb 05, 2026 at 10:27:52AM +0100, Amir Goldstein wrote:
I think we've all missed getting merged for 7.0 since 6.19 will be
released in 3 days. :/
(Granted most of the maintainers I know are /much/ less conservative
than I was about the schedule)
Yeah. Joanne and I spent a couple of days this week coprogram... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Thu, 5 Feb 2026 21:52:47 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Wed, Feb 04, 2026 at 11:43:05AM +0100, Jan Kara wrote:
OTOH the ESP and USB sticks needn't be high performance. <shrug>
But yeah, these ones in the long tail are probably good targets. Though
I think willy pointed out that the biggest barrier in his fs folio
conversions was that many of them aren't testable (e.... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Thu, 5 Feb 2026 22:09:22 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | Hi Darrick,
On 2026/2/6 13:38, Darrick J. Wong wrote:
Thanks, but I can't make decisions for every individual end user.
However, in my view, this approach is valuable for all container
users if they don't mind to try this approach (I'm building this
capabilities with several communities and people): they can achieve
... | {
"author": "Gao Xiang <hsiangkao@linux.alibaba.com>",
"date": "Fri, 6 Feb 2026 14:15:12 +0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Wed, Feb 04, 2026 at 01:22:02AM -0800, Joanne Koong wrote:
(Which we're working on :D)
Yes. That conversion turned out not to be too difficult, but the
resulting uapi is a little awkward because you have to pass the
/dev/fuse fd in one of the structs that you pass to the bpf syscall,
and then the bpf functions h... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Thu, 5 Feb 2026 22:26:54 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On 26/02/05 09:52PM, Darrick J. Wong wrote:
Doh - right you are...
I'd love to learn more about this; happy to do a call if that's a
good way to get me briefed.
I [generally but not specifically] understand how this could avoid
GET_FMAP, but not GET_DAXDEV.
But I'm not sure it could (or should) avoid dax_iomap_rw... | {
"author": "John Groves <john@groves.net>",
"date": "Fri, 6 Feb 2026 14:48:43 -0600",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Fri, Feb 6, 2026 at 12:48 PM John Groves <john@groves.net> wrote:
Hi John,
The conversation started [1] on Darrick's containerization patchset
about using bpf to a) avoid extra requests / context switching for
->iomap_begin and ->iomap_end calls and b) offload what would
otherwise have to be hard-coded kernel logi... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Fri, 6 Feb 2026 16:22:45 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Fri, Feb 6, 2026 at 4:22 PM Joanne Koong <joannelkoong@gmail.com> wrote:
I put together a quick prototype to test this out - this is what it
looks like with fuse having a generic iomap interface that supports
dax [1], and the famfs custom logic moved to a bpf program [2]. I
didn't change much, I just moved around y... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Wed, 11 Feb 2026 20:46:26 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Fri, Feb 06, 2026 at 02:48:43PM -0600, John Groves wrote:
fuse-iomap requires fuse servers to open block devices and register them
with the fuse_conn as a backing file. The kernel returns a magic cookie
that can then be passed back to the kernel in iomap_begin. This is
(AFAICT) similar to what fuse does w.r.t. pa... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Fri, 20 Feb 2026 15:59:10 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Wed, Feb 11, 2026 at 08:46:26PM -0800, Joanne Koong wrote:
The bpf maps that you've used to upload per-inode data into the kernel
is a /much/ cleaner method than custom-compiling C into BPF at runtime!
You can statically compile the BPF object code into the fuse server,
which means that (a) you can take advantage o... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Fri, 20 Feb 2026 16:37:56 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Fri, Feb 06, 2026 at 02:15:12PM +0800, Gao Xiang wrote:
<nod> I hope you succeed!
Oh yes, the policy question is a very large one; for a specific given
filesystem, you need to trust:
A> whatever user is asking to do the mount
B> the quality of the kernel or userspace drivers
C> the provenance of the filesystem... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Fri, 20 Feb 2026 16:47:52 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Sat, Feb 21, 2026 at 01:07:55AM -0500, Demi Marie Obenour wrote:
In principle it might work, though I have questions about the quality of
whatever's internally driving guestmount.
Do you know how exactly libguestfs/guestmount accesses (say) an XFS
filesystem? I'm curious because libxfs isn't a shared library, so
... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Fri, 20 Feb 2026 23:07:05 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Sat, Feb 21, 2026 at 05:16:25PM -0500, Demi Marie Obenour wrote:
/me tries out libguestfs and ... wow it's slow to start. It does seem
to provide the isolation of the fs parsing code that I want, but the
overheads are quite high. 500MB memory to mount a totally empty XFS
filesystem, and 350MB of disk space to cre... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 13:58:04 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | I propose a session where various topics of interest could be
discussed including but not limited to the below list
New features being proposed at various stages of readiness:
- fuse4fs: exporting the iomap interface to userspace
- famfs: export distributed memory
- zero copy for fuse-io-uring
- large folios
... | null | null | null | [LSF/MM/BPF TOPIC] Where is fuse going? API cleanup, restructuring
and more | On Fri, Feb 20, 2026 at 4:37 PM Darrick J. Wong <djwong@kernel.org> wrote:
I don't think this is an issue because bpf does dynamic btf-based
relocations (CO-RE) at load time [1]. On the target machine, when
libbpf loads the bpf object it will read the machine's btf and patch
any offsets in bytecode and load the fixed-... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Thu, 26 Feb 2026 12:21:43 -0800",
"is_openbsd": false,
"thread_id": "CAJnrk1ZJksW=uz1itdh+zoaQBo_XQ4ZSF13BSnZXMie5pBCvYA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Large folios can reduce per-page overhead and improve throughput for large buffered I/O, but enabling them in filesystems is not a mechanical page folio conversion. The core difficulty is preserving correctness and performance when a folio must maintain subrange state, while existing filesystem code paths and the ioma... | null | null | null | [LSF/MM/BPF TOPIC] Large folio support: iomap framework changes
versus filesystem-specific implementations | Maybe you catch on the wrong foot, but this pisses me off. I've been
telling you guys to please actually fricking try converting f2fs to
iomap, and it's been constantly ignored.
And arguments about "log structured filesystems" here are BS. iomap
has supported out of places writes for XFS since 2016, which is
right a... | {
"author": "Christoph Hellwig <hch@infradead.org>",
"date": "Fri, 20 Feb 2026 07:48:39 -0800",
"is_openbsd": false,
"thread_id": "CAGsJ_4zNvSYa+fyBVkt1eOqpMPGi0Wrckb+fxn8Pqt5erZbTfw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Large folios can reduce per-page overhead and improve throughput for large buffered I/O, but enabling them in filesystems is not a mechanical page folio conversion. The core difficulty is preserving correctness and performance when a folio must maintain subrange state, while existing filesystem code paths and the ioma... | null | null | null | [LSF/MM/BPF TOPIC] Large folio support: iomap framework changes
versus filesystem-specific implementations | On Fri 20-02-26 20:59:38, Nanzhe Zhao wrote:
Just for record: Ext4 does currently support large folios for buffered IO
(currently using buffer heads). We are in the process of converting the
buffered IO paths to iomap (Zhang Yi is working on that) and although they
do face some challenges with lock ordering (mostly du... | {
"author": "Jan Kara <jack@suse.cz>",
"date": "Fri, 20 Feb 2026 18:07:58 +0100",
"is_openbsd": false,
"thread_id": "CAGsJ_4zNvSYa+fyBVkt1eOqpMPGi0Wrckb+fxn8Pqt5erZbTfw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Large folios can reduce per-page overhead and improve throughput for large buffered I/O, but enabling them in filesystems is not a mechanical page folio conversion. The core difficulty is preserving correctness and performance when a folio must maintain subrange state, while existing filesystem code paths and the ioma... | null | null | null | [LSF/MM/BPF TOPIC] Large folio support: iomap framework changes
versus filesystem-specific implementations | On Fri, Feb 20, 2026 at 07:48:39AM -0800, Christoph Hellwig wrote:
Christoph isn't alone here. There's a consistent pattern of f2fs going
off and doing weird shit without talking to anyone else. A good start
would be f2fs maintainers actually coming to LSFMM, but a lot more design
decisions need to be cc'd to linux-... | {
"author": "Matthew Wilcox <willy@infradead.org>",
"date": "Fri, 20 Feb 2026 18:40:49 +0000",
"is_openbsd": false,
"thread_id": "CAGsJ_4zNvSYa+fyBVkt1eOqpMPGi0Wrckb+fxn8Pqt5erZbTfw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Large folios can reduce per-page overhead and improve throughput for large buffered I/O, but enabling them in filesystems is not a mechanical page folio conversion. The core difficulty is preserving correctness and performance when a folio must maintain subrange state, while existing filesystem code paths and the ioma... | null | null | null | [LSF/MM/BPF TOPIC] Large folio support: iomap framework changes
versus filesystem-specific implementations | 在 2026/2/20 23:29, Nanzhe Zhao 写道:
Please note that, btrfs chose this "native fs" way only because there
are a lot of blockage preventing us from going full iomap directly.
Our long term objective is to go full iomap, and Goldwyn is already
working on non-compressed buffered write path.
And I'm working on the compr... | {
"author": "Qu Wenruo <wqu@suse.com>",
"date": "Mon, 23 Feb 2026 19:04:55 +1030",
"is_openbsd": false,
"thread_id": "CAGsJ_4zNvSYa+fyBVkt1eOqpMPGi0Wrckb+fxn8Pqt5erZbTfw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Large folios can reduce per-page overhead and improve throughput for large buffered I/O, but enabling them in filesystems is not a mechanical page folio conversion. The core difficulty is preserving correctness and performance when a folio must maintain subrange state, while existing filesystem code paths and the ioma... | null | null | null | [LSF/MM/BPF TOPIC] Large folio support: iomap framework changes
versus filesystem-specific implementations | On Mon, Feb 23, 2026 at 07:04:55PM +1030, Qu Wenruo wrote:
I still think btrfs would benefit greatly from killing the async
submission workqueue, and I hope that the multiple writeback thread
work going on currently will help with this. I think you really should
talk to Kundan. | {
"author": "Christoph Hellwig <hch@infradead.org>",
"date": "Mon, 23 Feb 2026 05:06:26 -0800",
"is_openbsd": false,
"thread_id": "CAGsJ_4zNvSYa+fyBVkt1eOqpMPGi0Wrckb+fxn8Pqt5erZbTfw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Large folios can reduce per-page overhead and improve throughput for large buffered I/O, but enabling them in filesystems is not a mechanical page folio conversion. The core difficulty is preserving correctness and performance when a folio must maintain subrange state, while existing filesystem code paths and the ioma... | null | null | null | [LSF/MM/BPF TOPIC] Large folio support: iomap framework changes
versus filesystem-specific implementations | On 02/20, Matthew Wilcox wrote:
What's the benefit of supporting the large folio on the write path? And,
which other designs are you talking about?
I'm also getting the consistent pattern: 1) posting patches in f2fs for
production, 2) requested to post patches modifying the generic layer, 3)
posting the converted pat... | {
"author": "Jaegeuk Kim <jaegeuk@kernel.org>",
"date": "Mon, 23 Feb 2026 21:36:18 +0000",
"is_openbsd": false,
"thread_id": "CAGsJ_4zNvSYa+fyBVkt1eOqpMPGi0Wrckb+fxn8Pqt5erZbTfw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Large folios can reduce per-page overhead and improve throughput for large buffered I/O, but enabling them in filesystems is not a mechanical page folio conversion. The core difficulty is preserving correctness and performance when a folio must maintain subrange state, while existing filesystem code paths and the ioma... | null | null | null | [LSF/MM/BPF TOPIC] Large folio support: iomap framework changes
versus filesystem-specific implementations | 在 2026/2/23 23:36, Christoph Hellwig 写道:
That's for sure. Although without that workqueue, where should the
compression workload happen?
Even we kill async submission workqueue, we still want to take advantage
of multi-thread compression, just at a different timing (without locking
every involved folio).
Mind to... | {
"author": "Qu Wenruo <wqu@suse.com>",
"date": "Tue, 24 Feb 2026 08:23:35 +1030",
"is_openbsd": false,
"thread_id": "CAGsJ_4zNvSYa+fyBVkt1eOqpMPGi0Wrckb+fxn8Pqt5erZbTfw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Large folios can reduce per-page overhead and improve throughput for large buffered I/O, but enabling them in filesystems is not a mechanical page folio conversion. The core difficulty is preserving correctness and performance when a folio must maintain subrange state, while existing filesystem code paths and the ioma... | null | null | null | [LSF/MM/BPF TOPIC] Large folio support: iomap framework changes
versus filesystem-specific implementations | On Tue, Feb 24, 2026 at 08:23:35AM +1030, Qu Wenruo wrote:
In the additional writeback threads mentioned below.
Added. | {
"author": "Christoph Hellwig <hch@infradead.org>",
"date": "Tue, 24 Feb 2026 06:58:08 -0800",
"is_openbsd": false,
"thread_id": "CAGsJ_4zNvSYa+fyBVkt1eOqpMPGi0Wrckb+fxn8Pqt5erZbTfw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Large folios can reduce per-page overhead and improve throughput for large buffered I/O, but enabling them in filesystems is not a mechanical page folio conversion. The core difficulty is preserving correctness and performance when a folio must maintain subrange state, while existing filesystem code paths and the ioma... | null | null | null | [LSF/MM/BPF TOPIC] Large folio support: iomap framework changes
versus filesystem-specific implementations | On Tue, Feb 24, 2026 at 5:36 AM Jaegeuk Kim <jaegeuk@kernel.org> wrote:
It can sometimes be a bit tricky for the common layer and
filesystem-specific layers to coordinate smoothly. At times,
it can be somewhat frustrating.
Privately, I know how tough it was for Nanzhe to decide whether
to make changes in the iomap la... | {
"author": "Barry Song <21cnbao@gmail.com>",
"date": "Thu, 26 Feb 2026 18:13:01 +0800",
"is_openbsd": false,
"thread_id": "CAGsJ_4zNvSYa+fyBVkt1eOqpMPGi0Wrckb+fxn8Pqt5erZbTfw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Large folios can reduce per-page overhead and improve throughput for large buffered I/O, but enabling them in filesystems is not a mechanical page folio conversion. The core difficulty is preserving correctness and performance when a folio must maintain subrange state, while existing filesystem code paths and the ioma... | null | null | null | [LSF/MM/BPF TOPIC] Large folio support: iomap framework changes
versus filesystem-specific implementations | On 02/26, Barry Song wrote:
We don't have a plan to attend this year summit. But I'm open to have an offline
call to discuss about what we can do in f2fs, if you guys are interested in.
Let me know. | {
"author": "Jaegeuk Kim <jaegeuk@kernel.org>",
"date": "Fri, 27 Feb 2026 02:02:41 +0000",
"is_openbsd": false,
"thread_id": "CAGsJ_4zNvSYa+fyBVkt1eOqpMPGi0Wrckb+fxn8Pqt5erZbTfw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Large folios can reduce per-page overhead and improve throughput for large buffered I/O, but enabling them in filesystems is not a mechanical page folio conversion. The core difficulty is preserving correctness and performance when a folio must maintain subrange state, while existing filesystem code paths and the ioma... | null | null | null | [LSF/MM/BPF TOPIC] Large folio support: iomap framework changes
versus filesystem-specific implementations | On Fri, Feb 27, 2026 at 10:02 AM Jaegeuk Kim <jaegeuk@kernel.org> wrote:
It’s truly a shame, but I understand that you have prior commitments.
Many thanks for your willingness to have an offline call.
Absolutely, I’m very interested. I spoke with Nanzhe today, and he’ll
prepare documents and code to review with you... | {
"author": "Barry Song <21cnbao@gmail.com>",
"date": "Fri, 27 Feb 2026 10:43:49 +0800",
"is_openbsd": false,
"thread_id": "CAGsJ_4zNvSYa+fyBVkt1eOqpMPGi0Wrckb+fxn8Pqt5erZbTfw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Jim Harris <jim.harris@nvidia.com>
When O_CREAT is set, we don't need the lookup. The lookup doesn't
harm anything, but it's an extra FUSE operation that's not required.
Signed-off-by: Jim Harris <jim.harris@nvidia.com>
---
fs/fuse/dir.c | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
d... | null | null | null | [PATCH] fuse: skip lookup during atomic_open() when O_CREAT is set | Hi Jim,
On Fri, Feb 20, 2026 at 01:41:02PM -0700, Jim Harris wrote:
I have been looking at that code lately a lot since I was planning to
replace it with a compound.
I'm not entirely convinced that your proposal is the right direction.
I would involve O_EXCL as well, since that lookup could actually
help in that ca... | {
"author": "Horst Birthelmer <horst@birthelmer.de>",
"date": "Sat, 21 Feb 2026 16:19:39 +0100",
"is_openbsd": false,
"thread_id": "6D884659-21B7-438D-8323-477EA22ACD43@nvidia.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Jim Harris <jim.harris@nvidia.com>
When O_CREAT is set, we don't need the lookup. The lookup doesn't
harm anything, but it's an extra FUSE operation that's not required.
Signed-off-by: Jim Harris <jim.harris@nvidia.com>
---
fs/fuse/dir.c | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
d... | null | null | null | [PATCH] fuse: skip lookup during atomic_open() when O_CREAT is set | On Fri, 20 Feb 2026 at 21:41, Jim Harris <jim.harris@nvidia.com> wrote:
Now this is not necessarily true. Setting FMODE_CREATED in case of an
existing file will have the effect of not checking permissions to open
(think open(path, O_CREAT | O_RDWR, 0444)).
Sad fact is that the same thing could happen with current co... | {
"author": "Miklos Szeredi <miklos@szeredi.hu>",
"date": "Mon, 23 Feb 2026 15:57:05 +0100",
"is_openbsd": false,
"thread_id": "6D884659-21B7-438D-8323-477EA22ACD43@nvidia.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Jim Harris <jim.harris@nvidia.com>
When O_CREAT is set, we don't need the lookup. The lookup doesn't
harm anything, but it's an extra FUSE operation that's not required.
Signed-off-by: Jim Harris <jim.harris@nvidia.com>
---
fs/fuse/dir.c | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
d... | null | null | null | [PATCH] fuse: skip lookup during atomic_open() when O_CREAT is set | On Sat, 21 Feb 2026 at 16:19, Horst Birthelmer <horst@birthelmer.de> wrote:
Bernd had actual patches, that got sidetracked unfortunately:
https://lore.kernel.org/all/20231023183035.11035-1-bschubert@ddn.com/
Thanks,
Miklos | {
"author": "Miklos Szeredi <miklos@szeredi.hu>",
"date": "Mon, 23 Feb 2026 16:09:51 +0100",
"is_openbsd": false,
"thread_id": "6D884659-21B7-438D-8323-477EA22ACD43@nvidia.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Jim Harris <jim.harris@nvidia.com>
When O_CREAT is set, we don't need the lookup. The lookup doesn't
harm anything, but it's an extra FUSE operation that's not required.
Signed-off-by: Jim Harris <jim.harris@nvidia.com>
---
fs/fuse/dir.c | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
d... | null | null | null | [PATCH] fuse: skip lookup during atomic_open() when O_CREAT is set | On 2/23/26 16:09, Miklos Szeredi wrote:
After the discussion about LOOKUO_HANDLE my impression was actually that
we want to use compounds for the atomic open.
Thanks,
Bernd | {
"author": "Bernd Schubert <bernd@bsbernd.com>",
"date": "Mon, 23 Feb 2026 16:36:50 +0100",
"is_openbsd": false,
"thread_id": "6D884659-21B7-438D-8323-477EA22ACD43@nvidia.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Jim Harris <jim.harris@nvidia.com>
When O_CREAT is set, we don't need the lookup. The lookup doesn't
harm anything, but it's an extra FUSE operation that's not required.
Signed-off-by: Jim Harris <jim.harris@nvidia.com>
---
fs/fuse/dir.c | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
d... | null | null | null | [PATCH] fuse: skip lookup during atomic_open() when O_CREAT is set | On Mon, 23 Feb 2026 at 16:37, Bernd Schubert <bernd@bsbernd.com> wrote:
I think we want to introduce an atomic operation that does a lookup +
an optional mknod, lets call this LOOKUP_CREATE_FH, this would return
a flag indicating whether the file was created or if it existed prior
to the operation.
Then, instead of ... | {
"author": "Miklos Szeredi <miklos@szeredi.hu>",
"date": "Mon, 23 Feb 2026 16:53:33 +0100",
"is_openbsd": false,
"thread_id": "6D884659-21B7-438D-8323-477EA22ACD43@nvidia.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Jim Harris <jim.harris@nvidia.com>
When O_CREAT is set, we don't need the lookup. The lookup doesn't
harm anything, but it's an extra FUSE operation that's not required.
Signed-off-by: Jim Harris <jim.harris@nvidia.com>
---
fs/fuse/dir.c | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
d... | null | null | null | [PATCH] fuse: skip lookup during atomic_open() when O_CREAT is set | On 2/20/26 21:41, Jim Harris wrote:
Problem is that it is a change of behavior - it might cause issues for
some fuse server implementations that expect that a node-id was obtained
before open of an existing file is done.
Thanks,
Bernd | {
"author": "Bernd Schubert <bernd@bsbernd.com>",
"date": "Mon, 23 Feb 2026 17:41:21 +0100",
"is_openbsd": false,
"thread_id": "6D884659-21B7-438D-8323-477EA22ACD43@nvidia.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Jim Harris <jim.harris@nvidia.com>
When O_CREAT is set, we don't need the lookup. The lookup doesn't
harm anything, but it's an extra FUSE operation that's not required.
Signed-off-by: Jim Harris <jim.harris@nvidia.com>
---
fs/fuse/dir.c | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
d... | null | null | null | [PATCH] fuse: skip lookup during atomic_open() when O_CREAT is set | On Mon, Feb 23 2026, Miklos Szeredi wrote:
FWIW, what I've been doing is something slightly different. I have been
working on implementing MKOBJ_HANDLE+STATX+OPEN. And the plan was to rely
on the compound flags, leaving it to user-space to handle the atomicity
(e.g. MKOBJ_HANDLE would fail if O_EXCL was set).
I wa... | {
"author": "Luis Henriques <luis@igalia.com>",
"date": "Mon, 23 Feb 2026 16:43:06 +0000",
"is_openbsd": false,
"thread_id": "6D884659-21B7-438D-8323-477EA22ACD43@nvidia.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Jim Harris <jim.harris@nvidia.com>
When O_CREAT is set, we don't need the lookup. The lookup doesn't
harm anything, but it's an extra FUSE operation that's not required.
Signed-off-by: Jim Harris <jim.harris@nvidia.com>
---
fs/fuse/dir.c | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
d... | null | null | null | [PATCH] fuse: skip lookup during atomic_open() when O_CREAT is set | On 2/23/26 16:53, Miklos Szeredi wrote:
Fine with me, but I need to process a bit if we want to that lookup to
return attributes or if it should be LOOKUP_CREATE_FH + OPEN + GETATTR.
Currently in the wrong time zone to do that today and also not much time
in general this week.
Thanks,
Bernd | {
"author": "Bernd Schubert <bernd@bsbernd.com>",
"date": "Mon, 23 Feb 2026 17:48:50 +0100",
"is_openbsd": false,
"thread_id": "6D884659-21B7-438D-8323-477EA22ACD43@nvidia.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Jim Harris <jim.harris@nvidia.com>
When O_CREAT is set, we don't need the lookup. The lookup doesn't
harm anything, but it's an extra FUSE operation that's not required.
Signed-off-by: Jim Harris <jim.harris@nvidia.com>
---
fs/fuse/dir.c | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
d... | null | null | null | [PATCH] fuse: skip lookup during atomic_open() when O_CREAT is set | On Mon, Feb 23, 2026 at 04:53:33PM +0100, Miklos Szeredi wrote:
What is wrong with a compound doing LOOKUP + MKNOD + OPEN?
If the fuse server knows how to process that 'group' atomically
in one big step it will do the right thing,
if not, we will call those in series and sort out the data
in kernel afterwards.
If w... | {
"author": "Horst Birthelmer <horst@birthelmer.de>",
"date": "Mon, 23 Feb 2026 19:55:47 +0100",
"is_openbsd": false,
"thread_id": "6D884659-21B7-438D-8323-477EA22ACD43@nvidia.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Jim Harris <jim.harris@nvidia.com>
When O_CREAT is set, we don't need the lookup. The lookup doesn't
harm anything, but it's an extra FUSE operation that's not required.
Signed-off-by: Jim Harris <jim.harris@nvidia.com>
---
fs/fuse/dir.c | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
d... | null | null | null | [PATCH] fuse: skip lookup during atomic_open() when O_CREAT is set | On Mon, 23 Feb 2026 at 19:55, Horst Birthelmer <horst@birthelmer.de> wrote:
Okay, I won't stop you experimenting.
My thinking is that it's simpler as a separate op (dir handle and name
are the same for LOOKUP and MKNOD). But adding this special "stop if
error or non-regular, else skip create if positive" dependenc... | {
"author": "Miklos Szeredi <miklos@szeredi.hu>",
"date": "Tue, 24 Feb 2026 16:33:32 +0100",
"is_openbsd": false,
"thread_id": "6D884659-21B7-438D-8323-477EA22ACD43@nvidia.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Jim Harris <jim.harris@nvidia.com>
When O_CREAT is set, we don't need the lookup. The lookup doesn't
harm anything, but it's an extra FUSE operation that's not required.
Signed-off-by: Jim Harris <jim.harris@nvidia.com>
---
fs/fuse/dir.c | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
d... | null | null | null | [PATCH] fuse: skip lookup during atomic_open() when O_CREAT is set | Thanks for the feedback everyone. Sounds like compounds will be the way forward to optimize this path, once they are ready.
Do we think compounds will be land for 7.1? Or later?
Best regards,
Jim | {
"author": "Jim Harris <jiharris@nvidia.com>",
"date": "Thu, 26 Feb 2026 23:11:22 +0000",
"is_openbsd": false,
"thread_id": "6D884659-21B7-438D-8323-477EA22ACD43@nvidia.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Jim Harris <jim.harris@nvidia.com>
When O_CREAT is set, we don't need the lookup. The lookup doesn't
harm anything, but it's an extra FUSE operation that's not required.
Signed-off-by: Jim Harris <jim.harris@nvidia.com>
---
fs/fuse/dir.c | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
d... | null | null | null | [PATCH] fuse: skip lookup during atomic_open() when O_CREAT is set | On Thu, Feb 26, 2026 at 11:11:22PM +0000, Jim Harris wrote:
I honestly have no idea. I'm going as fast as I can.
BTW, the post you are responding to, wasn't meant to reject the patch IMHO, but the change in behavior could actually
become a real problem.
I have the same fear for the compound of open+getattr, which act... | {
"author": "Horst Birthelmer <horst@birthelmer.de>",
"date": "Fri, 27 Feb 2026 08:59:11 +0100",
"is_openbsd": false,
"thread_id": "6D884659-21B7-438D-8323-477EA22ACD43@nvidia.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
When an NFS server exports a filesystem and clients hold NFSv4 state
(opens, locks, delegations), unmounting the underlying filesystem
fails with EBUSY. The /proc/fs/nfsd/unlock_fs interface exists for
administrators to manually revoke state before retrying the unmount,
but t... | null | null | null | [PATCH v3 0/3] Automatic NFSv4 state revocation on filesystem unmount | From: Chuck Lever <chuck.lever@oracle.com>
Kernel subsystems occasionally need notification when a filesystem
is unmounted. Until now, the only mechanism available is the fs_pin
infrastructure, which has limited adoption (only BSD process
accounting uses it) and VFS maintainers consider it deprecated.
Add an SRCU not... | {
"author": "Chuck Lever <cel@kernel.org>",
"date": "Tue, 24 Feb 2026 11:39:06 -0500",
"is_openbsd": false,
"thread_id": "3cff098e-74a8-4111-babb-9c13c7ba2344@kernel.org.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
When an NFS server exports a filesystem and clients hold NFSv4 state
(opens, locks, delegations), unmounting the underlying filesystem
fails with EBUSY. The /proc/fs/nfsd/unlock_fs interface exists for
administrators to manually revoke state before retrying the unmount,
but t... | null | null | null | [PATCH v3 0/3] Automatic NFSv4 state revocation on filesystem unmount | From: Chuck Lever <chuck.lever@oracle.com>
When an NFS server's local filesystem is unmounted while NFS clients
are still accessing it, NFSv4 state holds files open which pins the
filesystem, preventing unmount.
Previously, administrators had to manually revoke state via
/proc/fs/nfsd/unlock_fs before a formerly expo... | {
"author": "Chuck Lever <cel@kernel.org>",
"date": "Tue, 24 Feb 2026 11:39:07 -0500",
"is_openbsd": false,
"thread_id": "3cff098e-74a8-4111-babb-9c13c7ba2344@kernel.org.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
When an NFS server exports a filesystem and clients hold NFSv4 state
(opens, locks, delegations), unmounting the underlying filesystem
fails with EBUSY. The /proc/fs/nfsd/unlock_fs interface exists for
administrators to manually revoke state before retrying the unmount,
but t... | null | null | null | [PATCH v3 0/3] Automatic NFSv4 state revocation on filesystem unmount | From: Chuck Lever <chuck.lever@oracle.com>
When a filesystem is unmounted while NFS is exporting it, the
unmount can fail with EBUSY even after NFSv4 state has been revoked.
This occurs because the nfsd_file cache holds open NFSv2/3 file
handles that pin the filesystem.
Extend the mechanism that revokes NFSv4 state o... | {
"author": "Chuck Lever <cel@kernel.org>",
"date": "Tue, 24 Feb 2026 11:39:08 -0500",
"is_openbsd": false,
"thread_id": "3cff098e-74a8-4111-babb-9c13c7ba2344@kernel.org.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
When an NFS server exports a filesystem and clients hold NFSv4 state
(opens, locks, delegations), unmounting the underlying filesystem
fails with EBUSY. The /proc/fs/nfsd/unlock_fs interface exists for
administrators to manually revoke state before retrying the unmount,
but t... | null | null | null | [PATCH v3 0/3] Automatic NFSv4 state revocation on filesystem unmount | On Tue, Feb 24, 2026 at 11:39:05AM -0500, Chuck Lever wrote:
So anyone can force that just with unshare -U -m date? Creates
a new namespace, populated by clones of all mounts you see, runs
date(1) in that, then exits, with namespace dissolved. At that
point all cloned mounts are released, each triggering your notifi... | {
"author": "Al Viro <viro@zeniv.linux.org.uk>",
"date": "Tue, 24 Feb 2026 17:14:24 +0000",
"is_openbsd": false,
"thread_id": "3cff098e-74a8-4111-babb-9c13c7ba2344@kernel.org.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
When an NFS server exports a filesystem and clients hold NFSv4 state
(opens, locks, delegations), unmounting the underlying filesystem
fails with EBUSY. The /proc/fs/nfsd/unlock_fs interface exists for
administrators to manually revoke state before retrying the unmount,
but t... | null | null | null | [PATCH v3 0/3] Automatic NFSv4 state revocation on filesystem unmount | On Tue, Feb 24, 2026 at 11:39:06AM -0500, Chuck Lever wrote:
What I don't understand is why you need this per-mount especially
because you say above "when a filesystem is mounted. Could you explain
this in some more details, please?
Also this should take namespaces into account somehow, right? As Al
correctly observe... | {
"author": "Christian Brauner <brauner@kernel.org>",
"date": "Thu, 26 Feb 2026 09:48:24 +0100",
"is_openbsd": false,
"thread_id": "3cff098e-74a8-4111-babb-9c13c7ba2344@kernel.org.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
When an NFS server exports a filesystem and clients hold NFSv4 state
(opens, locks, delegations), unmounting the underlying filesystem
fails with EBUSY. The /proc/fs/nfsd/unlock_fs interface exists for
administrators to manually revoke state before retrying the unmount,
but t... | null | null | null | [PATCH v3 0/3] Automatic NFSv4 state revocation on filesystem unmount | On Thu, Feb 26, 2026 at 9:48 AM Christian Brauner <brauner@kernel.org> wrote:
Did you see commit 74bd284537b34 ("fsnotify: Shutdown fsnotify
before destroying sb's dcache")?
Does it make the fsnotify_sb_delete() hook an appropriate place
for this cleanup?
We could send an FS_UNMOUNT event on sb, the same way as we s... | {
"author": "Amir Goldstein <amir73il@gmail.com>",
"date": "Thu, 26 Feb 2026 11:52:14 +0100",
"is_openbsd": false,
"thread_id": "3cff098e-74a8-4111-babb-9c13c7ba2344@kernel.org.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
When an NFS server exports a filesystem and clients hold NFSv4 state
(opens, locks, delegations), unmounting the underlying filesystem
fails with EBUSY. The /proc/fs/nfsd/unlock_fs interface exists for
administrators to manually revoke state before retrying the unmount,
but t... | null | null | null | [PATCH v3 0/3] Automatic NFSv4 state revocation on filesystem unmount | On 2/26/26 5:52 AM, Amir Goldstein wrote:
I agree with Al's earlier comment and have added some protection there
for the next revision of the series.
There isn't much required here aside from getting a synchronous notice
that the final file system unmount is going on. I'm happy to try
whatever mechanism VFS maintai... | {
"author": "Chuck Lever <cel@kernel.org>",
"date": "Thu, 26 Feb 2026 08:27:00 -0500",
"is_openbsd": false,
"thread_id": "3cff098e-74a8-4111-babb-9c13c7ba2344@kernel.org.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
When an NFS server exports a filesystem and clients hold NFSv4 state
(opens, locks, delegations), unmounting the underlying filesystem
fails with EBUSY. The /proc/fs/nfsd/unlock_fs interface exists for
administrators to manually revoke state before retrying the unmount,
but t... | null | null | null | [PATCH v3 0/3] Automatic NFSv4 state revocation on filesystem unmount | On Thu 26-02-26 08:27:00, Chuck Lever wrote:
Yeah, then as Amir writes placing a mark with FS_UNMOUNT event on the
export root path and handling the event in
nfsd_file_fsnotify_handle_event() should do what you need?
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR | {
"author": "Jan Kara <jack@suse.cz>",
"date": "Thu, 26 Feb 2026 14:32:54 +0100",
"is_openbsd": false,
"thread_id": "3cff098e-74a8-4111-babb-9c13c7ba2344@kernel.org.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Chuck Lever <chuck.lever@oracle.com>
When an NFS server exports a filesystem and clients hold NFSv4 state
(opens, locks, delegations), unmounting the underlying filesystem
fails with EBUSY. The /proc/fs/nfsd/unlock_fs interface exists for
administrators to manually revoke state before retrying the unmount,
but t... | null | null | null | [PATCH v3 0/3] Automatic NFSv4 state revocation on filesystem unmount | On 2/26/26 8:32 AM, Jan Kara wrote:
Turns out FS_UNMOUNT doesn't do what I need.
1/3 here has a fatal flaw: the SRCU notifier does not fire until all
files on the mount are closed. The problem is that NFSD holds files
open when there is outstanding NFSv4 state. So the SRCU notifier will
never fire, on umount, to rele... | {
"author": "Chuck Lever <cel@kernel.org>",
"date": "Fri, 27 Feb 2026 10:10:17 -0500",
"is_openbsd": false,
"thread_id": "3cff098e-74a8-4111-babb-9c13c7ba2344@kernel.org.mbox.gz"
} |
lkml_critique | linux-fsdevel | Hi,
syzbot reported an issue with corrupted HFS+ images where the b-tree
allocation bitmap indicates that the header node (Node 0) is free. Node 0
must always be allocated as it contains the b-tree header record and the
allocation bitmap itself. Violating this invariant leads to allocator
corruption, which cascades in... | null | null | null | [PATCH v4 0/2] hfsplus: validate btree bitmap during mount and handle corruption gracefully | In HFS+ b-trees, the node allocation bitmap is stored across multiple
records. The first chunk resides in the b-tree Header Node at record
index 2, while all subsequent chunks are stored in dedicated Map Nodes
at record index 0.
This structural quirk forces callers like hfs_bmap_alloc() to duplicate
boilerplate code t... | {
"author": "Shardul Bankar <shardulsb08@gmail.com>",
"date": "Thu, 26 Feb 2026 14:42:34 +0530",
"is_openbsd": false,
"thread_id": "66941e77b76d1930a759a843783f1c68bb3089a8.camel@ibm.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Hi,
syzbot reported an issue with corrupted HFS+ images where the b-tree
allocation bitmap indicates that the header node (Node 0) is free. Node 0
must always be allocated as it contains the b-tree header record and the
allocation bitmap itself. Violating this invariant leads to allocator
corruption, which cascades in... | null | null | null | [PATCH v4 0/2] hfsplus: validate btree bitmap during mount and handle corruption gracefully | Syzkaller reported an issue with corrupted HFS+ images where the b-tree
allocation bitmap indicates that the header node (Node 0) is free. Node 0
must always be allocated as it contains the b-tree header record and the
allocation bitmap itself. Violating this invariant leads to allocator
corruption, which can cascade i... | {
"author": "Shardul Bankar <shardulsb08@gmail.com>",
"date": "Thu, 26 Feb 2026 14:42:35 +0530",
"is_openbsd": false,
"thread_id": "66941e77b76d1930a759a843783f1c68bb3089a8.camel@ibm.com.mbox.gz"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.