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 the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
In iomap mode, we trust the kernel to cache file attributes, because it
is critical to keep all of the file IO permissions checking in the
kernel as part of keeping all the file IO paths in the kernel.
Therefore, increase the attribute timeout to 30 seconds to reduce the
numbe... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:43:53 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
Cache the iomaps we generate in the kernel for better performance.
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
---
fuse4fs/fuse4fs.c | 31 +++++++++++++++++++++++++++++++
misc/fuse2fs.c | 30 ++++++++++++++++++++++++++++++
2 files changed, 61 insertions(+)
... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:44:09 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
Update the iomap config functions to handle the new iomap mapping cache
size restriction knob.
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
---
fuse4fs/fuse4fs.c | 9 ++++++---
misc/fuse2fs.c | 6 ++++--
2 files changed, 10 insertions(+), 5 deletions(-)
di... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:44:24 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
Now that iomap functionality is complete, enable this for users.
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
---
fuse4fs/fuse4fs.c | 4 ----
misc/fuse2fs.c | 4 ----
2 files changed, 8 deletions(-)
diff --git a/fuse4fs/fuse4fs.c b/fuse4fs/fuse4fs.c
index ... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:44:40 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
Start creating a caching IO manager so that we can have better caching
of metadata blocks in fuse2fs. For now it's just a passthrough cache.
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
---
lib/support/iocache.h | 17 +++
lib/ext2fs/io_manager.c | 3
lib/sup... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:44:56 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
Wire up buffer caching into our new caching IO manager.
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
---
lib/support/iocache.c | 483 +++++++++++++++++++++++++++++++++++++++++++++++--
1 file changed, 461 insertions(+), 22 deletions(-)
diff --git a/lib/support/ioca... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:45:11 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
If a buffer is hot enough to survive more than 50 access without being
reclaimed, bump its priority to the next MRU so it sticks around longer.
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
---
lib/support/cache.h | 1 +
lib/support/cache.c | 16 +++++++++++++... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:45:27 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
Enable the new dynamic iocache I/O manager in the fuse server, and turn
off all the other cache control.
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
---
fuse4fs/Makefile.in | 3 ++-
fuse4fs/fuse4fs.c | 4 +++-
misc/Makefile.in | 4 +++-
misc/fuse2fs.c ... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:45:42 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
Increase the internal inode cache size. Does this improve performance
any?
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
---
fuse4fs/fuse4fs.c | 4 ++++
misc/fuse2fs.c | 4 ++++
2 files changed, 8 insertions(+)
diff --git a/fuse4fs/fuse4fs.c b/fuse4fs/fuse... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:45:58 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
Use our new cache code to improve the ondisk inode cache inside
libext2fs. Oops, list.h duplication, and libext2fs needs to link
against libsupport now.
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
---
lib/ext2fs/ext2fsP.h | 13 ++-
debugfs/Makefile.in | ... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:46:14 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
The MMP code wants to be able to read and write the MMP block directly
to storage so that the pagecache does not get in the way. This is
critical for correct operation of MMP, because it is guarding against
two cluster nodes trying to change the filesystem at the same time.
... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:46:29 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
Make it possible to run fuse4fs as a safe systemd service, wherein the
fuse server only has access to the fds that we pass in.
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
---
MCONFIG.in | 1
configure | 135 +++++++++++++++++++... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:46:45 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
When in fuse service mode, set the process title so that we can identify
fuse servers by mount arguments. When the service ends, amend the title
again to say that we're cleaning up. This is done to make ps aux a bit
more communicative as to what is going on.
Signed-off-by: ... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:47:01 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
Try to speed up the first access to a file by upserting the first
file space mapping to the kernel at open time.
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
---
fuse4fs/fuse4fs.c | 33 ++++++++++++++++++++++++++++++++-
1 file changed, 32 insertions(+), 1 deletion(... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:47:16 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
If we're running as an unprivileged iomap fuse server, we must ask the
kernel to set the blocksize of the block device.
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
---
fuse4fs/fuse4fs.c | 41 +++++++++++++++++++++++++++++++----------
1 file changed, 31 insertions(... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:47:32 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
When requesting a file, ask the fuservicemount program to transform an
open regular file into a loop device for us, so that we can use iomap
even when the filesystem is actually an image file.
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
---
fuse4fs/fuse4fs.c | 3 ... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:47:48 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
Normally, the libext2fs MMP code open()s a complete separate file
descriptor to read and write the MMP block so that it can have its own
private open file with its own access mode and file position. However,
if the unixfd IO manager is in use, it will reuse the io channel, wh... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:48:03 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
Update the Debian packaging code so that we can create fuse4fs service
containers.
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
---
debian/e2fsprogs.install | 7 ++++++-
debian/fuse4fs.install | 3 +++
debian/rules | 3 +++
3 files changed, 12 ... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:48:19 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
Create some monitoring code that will sit in the background and watch
for resource pressure stalls and call some sort of handler when this
happens. This will be useful for shrinking the buffer cache when memory
gets tight.
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:48:35 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
Use the pressure stall indicator library that we added in the previous
patch to make it so that we only shrink the cache when there's memory
pressure.
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
---
fuse4fs/Makefile.in | 2 +
fuse4fs/fuse4fs.c | 84 ++++++++++... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:48:50 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
Ask the fuse filesystem service mount helper to open the memory pressure
stall files because we cannot open them ourselves.
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
---
lib/support/psi.h | 9 +++++++
fuse4fs/fuse4fs.c | 71 +++++++++++++++++++++++++++++++++++... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:49:06 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
Flush dirty metadata out to disk periodically like the kernel, to reduce
the potential for data loss if userspace doesn't explicitly fsync.
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
---
fuse4fs/fuse4fs.c | 112 +++++++++++++++++++++++++++++++++++++++++++++++++----... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:49:21 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
Enhance fuse4fs to report rogue results from FIEMAP to prove that iomap
bpf actually works. This patch employs dynamic compilation of the bpf
program so that the filesystem can tailor the bpf code to the needs of
the filesystem it's serving.
Signed-off-by: "Darrick J. Wong" ... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:49:37 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
Continue our demonstration of fuse iomap bpf by enabling the test
program to update the iomap cache.
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
---
fuse4fs/fuse4fs.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/fuse4fs/fuse4fs.c b/fuse4fs/fuse... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:49:53 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | From: Darrick J. Wong <djwong@kernel.org>
Adjust the test program to deal with fuse_bpf_inode.
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
---
fuse4fs/fuse4fs.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/fuse4fs/fuse4fs.c b/fuse4fs/fuse4fs.c
index b3c5d571d52448..09ffd93c7... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Mon, 23 Feb 2026 15:50:08 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | On Mon, Feb 23, 2026 at 03:06:50PM -0800, Darrick J. Wong wrote:
This looks good to me. Trivial fix for an annoying problem.
Reviewed-by: Horst Birthelmer <hbirthelmer@ddn.com> | {
"author": "Horst Birthelmer <horst@birthelmer.de>",
"date": "Tue, 24 Feb 2026 09:36:38 +0100",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | I still haven't gone through the whole patch blizzard but I had a
general question here: we don't give ATOMIC guarantees to buffered IO,
so I am wondering how we give that here. For example, we might mix
atomic and non atomic buffered IO during writeback. Am I missing some
implementation detail that makes it possible h... | {
"author": "\"Pankaj Raghav (Samsung)\" <pankaj.raghav@linux.dev>",
"date": "Tue, 24 Feb 2026 12:58:31 +0000",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | On Mon, Feb 23, 2026 at 03:07:53PM -0800, Darrick J. Wong wrote:
Maybe move up IOMAP_DIO_NO_INVALIDATE to avoid unused bits?
Otherwise this looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de> | {
"author": "Christoph Hellwig <hch@lst.de>",
"date": "Tue, 24 Feb 2026 15:00:30 +0100",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | On Mon, Feb 23, 2026 at 03:08:08PM -0800, Darrick J. Wong wrote:
That sounds pretty sketchy. How do you make sure that is safe vs
memory reclaim deadlocks? Does someone really need this feature? | {
"author": "Christoph Hellwig <hch@lst.de>",
"date": "Tue, 24 Feb 2026 15:01:18 +0100",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | On Tue, Feb 24, 2026 at 03:00:30PM +0100, Christoph Hellwig wrote:
Done, and thanks for the review!
--D | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Tue, 24 Feb 2026 11:17:19 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | On Tue, Feb 24, 2026 at 03:01:18PM +0100, Christoph Hellwig wrote:
Err, which part is sketchy, specifically? This patch that adjusts stuff
in fs/iomap/, or the (much later) patch to fuse-iomap?
If it's the second part (activating swapfiles via fuse-iomap) then I'll
state that fuse-iomap swapfiles work mostly the sam... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Tue, 24 Feb 2026 11:26:53 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | On Tue, Feb 24, 2026 at 12:58:31PM +0000, Pankaj Raghav (Samsung) wrote:
Oh, we don't. generic_atomic_write_valid rejects !IOCB_DIRECT iocbs.
<nod> Now that y'all have an lsf thread on this, I agree that not
supporting buffered writes in fuse-iomap should be more explicit.
if (iocb->ki_flags & IOCB_ATOMIC)
retu... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Tue, 24 Feb 2026 11:30:05 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | On Mon, Feb 23, 2026 at 3:06 PM Darrick J. Wong <djwong@kernel.org> wrote:
Overall LGTM, left a few comments below
Reviewed-by: Joanne Koong <joannelkoong@gmail.com>
nit: /* */ comment style
I don't think you meant to add this?
I think you meant "don't wait" for them?
nit: imo the "because the fuse server mus... | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Tue, 24 Feb 2026 11:33:12 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | On Tue, Feb 24, 2026 at 11:33:12AM -0800, Joanne Koong wrote:
Thanks!
I'm very confused by the comment style in this header file. Some of
them look like kerneldoc comments (albeit not documenting the sole
parameter), but others are just regular C comments.
<shrug> I sorta dislike kerneldoc's fussiness so I'll chan... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Tue, 24 Feb 2026 11:57:28 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | On Tue, Feb 24, 2026 at 11:57 AM Darrick J. Wong <djwong@kernel.org> wrote:
Oh I see your confusion now. Yeah the comment styles in this .h file
are kind of all over the place. Most of the functions don't even have
comments.
This sounds a lot better to me.
Thanks,
Joanne | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Tue, 24 Feb 2026 12:03:44 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | On Mon, Feb 23, 2026 at 3:06 PM Darrick J. Wong <djwong@kernel.org> wrote:
Makes sense to me.
Reviewed-by: Joanne Koong <joannelkoong@gmail.com> | {
"author": "Joanne Koong <joannelkoong@gmail.com>",
"date": "Tue, 24 Feb 2026 12:09:27 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | Ah, that is true. I was secretly hoping you added support for buffered
IO atomics ;)
Yeah. This looks more explicit. Of course this change does not warrant a
new series as it is not changing anything functionally. If you plan to
send a new series anyway, then this could be folded in.
--
Pankaj | {
"author": "\"Pankaj Raghav (Samsung)\" <pankaj.raghav@linux.dev>",
"date": "Tue, 24 Feb 2026 21:18:28 +0000",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | On Tue, Feb 24, 2026 at 11:26:53AM -0800, Darrick J. Wong wrote:
The concept of swapping to fuse.
Eww, I didn't know people were already trying to support swap to fuse. | {
"author": "Christoph Hellwig <hch@lst.de>",
"date": "Wed, 25 Feb 2026 15:16:39 +0100",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | On Wed, Feb 25, 2026 at 03:16:39PM +0100, Christoph Hellwig wrote:
It was merged in the kernel via commit b2d2272fae1e1d ("[PATCH] fuse:
add bmap support"), which was 2.6.20. So people have been using it for
~20 years now. At least it's the mm-managed bio swap path and we're not
actually upcalling the fuse server to... | {
"author": "\"Darrick J. Wong\" <djwong@kernel.org>",
"date": "Wed, 25 Feb 2026 09:03:22 -0800",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | This is the seventh public draft of a prototype to connect the Linux
fuse driver to fs-iomap for regular file IO operations to and from files
whose contents persist to locally attached storage devices. With this
release, I show that it's possible to build a fuse server for a real
filesystem (ext4) that runs entirely i... | null | null | null | [PATCHBLIZZARD v7] fuse/libfuse/e2fsprogs: containerize ext4 for
safer operation | On Wed, Feb 25, 2026 at 09:03:22AM -0800, Darrick J. Wong wrote:
Assuming it actually gets used, but yes, it's been there forever.
:( | {
"author": "Christoph Hellwig <hch@lst.de>",
"date": "Wed, 25 Feb 2026 18:49:11 +0100",
"is_openbsd": false,
"thread_id": "CAJfpegubENC3LxtG8MbO4OxUgD_Pd1GR9pw6Xcob_JiG+2cOFg@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Zhang Yi <yi.zhang@huawei.com>
When the device supports the Write Zeroes command and the DEAC bit, it
indicates that the deallocate bit in the Write Zeroes command is
supported, and the bytes read from a deallocated logical block are
zeroes. This means the device supports unmap Write Zeroes operation, so
set the... | null | null | null | [PATCH v2 2/9] nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit | From: Zhang Yi <yi.zhang@huawei.com>
Set the WZDS and DRB bits to the namespace dlfeat if the underlying
block device enables the unmap write zeroes operation, make the nvme
target device supports the unmap write zeroes command.
Signed-off-by: Zhang Yi <yi.zhang@huawei.com>
---
drivers/nvme/target/io-cmd-bdev.c | 4 ... | {
"author": "Zhang Yi <yi.zhang@huaweicloud.com>",
"date": "Thu, 19 Jun 2025 19:18:00 +0800",
"is_openbsd": false,
"thread_id": "CAJhEC04Vpo96SKN7iRjV0fUKXEj3oQ698RdoVAdWjRjVLpgvGw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Zhang Yi <yi.zhang@huawei.com>
When the device supports the Write Zeroes command and the DEAC bit, it
indicates that the deallocate bit in the Write Zeroes command is
supported, and the bytes read from a deallocated logical block are
zeroes. This means the device supports unmap Write Zeroes operation, so
set the... | null | null | null | [PATCH v2 2/9] nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit | From: Zhang Yi <yi.zhang@huawei.com>
Only the flags passed to blkdev_issue_zeroout() differ among the two
zeroing branches in blkdev_fallocate(). Therefore, do cleanup by
factoring them out.
Signed-off-by: Zhang Yi <yi.zhang@huawei.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Martin K. Petersen <mart... | {
"author": "Zhang Yi <yi.zhang@huaweicloud.com>",
"date": "Thu, 19 Jun 2025 19:18:04 +0800",
"is_openbsd": false,
"thread_id": "CAJhEC04Vpo96SKN7iRjV0fUKXEj3oQ698RdoVAdWjRjVLpgvGw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Zhang Yi <yi.zhang@huawei.com>
When the device supports the Write Zeroes command and the DEAC bit, it
indicates that the deallocate bit in the Write Zeroes command is
supported, and the bytes read from a deallocated logical block are
zeroes. This means the device supports unmap Write Zeroes operation, so
set the... | null | null | null | [PATCH v2 2/9] nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit | From: Zhang Yi <yi.zhang@huawei.com>
Changes since v1:
- Rebase codes on 6.16-rc2.
- Use max_{hw|user}_wzeroes_unmap_sectors queue limits instead of
BLK_FEAT_WRITE_ZEROES_UNMAP feature to represent the status of the
unmap write zeroes operation as Christoph and Darrick suggested. This
redoes the first 5 pat... | {
"author": "Zhang Yi <yi.zhang@huaweicloud.com>",
"date": "Thu, 19 Jun 2025 19:17:57 +0800",
"is_openbsd": false,
"thread_id": "CAJhEC04Vpo96SKN7iRjV0fUKXEj3oQ698RdoVAdWjRjVLpgvGw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Zhang Yi <yi.zhang@huawei.com>
When the device supports the Write Zeroes command and the DEAC bit, it
indicates that the deallocate bit in the Write Zeroes command is
supported, and the bytes read from a deallocated logical block are
zeroes. This means the device supports unmap Write Zeroes operation, so
set the... | null | null | null | [PATCH v2 2/9] nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit | From: Zhang Yi <yi.zhang@huawei.com>
Currently, disks primarily implement the write zeroes command (aka
REQ_OP_WRITE_ZEROES) through two mechanisms: the first involves
physically writing zeros to the disk media (e.g., HDDs), while the
second performs an unmap operation on the logical blocks, effectively
putting them i... | {
"author": "Zhang Yi <yi.zhang@huaweicloud.com>",
"date": "Thu, 19 Jun 2025 19:17:58 +0800",
"is_openbsd": false,
"thread_id": "CAJhEC04Vpo96SKN7iRjV0fUKXEj3oQ698RdoVAdWjRjVLpgvGw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Zhang Yi <yi.zhang@huawei.com>
When the device supports the Write Zeroes command and the DEAC bit, it
indicates that the deallocate bit in the Write Zeroes command is
supported, and the bytes read from a deallocated logical block are
zeroes. This means the device supports unmap Write Zeroes operation, so
set the... | null | null | null | [PATCH v2 2/9] nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit | From: Zhang Yi <yi.zhang@huawei.com>
Add support for FALLOC_FL_WRITE_ZEROES if the underlying device enable
the unmap write zeroes operation. This first allocates blocks as
unwritten, then issues a zero command outside of the running journal
handle, and finally converts them to a written state.
Signed-off-by: Zhang Y... | {
"author": "Zhang Yi <yi.zhang@huaweicloud.com>",
"date": "Thu, 19 Jun 2025 19:18:06 +0800",
"is_openbsd": false,
"thread_id": "CAJhEC04Vpo96SKN7iRjV0fUKXEj3oQ698RdoVAdWjRjVLpgvGw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Zhang Yi <yi.zhang@huawei.com>
When the device supports the Write Zeroes command and the DEAC bit, it
indicates that the deallocate bit in the Write Zeroes command is
supported, and the bytes read from a deallocated logical block are
zeroes. This means the device supports unmap Write Zeroes operation, so
set the... | null | null | null | [PATCH v2 2/9] nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit | From: Zhang Yi <yi.zhang@huawei.com>
The unmap write zeroes limits have been set to the stacking queue limits
by default in blk_set_stacking_limits() and blk_stack_limits(), but it
should be cleared if any underlying device does not support it.
Signed-off-by: Zhang Yi <yi.zhang@huawei.com>
---
drivers/md/dm-table.c ... | {
"author": "Zhang Yi <yi.zhang@huaweicloud.com>",
"date": "Thu, 19 Jun 2025 19:18:02 +0800",
"is_openbsd": false,
"thread_id": "CAJhEC04Vpo96SKN7iRjV0fUKXEj3oQ698RdoVAdWjRjVLpgvGw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Zhang Yi <yi.zhang@huawei.com>
When the device supports the Write Zeroes command and the DEAC bit, it
indicates that the deallocate bit in the Write Zeroes command is
supported, and the bytes read from a deallocated logical block are
zeroes. This means the device supports unmap Write Zeroes operation, so
set the... | null | null | null | [PATCH v2 2/9] nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit | From: Zhang Yi <yi.zhang@huawei.com>
When the device supports the Write Zeroes command and the zeroing mode
is set to SD_ZERO_WS16_UNMAP or SD_ZERO_WS10_UNMAP, this means that the
device supports unmap Write Zeroes, so set the corresponding
max_hw_write_zeroes_unmap_sectors to max_write_zeroes_sectors on the
device's ... | {
"author": "Zhang Yi <yi.zhang@huaweicloud.com>",
"date": "Thu, 19 Jun 2025 19:18:01 +0800",
"is_openbsd": false,
"thread_id": "CAJhEC04Vpo96SKN7iRjV0fUKXEj3oQ698RdoVAdWjRjVLpgvGw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Zhang Yi <yi.zhang@huawei.com>
When the device supports the Write Zeroes command and the DEAC bit, it
indicates that the deallocate bit in the Write Zeroes command is
supported, and the bytes read from a deallocated logical block are
zeroes. This means the device supports unmap Write Zeroes operation, so
set the... | null | null | null | [PATCH v2 2/9] nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit | From: Zhang Yi <yi.zhang@huawei.com>
With the development of flash-based storage devices, we can quickly
write zeros to SSDs using the WRITE_ZERO command if the devices do not
actually write physical zeroes to the media. Therefore, we can use this
command to quickly preallocate a real all-zero file with written
extent... | {
"author": "Zhang Yi <yi.zhang@huaweicloud.com>",
"date": "Thu, 19 Jun 2025 19:18:03 +0800",
"is_openbsd": false,
"thread_id": "CAJhEC04Vpo96SKN7iRjV0fUKXEj3oQ698RdoVAdWjRjVLpgvGw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Zhang Yi <yi.zhang@huawei.com>
When the device supports the Write Zeroes command and the DEAC bit, it
indicates that the deallocate bit in the Write Zeroes command is
supported, and the bytes read from a deallocated logical block are
zeroes. This means the device supports unmap Write Zeroes operation, so
set the... | null | null | null | [PATCH v2 2/9] nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit | From: Zhang Yi <yi.zhang@huawei.com>
Add support for FALLOC_FL_WRITE_ZEROES, if the block device enables the
unmap write zeroes operation, it will issue a write zeroes command.
Signed-off-by: Zhang Yi <yi.zhang@huawei.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Martin K. Petersen <martin.petersen@or... | {
"author": "Zhang Yi <yi.zhang@huaweicloud.com>",
"date": "Thu, 19 Jun 2025 19:18:05 +0800",
"is_openbsd": false,
"thread_id": "CAJhEC04Vpo96SKN7iRjV0fUKXEj3oQ698RdoVAdWjRjVLpgvGw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Zhang Yi <yi.zhang@huawei.com>
When the device supports the Write Zeroes command and the DEAC bit, it
indicates that the deallocate bit in the Write Zeroes command is
supported, and the bytes read from a deallocated logical block are
zeroes. This means the device supports unmap Write Zeroes operation, so
set the... | null | null | null | [PATCH v2 2/9] nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit | On Thu, 19 Jun 2025 19:17:57 +0800, Zhang Yi wrote:
If needed, the branch can be declared stable and thus be used as base
for other work.
---
Applied to the vfs-6.17.fallocate branch of the vfs/vfs.git tree.
Patches in the vfs-6.17.fallocate branch should appear in linux-next soon.
Please report any outstanding bug... | {
"author": "Christian Brauner <brauner@kernel.org>",
"date": "Mon, 23 Jun 2025 12:46:54 +0200",
"is_openbsd": false,
"thread_id": "CAJhEC04Vpo96SKN7iRjV0fUKXEj3oQ698RdoVAdWjRjVLpgvGw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Zhang Yi <yi.zhang@huawei.com>
When the device supports the Write Zeroes command and the DEAC bit, it
indicates that the deallocate bit in the Write Zeroes command is
supported, and the bytes read from a deallocated logical block are
zeroes. This means the device supports unmap Write Zeroes operation, so
set the... | null | null | null | [PATCH v2 2/9] nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit | Zhang,
This looks OK to me.
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
--
Martin K. Petersen | {
"author": "\"Martin K. Petersen\" <martin.petersen@oracle.com>",
"date": "Mon, 23 Jun 2025 11:08:39 -0400",
"is_openbsd": false,
"thread_id": "CAJhEC04Vpo96SKN7iRjV0fUKXEj3oQ698RdoVAdWjRjVLpgvGw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Zhang Yi <yi.zhang@huawei.com>
When the device supports the Write Zeroes command and the DEAC bit, it
indicates that the deallocate bit in the Write Zeroes command is
supported, and the bytes read from a deallocated logical block are
zeroes. This means the device supports unmap Write Zeroes operation, so
set the... | null | null | null | [PATCH v2 2/9] nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit | On 2025/6/23 23:08, Martin K. Petersen wrote:
Thank you, Martin and Christoph, for the patient review. I will update
my test patches next.
Best regards,
Yi. | {
"author": "Zhang Yi <yi.zhang@huaweicloud.com>",
"date": "Thu, 26 Jun 2025 21:57:14 +0800",
"is_openbsd": false,
"thread_id": "CAJhEC04Vpo96SKN7iRjV0fUKXEj3oQ698RdoVAdWjRjVLpgvGw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Zhang Yi <yi.zhang@huawei.com>
When the device supports the Write Zeroes command and the DEAC bit, it
indicates that the deallocate bit in the Write Zeroes command is
supported, and the bytes read from a deallocated logical block are
zeroes. This means the device supports unmap Write Zeroes operation, so
set the... | null | null | null | [PATCH v2 2/9] nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit | On 2025/6/23 18:46, Christian Brauner wrote:
Hi Christian,
I noticed that this patch series doesn't appear to be merged into this
branch. Just wondering if it might have been missed?
Best regards,
Yi. | {
"author": "Zhang Yi <yi.zhang@huaweicloud.com>",
"date": "Thu, 3 Jul 2025 11:35:41 +0800",
"is_openbsd": false,
"thread_id": "CAJhEC04Vpo96SKN7iRjV0fUKXEj3oQ698RdoVAdWjRjVLpgvGw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Zhang Yi <yi.zhang@huawei.com>
When the device supports the Write Zeroes command and the DEAC bit, it
indicates that the deallocate bit in the Write Zeroes command is
supported, and the bytes read from a deallocated logical block are
zeroes. This means the device supports unmap Write Zeroes operation, so
set the... | null | null | null | [PATCH v2 2/9] nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit | On Thu, Jul 03, 2025 at 11:35:41AM +0800, Zhang Yi wrote:
Dammit, my script missed to push the branch. Fixed now. Thanks for
checking! | {
"author": "Christian Brauner <brauner@kernel.org>",
"date": "Fri, 4 Jul 2025 10:39:53 +0200",
"is_openbsd": false,
"thread_id": "CAJhEC04Vpo96SKN7iRjV0fUKXEj3oQ698RdoVAdWjRjVLpgvGw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Zhang Yi <yi.zhang@huawei.com>
When the device supports the Write Zeroes command and the DEAC bit, it
indicates that the deallocate bit in the Write Zeroes command is
supported, and the bytes read from a deallocated logical block are
zeroes. This means the device supports unmap Write Zeroes operation, so
set the... | null | null | null | [PATCH v2 2/9] nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit | On 19/06/2025 12:17, Zhang Yi wrote:
JFYI, I noticed that I am failing this check in raid0_set_limits() ->
queue_limits_set() -> queue_limits_commit_update() ->
blk_validate_limits() for v6.17-rc2
The raid0 array consists of NVMe partitions. Here
lim->max_hw_wzeroes_unmap_sectors = 4096 and
lim->max_write_zeroes_... | {
"author": "John Garry <john.g.garry@oracle.com>",
"date": "Thu, 21 Aug 2025 13:55:10 +0100",
"is_openbsd": false,
"thread_id": "CAJhEC04Vpo96SKN7iRjV0fUKXEj3oQ698RdoVAdWjRjVLpgvGw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Zhang Yi <yi.zhang@huawei.com>
When the device supports the Write Zeroes command and the DEAC bit, it
indicates that the deallocate bit in the Write Zeroes command is
supported, and the bytes read from a deallocated logical block are
zeroes. This means the device supports unmap Write Zeroes operation, so
set the... | null | null | null | [PATCH v2 2/9] nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit | On 8/21/2025 8:55 PM, John Garry wrote:
Thank you for checking on this!
The problem is that raid0_set_limits() only sets max_write_zeroes_sectors
without synchronously setting max_hw_wzeroes_unmap_sectors. It appears
that all stacked drivers that call blk_set_stacking_limits() to
initialize stacked limits but indepen... | {
"author": "Zhang Yi <yi.zhang@huaweicloud.com>",
"date": "Sat, 23 Aug 2025 12:37:17 +0800",
"is_openbsd": false,
"thread_id": "CAJhEC04Vpo96SKN7iRjV0fUKXEj3oQ698RdoVAdWjRjVLpgvGw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Zhang Yi <yi.zhang@huawei.com>
When the device supports the Write Zeroes command and the DEAC bit, it
indicates that the deallocate bit in the Write Zeroes command is
supported, and the bytes read from a deallocated logical block are
zeroes. This means the device supports unmap Write Zeroes operation, so
set the... | null | null | null | [PATCH v2 2/9] nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit | Dear Zhang Yi,
In reviewing your patch series implementing support for the
FALLOC_FL_WRITE_ZEROES flag, I noted the logic propagating
max_write_zeroes_sectors to max_hw_wzeroes_unmap_sectors in commit 545fb46e5bc6
"nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit" [1]. This
appears to be intended for... | {
"author": "Robert Pang <robertpang@google.com>",
"date": "Tue, 24 Feb 2026 16:05:31 -0800",
"is_openbsd": false,
"thread_id": "CAJhEC04Vpo96SKN7iRjV0fUKXEj3oQ698RdoVAdWjRjVLpgvGw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Zhang Yi <yi.zhang@huawei.com>
When the device supports the Write Zeroes command and the DEAC bit, it
indicates that the deallocate bit in the Write Zeroes command is
supported, and the bytes read from a deallocated logical block are
zeroes. This means the device supports unmap Write Zeroes operation, so
set the... | null | null | null | [PATCH v2 2/9] nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit | Hi Robert!
On 2/25/2026 8:05 AM, Robert Pang wrote:
Thank you for your point. Overall, this makes sense to me, but I have one
question below.
^^^^^^^^^^^^^^^^^^
Why do you want to add a check for NVME_CTRL_ONCS_DSM? In nvme_config_discard(),
it appears that we prioritize ctrl->dmrsl, ... | {
"author": "Zhang Yi <yi.zhang@huaweicloud.com>",
"date": "Wed, 25 Feb 2026 10:32:36 +0800",
"is_openbsd": false,
"thread_id": "CAJhEC04Vpo96SKN7iRjV0fUKXEj3oQ698RdoVAdWjRjVLpgvGw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Zhang Yi <yi.zhang@huawei.com>
When the device supports the Write Zeroes command and the DEAC bit, it
indicates that the deallocate bit in the Write Zeroes command is
supported, and the bytes read from a deallocated logical block are
zeroes. This means the device supports unmap Write Zeroes operation, so
set the... | null | null | null | [PATCH v2 2/9] nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit | Dear Zhang Yi
Thank you for your quick response. Please see my comments below:
On Tue, Feb 24, 2026 at 6:32 PM Zhang Yi <yi.zhang@huaweicloud.com> wrote:
The check for NVME_CTRL_ONCS_DSM is to follow the same check in [3]. There, the
check was added by 58a0c875ce02 "nvme: don't apply NVME_QUIRK_DEALLOCATE_ZEROES
when... | {
"author": "Robert Pang <robertpang@google.com>",
"date": "Wed, 25 Feb 2026 13:43:31 -0800",
"is_openbsd": false,
"thread_id": "CAJhEC04Vpo96SKN7iRjV0fUKXEj3oQ698RdoVAdWjRjVLpgvGw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | From: Zhang Yi <yi.zhang@huawei.com>
When the device supports the Write Zeroes command and the DEAC bit, it
indicates that the deallocate bit in the Write Zeroes command is
supported, and the bytes read from a deallocated logical block are
zeroes. This means the device supports unmap Write Zeroes operation, so
set the... | null | null | null | [PATCH v2 2/9] nvme: set max_hw_wzeroes_unmap_sectors if device supports DEAC bit | Dear Zhang Yi
On Thu, Feb 26, 2026 at 3:09 AM Zhang Yi <yi.zhang@huaweicloud.com> wrote:
Thank you for your confirmation. I will follow up and submit the patch
to other maintainers for their review.
Best regards,
Robert | {
"author": "Robert Pang <robertpang@google.com>",
"date": "Thu, 26 Feb 2026 17:34:38 -0800",
"is_openbsd": false,
"thread_id": "CAJhEC04Vpo96SKN7iRjV0fUKXEj3oQ698RdoVAdWjRjVLpgvGw@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Extract common queue iteration and teardown logic into
fuse_uring_teardown_all_queues() helper function to eliminate code
duplication between fuse_uring_async_stop_queues() and
fuse_uring_stop_queues().
This is a pure refactoring with no functional changes, intended to
improve maintainability.
Signed-off-by: Yuto Ohn... | null | null | null | [PATCH] fuse: refactor duplicate queue teardown operation | On 2/23/26 15:03, Yuto Ohnuki wrote:
Thank you! Looks good to me.
Reviewed-by: Bernd Schubert <bernd@bsbernd.com> | {
"author": "Bernd Schubert <bernd@bsbernd.com>",
"date": "Wed, 25 Feb 2026 04:24:01 +0100",
"is_openbsd": false,
"thread_id": "CAJfpegucMPVW1mEkRJrLUBuJ4pV54=h8S66U8H==qPmjEGwRPA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-fsdevel | Add support for using RWF_DONTCACHE with block devices and other
buffer_head-based I/O.
Dropbehind pruning needs to be done in non-IRQ context, but block
devices complete writeback in IRQ context. To fix this, we first defer
dropbehind completion initiated from IRQ context by scheduling a work
item to process a per-CP... | null | null | null | [PATCH RFC v3 0/2] block: enable RWF_DONTCACHE for block devices | Block device buffered reads and writes already pass through
filemap_read() and iomap_file_buffered_write() respectively, both of
which handle IOCB_DONTCACHE. Enable RWF_DONTCACHE for block device files
by setting FOP_DONTCACHE in def_blk_fops.
For CONFIG_BUFFER_HEAD paths, add block_write_begin_iocb() which threads
th... | {
"author": "Tal Zussman <tz2294@columbia.edu>",
"date": "Fri, 27 Feb 2026 11:41:08 -0500",
"is_openbsd": false,
"thread_id": "20260227-blk-dontcache-v3-2-cd309ccd5868@columbia.edu.mbox.gz"
} |
lkml_critique | linux-fsdevel | Add support for using RWF_DONTCACHE with block devices and other
buffer_head-based I/O.
Dropbehind pruning needs to be done in non-IRQ context, but block
devices complete writeback in IRQ context. To fix this, we first defer
dropbehind completion initiated from IRQ context by scheduling a work
item to process a per-CP... | null | null | null | [PATCH RFC v3 0/2] block: enable RWF_DONTCACHE for block devices | folio_end_dropbehind() is called from folio_end_writeback(), which can
run in IRQ context through buffer_head completion.
Previously, when folio_end_dropbehind() detected !in_task(), it skipped
the invalidation entirely. This meant that folios marked for dropbehind
via RWF_DONTCACHE would remain in the page cache afte... | {
"author": "Tal Zussman <tz2294@columbia.edu>",
"date": "Fri, 27 Feb 2026 11:41:07 -0500",
"is_openbsd": false,
"thread_id": "20260227-blk-dontcache-v3-2-cd309ccd5868@columbia.edu.mbox.gz"
} |
lkml_critique | bpf | Global subprogs are currently not allowed to return void. Adjust
verifier logic to allow global functions with a void return type.
Exception callbacks are excluded from this change, and still require
a scalar return type.
Adding additional logic for void globals significantly complicates
check_return_code(), mainly b... | null | null | null | [PATCH bpf-next v5 0/5] bpf: Allow void return type for global subprogs | Factor the return value range calculation logic in check_return_code
out of the function in preparation for separating the return value
validation logic for BPF_EXIT and bpf_throw().
Signed-off-by: Emil Tsalapatis <emil@etsalapatis.com>
---
include/linux/bpf_verifier.h | 1 +
kernel/bpf/verifier.c | 225 ++++... | {
"author": "Emil Tsalapatis <emil@etsalapatis.com>",
"date": "Fri, 27 Feb 2026 10:46:12 -0500",
"is_openbsd": false,
"thread_id": "DGPV3UPSTRSK.1QB5KADDS30GS@etsalapatis.com.mbox.gz"
} |
lkml_critique | bpf | Global subprogs are currently not allowed to return void. Adjust
verifier logic to allow global functions with a void return type.
Exception callbacks are excluded from this change, and still require
a scalar return type.
Adding additional logic for void globals significantly complicates
check_return_code(), mainly b... | null | null | null | [PATCH bpf-next v5 0/5] bpf: Allow void return type for global subprogs | From: Eduard Zingerman <eddyz87@gmail.com>
Both main progs and subprogs use the same function in the verifier,
check_return_code, to verify the type and value range of the register
being returned. However, subprogs only need a subset of the logic in
check_return_code. this also goes the way - check_return_code explici... | {
"author": "Emil Tsalapatis <emil@etsalapatis.com>",
"date": "Fri, 27 Feb 2026 10:46:14 -0500",
"is_openbsd": false,
"thread_id": "DGPV3UPSTRSK.1QB5KADDS30GS@etsalapatis.com.mbox.gz"
} |
lkml_critique | bpf | Global subprogs are currently not allowed to return void. Adjust
verifier logic to allow global functions with a void return type.
Exception callbacks are excluded from this change, and still require
a scalar return type.
Adding additional logic for void globals significantly complicates
check_return_code(), mainly b... | null | null | null | [PATCH bpf-next v5 0/5] bpf: Allow void return type for global subprogs | From: Eduard Zingerman <eddyz87@gmail.com>
The check_return_code function has explicit checks on whether
a program type can return void. Factor this logic out to reuse
it later for both main progs and subprogs.
Signed-off-by: Eduard Zingerman <eddyz87@gmail.com>
Reviewed-by: Emil Tsalapatis <emil@etsalapatis.com>
---... | {
"author": "Emil Tsalapatis <emil@etsalapatis.com>",
"date": "Fri, 27 Feb 2026 10:46:13 -0500",
"is_openbsd": false,
"thread_id": "DGPV3UPSTRSK.1QB5KADDS30GS@etsalapatis.com.mbox.gz"
} |
lkml_critique | bpf | Global subprogs are currently not allowed to return void. Adjust
verifier logic to allow global functions with a void return type.
Exception callbacks are excluded from this change, and still require
a scalar return type.
Adding additional logic for void globals significantly complicates
check_return_code(), mainly b... | null | null | null | [PATCH bpf-next v5 0/5] bpf: Allow void return type for global subprogs | Global subprogs are currently not allowed to return void. Adjust
verifier logic to allow global functions with a void return type.
Signed-off-by: Emil Tsalapatis <emil@etsalapatis.com>
---
kernel/bpf/btf.c | 7 +-
kernel/bpf/verifier.c | 64 ++++++++++++++++---
..... | {
"author": "Emil Tsalapatis <emil@etsalapatis.com>",
"date": "Fri, 27 Feb 2026 10:46:15 -0500",
"is_openbsd": false,
"thread_id": "DGPV3UPSTRSK.1QB5KADDS30GS@etsalapatis.com.mbox.gz"
} |
lkml_critique | bpf | Global subprogs are currently not allowed to return void. Adjust
verifier logic to allow global functions with a void return type.
Exception callbacks are excluded from this change, and still require
a scalar return type.
Adding additional logic for void globals significantly complicates
check_return_code(), mainly b... | null | null | null | [PATCH bpf-next v5 0/5] bpf: Allow void return type for global subprogs | Add additional testing for void global functions. The tests
ensure that calls to void global functions properly keep
R0 invalid. Also make sure that exception callbacks still
require a return value.
Signed-off-by: Emil Tsalapatis <emil@etsalapatis.com>
---
.../selftests/bpf/prog_tests/exceptions.c | 1 +
.../sel... | {
"author": "Emil Tsalapatis <emil@etsalapatis.com>",
"date": "Fri, 27 Feb 2026 10:46:16 -0500",
"is_openbsd": false,
"thread_id": "DGPV3UPSTRSK.1QB5KADDS30GS@etsalapatis.com.mbox.gz"
} |
lkml_critique | bpf | Global subprogs are currently not allowed to return void. Adjust
verifier logic to allow global functions with a void return type.
Exception callbacks are excluded from this change, and still require
a scalar return type.
Adding additional logic for void globals significantly complicates
check_return_code(), mainly b... | null | null | null | [PATCH bpf-next v5 0/5] bpf: Allow void return type for global subprogs | On Fri Feb 27, 2026 at 10:46 AM EST, Emil Tsalapatis wrote:
Note: I've kept the range and subsequent check as-is, but it's not actually
correct - the check below does tnum_in(enforce_attach_type_range,
var_off) when it should be tnum_overlap(). I will fix this in a separate
series since it definitely needs a selftest ... | {
"author": "\"Emil Tsalapatis\" <emil@etsalapatis.com>",
"date": "Fri, 27 Feb 2026 10:50:40 -0500",
"is_openbsd": false,
"thread_id": "DGPV3UPSTRSK.1QB5KADDS30GS@etsalapatis.com.mbox.gz"
} |
lkml_critique | bpf | Global subprogs are currently not allowed to return void. Adjust
verifier logic to allow global functions with a void return type.
Exception callbacks are excluded from this change, and still require
a scalar return type.
Adding additional logic for void globals significantly complicates
check_return_code(), mainly b... | null | null | null | [PATCH bpf-next v5 0/5] bpf: Allow void return type for global subprogs | [ ... ]
^^^^
Should this be one tab less? The rest of the function uses a single
tab for if-body indentation:
if (err)
return err;
but here we have three tabs instead of two.
[ ... ]
---
AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
See: https://github.... | {
"author": "bot+bpf-ci@kernel.org",
"date": "Fri, 27 Feb 2026 16:24:57 +0000 (UTC)",
"is_openbsd": false,
"thread_id": "DGPV3UPSTRSK.1QB5KADDS30GS@etsalapatis.com.mbox.gz"
} |
lkml_critique | bpf | Patch 1/2 skips kprobe_multi subtests when bpf_testmod isn't available.
Patch 2 makes perf_event triggering reliable on slower systems.
Tested:
./test_progs -t bpf_cookie/perf_event -vv (30 runs): 0 failures
Sun Jian (2):
selftests/bpf: bpf_cookie: skip kprobe_multi tests without bpf_testmod
selftests/bpf: bpf_... | null | null | null | [PATCH 0/2] selftests/bpf: fix bpf_cookie failures | The kprobe_multi subtests rely on bpf_testmod fentry ksyms.
When bpf_testmod isn't available, libbpf fails to resolve
bpf_testmod_fentry_test* and skeleton load fails with -ESRCH, causing
false failures.
Skip these subtests when env.has_testmod is false.
Signed-off-by: Sun Jian <sun.jian.kdev@gmail.com>
---
tools/t... | {
"author": "Sun Jian <sun.jian.kdev@gmail.com>",
"date": "Sat, 28 Feb 2026 00:40:36 +0800",
"is_openbsd": false,
"thread_id": "20260227164037.84110-3-sun.jian.kdev@gmail.com.mbox.gz"
} |
lkml_critique | bpf | Patch 1/2 skips kprobe_multi subtests when bpf_testmod isn't available.
Patch 2 makes perf_event triggering reliable on slower systems.
Tested:
./test_progs -t bpf_cookie/perf_event -vv (30 runs): 0 failures
Sun Jian (2):
selftests/bpf: bpf_cookie: skip kprobe_multi tests without bpf_testmod
selftests/bpf: bpf_... | null | null | null | [PATCH 0/2] selftests/bpf: fix bpf_cookie failures | The perf_event subtest relies on SW_CPU_CLOCK sampling to trigger the BPF
program, but the current CPU burn loop can be too short on slower systems
and may fail to generate any overflow sample. This leaves pe_res unchanged
and makes the test flaky.
Make burn_cpu() take a loop count and use a longer burn only for the
p... | {
"author": "Sun Jian <sun.jian.kdev@gmail.com>",
"date": "Sat, 28 Feb 2026 00:40:37 +0800",
"is_openbsd": false,
"thread_id": "20260227164037.84110-3-sun.jian.kdev@gmail.com.mbox.gz"
} |
lkml_critique | bpf | From: Abhishek Dubey <adubey@linux.ibm.com>
The first 2 patch enable support for instruction array. Now, the
instruction offset map maintain the mapping:
original inst -> xlated inst -> jited inst
The last two patch enable support for indirect jump. Any eligile
register can store jump target address for control flow... | null | null | null | [PATCH v2 0/4] powerpc64/bpf: Add support for instruction array and indirect jump | From: Abhishek Dubey <adubey@linux.ibm.com>
On loading the BPF program, the verifier might adjust/omit some
instructions. The adjusted instruction offset is accounted in the
map containing original instruction -> xlated mapping. This patch
add ppc64 JIT support to additionally build the xlated->jitted
mapping for ever... | {
"author": "adubey@linux.ibm.com",
"date": "Thu, 26 Feb 2026 20:43:08 -0500",
"is_openbsd": false,
"thread_id": "20260227014315.39980-3-adubey@linux.ibm.com.mbox.gz"
} |
lkml_critique | bpf | From: Abhishek Dubey <adubey@linux.ibm.com>
The first 2 patch enable support for instruction array. Now, the
instruction offset map maintain the mapping:
original inst -> xlated inst -> jited inst
The last two patch enable support for indirect jump. Any eligile
register can store jump target address for control flow... | null | null | null | [PATCH v2 0/4] powerpc64/bpf: Add support for instruction array and indirect jump | From: Abhishek Dubey <adubey@linux.ibm.com>
With instruction array now supported, enable corresponding bpf
selftest for powerpc.
Signed-off-by: Abhishek Dubey <adubey@linux.ibm.com>
---
tools/testing/selftests/bpf/prog_tests/bpf_insn_array.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/t... | {
"author": "adubey@linux.ibm.com",
"date": "Thu, 26 Feb 2026 20:43:09 -0500",
"is_openbsd": false,
"thread_id": "20260227014315.39980-3-adubey@linux.ibm.com.mbox.gz"
} |
lkml_critique | bpf | From: Abhishek Dubey <adubey@linux.ibm.com>
The first 2 patch enable support for instruction array. Now, the
instruction offset map maintain the mapping:
original inst -> xlated inst -> jited inst
The last two patch enable support for indirect jump. Any eligile
register can store jump target address for control flow... | null | null | null | [PATCH v2 0/4] powerpc64/bpf: Add support for instruction array and indirect jump | From: Abhishek Dubey <adubey@linux.ibm.com>
Add support for a new instruction
BPF_JMP|BPF_X|BPF_JA, SRC=0, DST=Rx, off=0, imm=0
which does an indirect jump to a location stored in Rx. The
register Rx should have type PTR_TO_INSN. This new type ensures
that the Rx register contains a value (or a range of values)
loa... | {
"author": "adubey@linux.ibm.com",
"date": "Thu, 26 Feb 2026 20:43:10 -0500",
"is_openbsd": false,
"thread_id": "20260227014315.39980-3-adubey@linux.ibm.com.mbox.gz"
} |
lkml_critique | bpf | From: Abhishek Dubey <adubey@linux.ibm.com>
The first 2 patch enable support for instruction array. Now, the
instruction offset map maintain the mapping:
original inst -> xlated inst -> jited inst
The last two patch enable support for indirect jump. Any eligile
register can store jump target address for control flow... | null | null | null | [PATCH v2 0/4] powerpc64/bpf: Add support for instruction array and indirect jump | From: Abhishek Dubey <adubey@linux.ibm.com>
With gotox instruction and jumptable now supported,
enable corresponding bpf selftest on powerpc.
Signed-off-by: Abhishek Dubey <adubey@linux.ibm.com>
---
tools/testing/selftests/bpf/progs/verifier_gotox.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --g... | {
"author": "adubey@linux.ibm.com",
"date": "Thu, 26 Feb 2026 20:43:11 -0500",
"is_openbsd": false,
"thread_id": "20260227014315.39980-3-adubey@linux.ibm.com.mbox.gz"
} |
lkml_critique | bpf | From: Abhishek Dubey <adubey@linux.ibm.com>
The first 2 patch enable support for instruction array. Now, the
instruction offset map maintain the mapping:
original inst -> xlated inst -> jited inst
The last two patch enable support for indirect jump. Any eligile
register can store jump target address for control flow... | null | null | null | [PATCH v2 0/4] powerpc64/bpf: Add support for instruction array and indirect jump | Tested-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
Tested this series and below are the results.
./test_progs-cpuv4 -n 21
#21/1 bpf_insn_array/one2one:OK
#21/2 bpf_insn_array/simple:OK
#21/3 bpf_insn_array/deletions:OK
#21/4 bpf_insn_array/deletions-with-functions:OK
#21/5 bpf_insn_array/blindne... | {
"author": "Venkat <venkat88@linux.ibm.com>",
"date": "Fri, 27 Feb 2026 20:58:29 +0530",
"is_openbsd": false,
"thread_id": "20260227014315.39980-3-adubey@linux.ibm.com.mbox.gz"
} |
lkml_critique | bpf | This series is based on Linux 7.0-rc1, tested on Loongson-3A6000,
the main aim is to support small struct arguments and 12 function
arguments for LoongArch BPF trampoline.
Tiezhu Yang (3):
LoongArch: BPF: Open code and remove invoke_bpf_mod_ret()
LoongArch: BPF: Support small struct arguments for trampoline
Loon... | null | null | null | [PATCH v1 0/3] LoongArch: BPF: Support more features for trampoline | invoke_bpf_mod_ret() is a small wrapper over invoke_bpf_prog(),
it should check the return value of invoke_bpf_prog() and then
return immediately if invoke_bpf_prog() failed, just open code
and remove it due to it is called only once.
Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
---
arch/loongarch/net/bpf_jit.... | {
"author": "Tiezhu Yang <yangtiezhu@loongson.cn>",
"date": "Tue, 24 Feb 2026 15:35:13 +0800",
"is_openbsd": false,
"thread_id": "CAEyhmHQVTzOohJUAL5FfP39pY=8q=ui7LYE3Z4+n1s71GK3Shw@mail.gmail.com.mbox.gz"
} |
lkml_critique | bpf | This series is based on Linux 7.0-rc1, tested on Loongson-3A6000,
the main aim is to support small struct arguments and 12 function
arguments for LoongArch BPF trampoline.
Tiezhu Yang (3):
LoongArch: BPF: Open code and remove invoke_bpf_mod_ret()
LoongArch: BPF: Support small struct arguments for trampoline
Loon... | null | null | null | [PATCH v1 0/3] LoongArch: BPF: Support more features for trampoline | Currently, LoongArch bpf trampoline supports up to 8 function arguments.
According to the statistics from commit 473e3150e30a ("bpf, x86: allow
function arguments up to 12 for TRACING"), there are over 200 functions
accept 9 to 12 arguments, so add 12 arguments support for trampoline.
With this patch, the following re... | {
"author": "Tiezhu Yang <yangtiezhu@loongson.cn>",
"date": "Tue, 24 Feb 2026 15:35:15 +0800",
"is_openbsd": false,
"thread_id": "CAEyhmHQVTzOohJUAL5FfP39pY=8q=ui7LYE3Z4+n1s71GK3Shw@mail.gmail.com.mbox.gz"
} |
lkml_critique | bpf | This series is based on Linux 7.0-rc1, tested on Loongson-3A6000,
the main aim is to support small struct arguments and 12 function
arguments for LoongArch BPF trampoline.
Tiezhu Yang (3):
LoongArch: BPF: Open code and remove invoke_bpf_mod_ret()
LoongArch: BPF: Support small struct arguments for trampoline
Loon... | null | null | null | [PATCH v1 0/3] LoongArch: BPF: Support more features for trampoline | In the current BPF code, the struct argument size is at most 16 bytes,
enforced by the verifier. According to the Procedure Call Standard for
LoongArch [1], the struct argument size below 16 bytes are provided as
part of the 8 argument registers, that is to say, the struct argument
may be passed in a pair of registers ... | {
"author": "Tiezhu Yang <yangtiezhu@loongson.cn>",
"date": "Tue, 24 Feb 2026 15:35:14 +0800",
"is_openbsd": false,
"thread_id": "CAEyhmHQVTzOohJUAL5FfP39pY=8q=ui7LYE3Z4+n1s71GK3Shw@mail.gmail.com.mbox.gz"
} |
lkml_critique | bpf | This series is based on Linux 7.0-rc1, tested on Loongson-3A6000,
the main aim is to support small struct arguments and 12 function
arguments for LoongArch BPF trampoline.
Tiezhu Yang (3):
LoongArch: BPF: Open code and remove invoke_bpf_mod_ret()
LoongArch: BPF: Support small struct arguments for trampoline
Loon... | null | null | null | [PATCH v1 0/3] LoongArch: BPF: Support more features for trampoline | On Tue, Feb 24, 2026 at 3:35 PM Tiezhu Yang <yangtiezhu@loongson.cn> wrote:
For the series:
Acked-by: Hengqi Chen <hengqi.chen@gmail.com>
Tested-by: Hengqi Chen <hengqi.chen@gmail.com> | {
"author": "Hengqi Chen <hengqi.chen@gmail.com>",
"date": "Fri, 27 Feb 2026 17:55:25 +0800",
"is_openbsd": false,
"thread_id": "CAEyhmHQVTzOohJUAL5FfP39pY=8q=ui7LYE3Z4+n1s71GK3Shw@mail.gmail.com.mbox.gz"
} |
lkml_critique | bpf | Update struct btf_header to add a new "layout" section containing
a description of how to parse the BTF kinds known about at BTF
encoding time. This provides the opportunity for tools that might
not know all of these kinds - as is the case when older tools run
on more newly-generated BTF - to still parse the BTF provi... | null | null | null | [PATCH v10 bpf-next 00/10] Add BTF layout to BTF | BTF kind layouts provide information to parse BTF kinds. By separating
parsing BTF from using all the information it provides, we allow BTF
to encode new features even if they cannot be used by readers. This
will be helpful in particular for cases where older tools are used
to parse newer BTF with kinds the older tools... | {
"author": "Alan Maguire <alan.maguire@oracle.com>",
"date": "Fri, 27 Feb 2026 10:04:17 +0000",
"is_openbsd": false,
"thread_id": "20260227100426.2585191-8-alan.maguire@oracle.com.mbox.gz"
} |
lkml_critique | bpf | Update struct btf_header to add a new "layout" section containing
a description of how to parse the BTF kinds known about at BTF
encoding time. This provides the opportunity for tools that might
not know all of these kinds - as is the case when older tools run
on more newly-generated BTF - to still parse the BTF provi... | null | null | null | [PATCH v10 bpf-next 00/10] Add BTF layout to BTF | Support reading in layout fixing endian issues on reading;
also support writing layout section to raw BTF object.
There is not yet an API to populate the layout with meaningful
information.
As part of this, we need to consider multiple valid BTF header
sizes; the original or the layout-extended headers.
So to support ... | {
"author": "Alan Maguire <alan.maguire@oracle.com>",
"date": "Fri, 27 Feb 2026 10:04:18 +0000",
"is_openbsd": false,
"thread_id": "20260227100426.2585191-8-alan.maguire@oracle.com.mbox.gz"
} |
lkml_critique | bpf | Update struct btf_header to add a new "layout" section containing
a description of how to parse the BTF kinds known about at BTF
encoding time. This provides the opportunity for tools that might
not know all of these kinds - as is the case when older tools run
on more newly-generated BTF - to still parse the BTF provi... | null | null | null | [PATCH v10 bpf-next 00/10] Add BTF layout to BTF | Validate layout if present, but because the kernel must be
strict in what it accepts, reject BTF with unsupported kinds,
even if they are in the layout information.
Signed-off-by: Alan Maguire <alan.maguire@oracle.com>
---
kernel/bpf/btf.c | 50 ++++++++++++++++++++++++++++++++++++++++++++----
1 file changed, 46 inse... | {
"author": "Alan Maguire <alan.maguire@oracle.com>",
"date": "Fri, 27 Feb 2026 10:04:22 +0000",
"is_openbsd": false,
"thread_id": "20260227100426.2585191-8-alan.maguire@oracle.com.mbox.gz"
} |
lkml_critique | bpf | Update struct btf_header to add a new "layout" section containing
a description of how to parse the BTF kinds known about at BTF
encoding time. This provides the opportunity for tools that might
not know all of these kinds - as is the case when older tools run
on more newly-generated BTF - to still parse the BTF provi... | null | null | null | [PATCH v10 bpf-next 00/10] Add BTF layout to BTF | This allows BTF parsing to proceed even if we do not know the
kind. Fall back to base BTF layout if layout information is
not in split BTF.
Signed-off-by: Alan Maguire <alan.maguire@oracle.com>
---
tools/lib/bpf/btf.c | 42 +++++++++++++++++++++++++++++++++---------
1 file changed, 33 insertions(+), 9 deletions(-)
... | {
"author": "Alan Maguire <alan.maguire@oracle.com>",
"date": "Fri, 27 Feb 2026 10:04:19 +0000",
"is_openbsd": false,
"thread_id": "20260227100426.2585191-8-alan.maguire@oracle.com.mbox.gz"
} |
lkml_critique | bpf | Update struct btf_header to add a new "layout" section containing
a description of how to parse the BTF kinds known about at BTF
encoding time. This provides the opportunity for tools that might
not know all of these kinds - as is the case when older tools run
on more newly-generated BTF - to still parse the BTF provi... | null | null | null | [PATCH v10 bpf-next 00/10] Add BTF layout to BTF | BTF parsing can use layout to navigate unknown kinds, so
btf_validate_type() should take layout information into
account to avoid failure when an unrecognized kind is met.
Signed-off-by: Alan Maguire <alan.maguire@oracle.com>
---
tools/lib/bpf/btf.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff ... | {
"author": "Alan Maguire <alan.maguire@oracle.com>",
"date": "Fri, 27 Feb 2026 10:04:21 +0000",
"is_openbsd": false,
"thread_id": "20260227100426.2585191-8-alan.maguire@oracle.com.mbox.gz"
} |
lkml_critique | bpf | Update struct btf_header to add a new "layout" section containing
a description of how to parse the BTF kinds known about at BTF
encoding time. This provides the opportunity for tools that might
not know all of these kinds - as is the case when older tools run
on more newly-generated BTF - to still parse the BTF provi... | null | null | null | [PATCH v10 bpf-next 00/10] Add BTF layout to BTF | Support encoding of BTF layout data via btf__new_empty_opts().
Current supported opts are base_btf and add_layout.
Layout information is maintained in btf.c in the layouts[] array;
when BTF is created with the add_layout option it represents the
current view of supported BTF kinds.
Signed-off-by: Alan Maguire <alan.... | {
"author": "Alan Maguire <alan.maguire@oracle.com>",
"date": "Fri, 27 Feb 2026 10:04:20 +0000",
"is_openbsd": false,
"thread_id": "20260227100426.2585191-8-alan.maguire@oracle.com.mbox.gz"
} |
lkml_critique | bpf | Update struct btf_header to add a new "layout" section containing
a description of how to parse the BTF kinds known about at BTF
encoding time. This provides the opportunity for tools that might
not know all of these kinds - as is the case when older tools run
on more newly-generated BTF - to still parse the BTF provi... | null | null | null | [PATCH v10 bpf-next 00/10] Add BTF layout to BTF | verify btf__new_empty_opts() adds layouts for all kinds supported,
and after adding kind-related types for an unknown kind, ensure that
parsing uses this info when that kind is encountered rather than
giving up.
Signed-off-by: Alan Maguire <alan.maguire@oracle.com>
---
.../selftests/bpf/prog_tests/btf_kind.c | ... | {
"author": "Alan Maguire <alan.maguire@oracle.com>",
"date": "Fri, 27 Feb 2026 10:04:23 +0000",
"is_openbsd": false,
"thread_id": "20260227100426.2585191-8-alan.maguire@oracle.com.mbox.gz"
} |
lkml_critique | bpf | Update struct btf_header to add a new "layout" section containing
a description of how to parse the BTF kinds known about at BTF
encoding time. This provides the opportunity for tools that might
not know all of these kinds - as is the case when older tools run
on more newly-generated BTF - to still parse the BTF provi... | null | null | null | [PATCH v10 bpf-next 00/10] Add BTF layout to BTF | Provide a way to dump BTF metadata info via bpftool; this
consists of BTF size, header fields and layout info
(if available); for example
$ bpftool btf dump file vmlinux format meta
size 6516862
magic 0xeb9f
version 1
flags 0x0
hdr_len 32
type_len 3929096
type_off 0
str_len 2587654
str_off 3929176
layout_len 80
layout... | {
"author": "Alan Maguire <alan.maguire@oracle.com>",
"date": "Fri, 27 Feb 2026 10:04:24 +0000",
"is_openbsd": false,
"thread_id": "20260227100426.2585191-8-alan.maguire@oracle.com.mbox.gz"
} |
lkml_critique | bpf | Update struct btf_header to add a new "layout" section containing
a description of how to parse the BTF kinds known about at BTF
encoding time. This provides the opportunity for tools that might
not know all of these kinds - as is the case when older tools run
on more newly-generated BTF - to still parse the BTF provi... | null | null | null | [PATCH v10 bpf-next 00/10] Add BTF layout to BTF | ...and provide an example of output.
Signed-off-by: Alan Maguire <alan.maguire@oracle.com>
---
.../bpf/bpftool/Documentation/bpftool-btf.rst | 28 +++++++++++++++++--
1 file changed, 26 insertions(+), 2 deletions(-)
diff --git a/tools/bpf/bpftool/Documentation/bpftool-btf.rst b/tools/bpf/bpftool/Documentation/bpftoo... | {
"author": "Alan Maguire <alan.maguire@oracle.com>",
"date": "Fri, 27 Feb 2026 10:04:25 +0000",
"is_openbsd": false,
"thread_id": "20260227100426.2585191-8-alan.maguire@oracle.com.mbox.gz"
} |
lkml_critique | bpf | Update struct btf_header to add a new "layout" section containing
a description of how to parse the BTF kinds known about at BTF
encoding time. This provides the opportunity for tools that might
not know all of these kinds - as is the case when older tools run
on more newly-generated BTF - to still parse the BTF provi... | null | null | null | [PATCH v10 bpf-next 00/10] Add BTF layout to BTF | The "layout" feature will add metadata about BTF kinds to the
generated BTF; its absence in pahole will not trigger an error so it
is safe to add unconditionally as it will simply be ignored if pahole
does not support it.
Signed-off-by: Alan Maguire <alan.maguire@oracle.com>
---
scripts/Makefile.btf | 2 ++
1 file ch... | {
"author": "Alan Maguire <alan.maguire@oracle.com>",
"date": "Fri, 27 Feb 2026 10:04:26 +0000",
"is_openbsd": false,
"thread_id": "20260227100426.2585191-8-alan.maguire@oracle.com.mbox.gz"
} |
lkml_critique | bpf | Update struct btf_header to add a new "layout" section containing
a description of how to parse the BTF kinds known about at BTF
encoding time. This provides the opportunity for tools that might
not know all of these kinds - as is the case when older tools run
on more newly-generated BTF - to still parse the BTF provi... | null | null | null | [PATCH v10 bpf-next 00/10] Add BTF layout to BTF | [ ... ]
Does this example reflect actual tool output? A few values appear
inconsistent with the implementation in dump_btf_meta() and the
layout encoding in libbpf:
The kind layout values are all zeros, but the layouts[] array in
tools/lib/bpf/btf.c populates non-zero values for known kinds:
[BTF_KIND_INT] = {... | {
"author": "bot+bpf-ci@kernel.org",
"date": "Fri, 27 Feb 2026 10:52:04 +0000 (UTC)",
"is_openbsd": false,
"thread_id": "20260227100426.2585191-8-alan.maguire@oracle.com.mbox.gz"
} |
lkml_critique | bpf | Update struct btf_header to add a new "layout" section containing
a description of how to parse the BTF kinds known about at BTF
encoding time. This provides the opportunity for tools that might
not know all of these kinds - as is the case when older tools run
on more newly-generated BTF - to still parse the BTF provi... | null | null | null | [PATCH v10 bpf-next 00/10] Add BTF layout to BTF | [ ... ]
Adding these two fields changes sizeof(struct btf_header) from 24
to 32 bytes. In libbpf's btf_parse_hdr(), the non-native endian
path has a strict equality check:
tools/lib/bpf/btf.c:btf_parse_hdr() {
if (hdr->magic == bswap_16(BTF_MAGIC)) {
btf->swapped_endian = true;
if (bswap_32(hdr->... | {
"author": "bot+bpf-ci@kernel.org",
"date": "Fri, 27 Feb 2026 10:52:07 +0000 (UTC)",
"is_openbsd": false,
"thread_id": "20260227100426.2585191-8-alan.maguire@oracle.com.mbox.gz"
} |
lkml_critique | bpf | Update struct btf_header to add a new "layout" section containing
a description of how to parse the BTF kinds known about at BTF
encoding time. This provides the opportunity for tools that might
not know all of these kinds - as is the case when older tools run
on more newly-generated BTF - to still parse the BTF provi... | null | null | null | [PATCH v10 bpf-next 00/10] Add BTF layout to BTF | [ ... ]
Should layout_len also be checked for alignment to
sizeof(struct btf_layout)? The libbpf counterpart in
btf_parse_layout_sec() validates this:
if (btf->hdr.layout_len % sizeof(struct btf_layout) != 0) {
pr_debug("Invalid BTF kind layout section\n");
return -EINVAL;
}
Without this ch... | {
"author": "bot+bpf-ci@kernel.org",
"date": "Fri, 27 Feb 2026 10:52:11 +0000 (UTC)",
"is_openbsd": false,
"thread_id": "20260227100426.2585191-8-alan.maguire@oracle.com.mbox.gz"
} |
lkml_critique | bpf | Update struct btf_header to add a new "layout" section containing
a description of how to parse the BTF kinds known about at BTF
encoding time. This provides the opportunity for tools that might
not know all of these kinds - as is the case when older tools run
on more newly-generated BTF - to still parse the BTF provi... | null | null | null | [PATCH v10 bpf-next 00/10] Add BTF layout to BTF | [ ... ]
Could the read of hdr->hdr_len at offset 4 above be an out-of-bounds
access when raw_size is less than 8?
The previous code set hdr as a pointer without dereferencing it, then
checked raw_size before accessing any header fields. The new code
reads hdr->hdr_len before the raw_size check.
btf_new() calls btf... | {
"author": "bot+bpf-ci@kernel.org",
"date": "Fri, 27 Feb 2026 10:52:14 +0000 (UTC)",
"is_openbsd": false,
"thread_id": "20260227100426.2585191-8-alan.maguire@oracle.com.mbox.gz"
} |
lkml_critique | bpf | Update struct btf_header to add a new "layout" section containing
a description of how to parse the BTF kinds known about at BTF
encoding time. This provides the opportunity for tools that might
not know all of these kinds - as is the case when older tools run
on more newly-generated BTF - to still parse the BTF provi... | null | null | null | [PATCH v10 bpf-next 00/10] Add BTF layout to BTF | On 27/02/2026 10:52, bot+bpf-ci@kernel.org wrote:
In order to handle all the fallout of the header size change
in a 100% bisect-friendly way it would be necessary to squash patches
1,2 and 6 in this series into a single patch dealing with the UAPI,
libbpf and kernel handling of same. I'm open to doing this,
but am co... | {
"author": "Alan Maguire <alan.maguire@oracle.com>",
"date": "Fri, 27 Feb 2026 13:35:27 +0000",
"is_openbsd": false,
"thread_id": "20260227100426.2585191-8-alan.maguire@oracle.com.mbox.gz"
} |
lkml_critique | bpf | Fix the warning:
BUG: using smp_processor_id() in preemptible [00000000] code: sys
temd/1
caller is larch_insn_text_copy+0x40/0xf0
Simply changing it to raw_smp_processor_id() is not enough: if preempt
and CPU hotplug happens after raw_smp_processor_id() but before
stop_machine(), the CPU where raw_smp_proces... | null | null | null | [PATCH v2] LoongArch: Fix calling smp_processor_id() in preemptible code | On Fri, Feb 27, 2026 at 4:04 PM Xi Ruoyao <xry111@xry111.site> wrote:
I think you should include the P.S. part from v1 in the commit message. | {
"author": "Hengqi Chen <hengqi.chen@gmail.com>",
"date": "Fri, 27 Feb 2026 17:59:02 +0800",
"is_openbsd": false,
"thread_id": "CAEyhmHTeDvWu1cZv59c80eZ31KjRtcXLcXuXphJ6_=oBk4rmZw@mail.gmail.com.mbox.gz"
} |
lkml_critique | bpf | Changelog:
v4: https://lore.kernel.org/all/20260224212535.1165151-1-puranjay@kernel.org/
Changes in v4 -> v5:
- Base the commits over bpf/master and not bpf-next/master
- Rename KF_FORBID_SLEEP to KF_FORBID_FAULT: mmap_lock is a sleeping
lock (rw_semaphore), so the actual constraint is about faulting (which
would ... | null | null | null | [PATCH bpf v5 0/8] Introduce KF_FORBID_FAULT modifier for acquire/release kfuncs | Some iterators hold resources (like mmap_lock in task_vma) that prevent
sleeping. To allow BPF programs to release such resources mid-iteration
and call sleepable helpers, the verifier needs to track acquire/release
semantics on iterator _next pointers.
Repurpose the st->id field on STACK_ITER slots to track the ref_o... | {
"author": "Puranjay Mohan <puranjay@kernel.org>",
"date": "Thu, 26 Feb 2026 08:14:50 -0800",
"is_openbsd": false,
"thread_id": "20260226161500.775715-4-puranjay@kernel.org.mbox.gz"
} |
lkml_critique | bpf | Changelog:
v4: https://lore.kernel.org/all/20260224212535.1165151-1-puranjay@kernel.org/
Changes in v4 -> v5:
- Base the commits over bpf/master and not bpf-next/master
- Rename KF_FORBID_SLEEP to KF_FORBID_FAULT: mmap_lock is a sleeping
lock (rw_semaphore), so the actual constraint is about faulting (which
would ... | null | null | null | [PATCH bpf v5 0/8] Introduce KF_FORBID_FAULT modifier for acquire/release kfuncs | check_helper_call() prints the error message for every
env->cur_state->active* element when calling a sleepable helper.
Consolidate all of them into a single print statement.
The check for env->cur_state->active_locks was not part of the removed
print statements and will not be triggered with the consolidated print
as... | {
"author": "Puranjay Mohan <puranjay@kernel.org>",
"date": "Thu, 26 Feb 2026 08:14:51 -0800",
"is_openbsd": false,
"thread_id": "20260226161500.775715-4-puranjay@kernel.org.mbox.gz"
} |
lkml_critique | bpf | Changelog:
v4: https://lore.kernel.org/all/20260224212535.1165151-1-puranjay@kernel.org/
Changes in v4 -> v5:
- Base the commits over bpf/master and not bpf-next/master
- Rename KF_FORBID_SLEEP to KF_FORBID_FAULT: mmap_lock is a sleeping
lock (rw_semaphore), so the actual constraint is about faulting (which
would ... | null | null | null | [PATCH bpf v5 0/8] Introduce KF_FORBID_FAULT modifier for acquire/release kfuncs | check_kfunc_call() has multiple scattered checks that reject sleepable
kfuncs in various non-sleepable contexts (RCU, preempt-disabled, IRQ-
disabled). These are the same conditions already checked by
in_sleepable_context(), so replace them with a single consolidated
check.
This also simplifies the preempt lock tracki... | {
"author": "Puranjay Mohan <puranjay@kernel.org>",
"date": "Thu, 26 Feb 2026 08:14:52 -0800",
"is_openbsd": false,
"thread_id": "20260226161500.775715-4-puranjay@kernel.org.mbox.gz"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.