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 | lkml | Geert reports that enabling CONFIG_KUNIT_ALL_TESTS shouldn't enable
features that aren't enabled without it. That isn't what "*all* tests"
means, but as the prompt puts it, "All KUnit tests with satisfied
dependencies".
The impact is that enabling CONFIG_KUNIT_ALL_TESTS brings features which
cannot be disabled as buil... | null | null | null | [PATCH phy-fixes] phy: make PHY_COMMON_PROPS Kconfig symbol conditionally user-selectable | On Thu, 26 Feb 2026 17:33:15 +0200, Vladimir Oltean wrote:
Applied, thanks!
[1/1] phy: make PHY_COMMON_PROPS Kconfig symbol conditionally user-selectable
commit: 48fafffcf29bb968c9dee6bf507c1e57d0ccb6b5
Best regards,
--
~Vinod | {
"author": "Vinod Koul <vkoul@kernel.org>",
"date": "Fri, 27 Feb 2026 20:55:07 +0530",
"is_openbsd": false,
"thread_id": "177220590775.320398.10026111548101706092.b4-ty@kernel.org.mbox.gz"
} |
lkml_critique | lkml | When a font is set on an invisible console, the screen will not update.
However, the fontbuffer is not updated to match the new font dimensions.
This inconsistency leads to out-of-bounds memory access when writing to
the tty bound to fbcon, as demonstrated by the following KASAN report:
BUG: KASAN: slab-out-of-bounds... | null | null | null | [RFC PATCH] fbcon: Fix out-of-bounds memory in fbcon_putcs | $B:_(B 2026/2/27 22:50, chenjun (AM) $B<LF;(B:
There is a poc:
```
#define _GNU_SOURCE
#include <errno.h>
#include <fcntl.h>
#include <stdlib.h>
#include <unistd.h>
#include <stdint.h>
#include <sys/ioctl.h>
#include <linux/capability.h>
char my_font_data[512 * 1 * 32 * 32];
struct console_font_op {
u... | {
"author": "\"chenjun (AM)\" <chenjun102@huawei.com>",
"date": "Fri, 27 Feb 2026 14:53:42 +0000",
"is_openbsd": false,
"thread_id": "e300c23760df488aaaa0648c4593c802@huawei.com.mbox.gz"
} |
lkml_critique | lkml | When mapping scatter-gather entries that reference reserved
memory regions without struct page backing (e.g., bootloader created
carveouts), is_pci_p2pdma_page() dereferences the page pointer
returned by sg_page() without first verifying its validity.
This causes a kernel paging fault when CONFIG_PCI_P2PDMA is enabled... | null | null | null | [PATCH RFC] iommu/dma: Validate page before accessing P2PDMA state | On Tue, Feb 24, 2026 at 10:42:57AM +0000, Ashish Mhetre wrote:
I believe this behavior started after commit 88df6ab2f34b
("mm: add folio_is_pci_p2pdma()"). Prior to that change, the
is_zone_device_page(page) check would return false when given a
non‑existent page pointer.
If any fix is needed, the is_pci_p2pdma_pag... | {
"author": "Leon Romanovsky <leon@kernel.org>",
"date": "Tue, 24 Feb 2026 14:32:21 +0200",
"is_openbsd": false,
"thread_id": "20260227141330.GK5933@nvidia.com.mbox.gz"
} |
lkml_critique | lkml | When mapping scatter-gather entries that reference reserved
memory regions without struct page backing (e.g., bootloader created
carveouts), is_pci_p2pdma_page() dereferences the page pointer
returned by sg_page() without first verifying its validity.
This causes a kernel paging fault when CONFIG_PCI_P2PDMA is enabled... | null | null | null | [PATCH RFC] iommu/dma: Validate page before accessing P2PDMA state | On Tue, Feb 24, 2026 at 02:32:21PM +0200, Leon Romanovsky wrote:
Doesn't folio_is_pci_p2pdma() also check for zone device?
I see[1] that it does:
static inline bool folio_is_pci_p2pdma(const struct folio *folio)
{
return IS_ENABLED(CONFIG_PCI_P2PDMA) &&
folio_is_zone_device(folio) &&
folio->pgmap->type == MEMORY... | {
"author": "Pranjal Shrivastava <praan@google.com>",
"date": "Tue, 24 Feb 2026 20:57:56 +0000",
"is_openbsd": false,
"thread_id": "20260227141330.GK5933@nvidia.com.mbox.gz"
} |
lkml_critique | lkml | When mapping scatter-gather entries that reference reserved
memory regions without struct page backing (e.g., bootloader created
carveouts), is_pci_p2pdma_page() dereferences the page pointer
returned by sg_page() without first verifying its validity.
This causes a kernel paging fault when CONFIG_PCI_P2PDMA is enabled... | null | null | null | [PATCH RFC] iommu/dma: Validate page before accessing P2PDMA state | On 2/25/2026 2:27 AM, Pranjal Shrivastava wrote:
Thanks Leon for the review. This crash started after commit 30280eee2db1
("iommu/dma: support PCI P2PDMA pages in dma-iommu map_sg").
Yes, this will also fix the crash.
Thanks for the feedback, Pranjal.
To clarify: are you suggesting we handle non-page-backed mappi... | {
"author": "Ashish Mhetre <amhetre@nvidia.com>",
"date": "Wed, 25 Feb 2026 10:19:41 +0530",
"is_openbsd": false,
"thread_id": "20260227141330.GK5933@nvidia.com.mbox.gz"
} |
lkml_critique | lkml | When mapping scatter-gather entries that reference reserved
memory regions without struct page backing (e.g., bootloader created
carveouts), is_pci_p2pdma_page() dereferences the page pointer
returned by sg_page() without first verifying its validity.
This causes a kernel paging fault when CONFIG_PCI_P2PDMA is enabled... | null | null | null | [PATCH RFC] iommu/dma: Validate page before accessing P2PDMA state | On Tue, Feb 24, 2026 at 08:57:56PM +0000, Pranjal Shrivastava wrote:
Yes, i came to the same conclusion, just explained why it worked before.
pfn_valid() is a relatively expensive function [1] to invoke in the data path,
and is_pci_p2pdma_page() ends up being called in these execution flows.
[1] https://elixir.boot... | {
"author": "Leon Romanovsky <leon@kernel.org>",
"date": "Wed, 25 Feb 2026 09:50:00 +0200",
"is_openbsd": false,
"thread_id": "20260227141330.GK5933@nvidia.com.mbox.gz"
} |
lkml_critique | lkml | When mapping scatter-gather entries that reference reserved
memory regions without struct page backing (e.g., bootloader created
carveouts), is_pci_p2pdma_page() dereferences the page pointer
returned by sg_page() without first verifying its validity.
This causes a kernel paging fault when CONFIG_PCI_P2PDMA is enabled... | null | null | null | [PATCH RFC] iommu/dma: Validate page before accessing P2PDMA state | On Wed, Feb 25, 2026 at 10:19:41AM +0530, Ashish Mhetre wrote:
The latter one.
The bug is in callers which used wrong API, they need to be adapted.
Thanks | {
"author": "Leon Romanovsky <leon@kernel.org>",
"date": "Wed, 25 Feb 2026 09:56:09 +0200",
"is_openbsd": false,
"thread_id": "20260227141330.GK5933@nvidia.com.mbox.gz"
} |
lkml_critique | lkml | When mapping scatter-gather entries that reference reserved
memory regions without struct page backing (e.g., bootloader created
carveouts), is_pci_p2pdma_page() dereferences the page pointer
returned by sg_page() without first verifying its validity.
This causes a kernel paging fault when CONFIG_PCI_P2PDMA is enabled... | null | null | null | [PATCH RFC] iommu/dma: Validate page before accessing P2PDMA state | On Wed, Feb 25, 2026 at 09:56:09AM +0200, Leon Romanovsky wrote:
Yup, I meant the latter.
Yes, the thing is, if the caller already knows that the region to be
mapped is NOT struct page-backed, then why does it use dma_map_sg
variants?
Thanks
Praan | {
"author": "Pranjal Shrivastava <praan@google.com>",
"date": "Wed, 25 Feb 2026 20:11:29 +0000",
"is_openbsd": false,
"thread_id": "20260227141330.GK5933@nvidia.com.mbox.gz"
} |
lkml_critique | lkml | When mapping scatter-gather entries that reference reserved
memory regions without struct page backing (e.g., bootloader created
carveouts), is_pci_p2pdma_page() dereferences the page pointer
returned by sg_page() without first verifying its validity.
This causes a kernel paging fault when CONFIG_PCI_P2PDMA is enabled... | null | null | null | [PATCH RFC] iommu/dma: Validate page before accessing P2PDMA state | On Wed, Feb 25, 2026 at 09:50:00AM +0200, Leon Romanovsky wrote:
Ack.
Right, that makes sense. Ideally, it shouldn't be there at either of the
places (iommu_dma_map_sg or is_pci_p2pdma_page()).
[--->8---]
Thanks,
Praan | {
"author": "Pranjal Shrivastava <praan@google.com>",
"date": "Wed, 25 Feb 2026 20:15:24 +0000",
"is_openbsd": false,
"thread_id": "20260227141330.GK5933@nvidia.com.mbox.gz"
} |
lkml_critique | lkml | When mapping scatter-gather entries that reference reserved
memory regions without struct page backing (e.g., bootloader created
carveouts), is_pci_p2pdma_page() dereferences the page pointer
returned by sg_page() without first verifying its validity.
This causes a kernel paging fault when CONFIG_PCI_P2PDMA is enabled... | null | null | null | [PATCH RFC] iommu/dma: Validate page before accessing P2PDMA state | On Wed, Feb 25, 2026 at 08:11:29PM +0000, Pranjal Shrivastava wrote:
Before dma_map_phys() was added, there was no reliable way to DMA‑map
such memory, and using dma_map_sg() was a workaround that happened to
work. I'm not sure whether it worked by design or by accident, but the
correct approach now is to use dma_map_... | {
"author": "Leon Romanovsky <leon@kernel.org>",
"date": "Thu, 26 Feb 2026 09:58:06 +0200",
"is_openbsd": false,
"thread_id": "20260227141330.GK5933@nvidia.com.mbox.gz"
} |
lkml_critique | lkml | When mapping scatter-gather entries that reference reserved
memory regions without struct page backing (e.g., bootloader created
carveouts), is_pci_p2pdma_page() dereferences the page pointer
returned by sg_page() without first verifying its validity.
This causes a kernel paging fault when CONFIG_PCI_P2PDMA is enabled... | null | null | null | [PATCH RFC] iommu/dma: Validate page before accessing P2PDMA state | On 2/26/2026 1:28 PM, Leon Romanovsky wrote:
Thanks Leon and Pranjal for the detailed feedback. I'll update our
callers to use
dma_map_phys() for non-page-backed buffers.
One question: would it make sense to add a check in iommu_dma_map_sg to
fail gracefully when non-page-backed buffers are passed, instead of crashi... | {
"author": "Ashish Mhetre <amhetre@nvidia.com>",
"date": "Fri, 27 Feb 2026 11:16:02 +0530",
"is_openbsd": false,
"thread_id": "20260227141330.GK5933@nvidia.com.mbox.gz"
} |
lkml_critique | lkml | When mapping scatter-gather entries that reference reserved
memory regions without struct page backing (e.g., bootloader created
carveouts), is_pci_p2pdma_page() dereferences the page pointer
returned by sg_page() without first verifying its validity.
This causes a kernel paging fault when CONFIG_PCI_P2PDMA is enabled... | null | null | null | [PATCH RFC] iommu/dma: Validate page before accessing P2PDMA state | On 2026-02-27 5:46 am, Ashish Mhetre wrote:
No, it is the responsibility of drivers not to abuse kernel APIs
inappropriately. Checking for misuse adds overhead that penalises
correct users. dma_map_page/sg on non-page-backed memory has never been
valid, and it would only have been system-configuration-dependent luc... | {
"author": "Robin Murphy <robin.murphy@arm.com>",
"date": "Fri, 27 Feb 2026 14:05:01 +0000",
"is_openbsd": false,
"thread_id": "20260227141330.GK5933@nvidia.com.mbox.gz"
} |
lkml_critique | lkml | When mapping scatter-gather entries that reference reserved
memory regions without struct page backing (e.g., bootloader created
carveouts), is_pci_p2pdma_page() dereferences the page pointer
returned by sg_page() without first verifying its validity.
This causes a kernel paging fault when CONFIG_PCI_P2PDMA is enabled... | null | null | null | [PATCH RFC] iommu/dma: Validate page before accessing P2PDMA state | On Fri, Feb 27, 2026 at 11:16:02AM +0530, Ashish Mhetre wrote:
Ack.
In my opinion, the answer is no, since this is almost like the "should
the kernel protect developers from themselves" debate.. we should be a
little dramatic to make sure the developer doesn't call the wrong API.
Sure, we could return a DMA_MAPPING_... | {
"author": "Pranjal Shrivastava <praan@google.com>",
"date": "Fri, 27 Feb 2026 14:08:42 +0000",
"is_openbsd": false,
"thread_id": "20260227141330.GK5933@nvidia.com.mbox.gz"
} |
lkml_critique | lkml | When mapping scatter-gather entries that reference reserved
memory regions without struct page backing (e.g., bootloader created
carveouts), is_pci_p2pdma_page() dereferences the page pointer
returned by sg_page() without first verifying its validity.
This causes a kernel paging fault when CONFIG_PCI_P2PDMA is enabled... | null | null | null | [PATCH RFC] iommu/dma: Validate page before accessing P2PDMA state | On Fri, Feb 27, 2026 at 02:08:42PM +0000, Pranjal Shrivastava wrote:
This is absolutely illegal and a driver bug to put non-struct page
memory into a scatter list. It was never an acceptable "work
around". What driver is doing this??
If you want to improve robustness add some pfn_valid/etc checks under
the CONFING D... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Fri, 27 Feb 2026 10:13:30 -0400",
"is_openbsd": false,
"thread_id": "20260227141330.GK5933@nvidia.com.mbox.gz"
} |
lkml_critique | lkml | Export (and rename) extend_arg() and fuse_ext_size() as these functions
are useful for using extension headers in other places.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++-------
fs/fuse/fuse_i.h | 7 +++++++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c... | null | null | null | [RFC PATCH v3 2/8] fuse: export extend_arg() and factor out fuse_ext_size() | Remove the fuse_conn argument from function fuse_lookup_init() as it isn't
used since commit 21f621741a77 ("fuse: fix LOOKUP vs INIT compat handling").
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/fs/fuse/dir.c b/fs/fuse... | {
"author": "Luis Henriques <luis@igalia.com>",
"date": "Wed, 25 Feb 2026 11:24:35 +0000",
"is_openbsd": false,
"thread_id": "20260225112439.27276-1-luis@igalia.com.mbox.gz"
} |
lkml_critique | lkml | Export (and rename) extend_arg() and fuse_ext_size() as these functions
are useful for using extension headers in other places.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++-------
fs/fuse/fuse_i.h | 7 +++++++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c... | null | null | null | [RFC PATCH v3 2/8] fuse: export extend_arg() and factor out fuse_ext_size() | Allow fuse_open_args_fill() fuction to be used from different files.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/file.c | 2 +-
fs/fuse/fuse_i.h | 10 +++++++---
2 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/fs/fuse/file.c b/fs/fuse/file.c
index 1045d74dd95f..ea9023150a38 100644
--... | {
"author": "Luis Henriques <luis@igalia.com>",
"date": "Wed, 25 Feb 2026 11:24:38 +0000",
"is_openbsd": false,
"thread_id": "20260225112439.27276-1-luis@igalia.com.mbox.gz"
} |
lkml_critique | lkml | Export (and rename) extend_arg() and fuse_ext_size() as these functions
are useful for using extension headers in other places.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++-------
fs/fuse/fuse_i.h | 7 +++++++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c... | null | null | null | [RFC PATCH v3 2/8] fuse: export extend_arg() and factor out fuse_ext_size() | fuse_lookup_name() requires a struct fuse_entry_out to be passed in.
However, the only caller that really needs it is fuse_lookup(). And even
this function only cares about the dentry time.
This patch simplifies fuse_lookup_name() so that it doesn't require a struct
as a parameter, replacing it by a local variable. ... | {
"author": "Luis Henriques <luis@igalia.com>",
"date": "Wed, 25 Feb 2026 11:24:32 +0000",
"is_openbsd": false,
"thread_id": "20260225112439.27276-1-luis@igalia.com.mbox.gz"
} |
lkml_critique | lkml | Export (and rename) extend_arg() and fuse_ext_size() as these functions
are useful for using extension headers in other places.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++-------
fs/fuse/fuse_i.h | 7 +++++++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c... | null | null | null | [RFC PATCH v3 2/8] fuse: export extend_arg() and factor out fuse_ext_size() | Split function fuse_do_statx(), so that we get two helper functions: one
to initialise the arguments and another to update the attributes and
statistics. This will allow compound operations to re-use these two helpers.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 88 +++++++++++++++++++++++++++... | {
"author": "Luis Henriques <luis@igalia.com>",
"date": "Wed, 25 Feb 2026 11:24:36 +0000",
"is_openbsd": false,
"thread_id": "20260225112439.27276-1-luis@igalia.com.mbox.gz"
} |
lkml_critique | lkml | Export (and rename) extend_arg() and fuse_ext_size() as these functions
are useful for using extension headers in other places.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++-------
fs/fuse/fuse_i.h | 7 +++++++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c... | null | null | null | [RFC PATCH v3 2/8] fuse: export extend_arg() and factor out fuse_ext_size() | Hi,
I'm sending a new version of my work on lookup_handle, even though it's
still incomplete. As suggested elsewhere, it is now based on compound
commands and thus it sits on top of Horst's patchset [0]. Also, because
this version is a complete re-write of the approach presented in my previous
RFC [1] I'm not going ... | {
"author": "Luis Henriques <luis@igalia.com>",
"date": "Wed, 25 Feb 2026 11:24:31 +0000",
"is_openbsd": false,
"thread_id": "20260225112439.27276-1-luis@igalia.com.mbox.gz"
} |
lkml_critique | lkml | Export (and rename) extend_arg() and fuse_ext_size() as these functions
are useful for using extension headers in other places.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++-------
fs/fuse/fuse_i.h | 7 +++++++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c... | null | null | null | [RFC PATCH v3 2/8] fuse: export extend_arg() and factor out fuse_ext_size() | Operations that have a variable length argument assume that it will always
be the last argument on the list. This patch allows this assumption to be
removed by keeping track of the index of variable length argument.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/compound.c | 1 +
fs/fuse/cuse.c | ... | {
"author": "Luis Henriques <luis@igalia.com>",
"date": "Wed, 25 Feb 2026 11:24:34 +0000",
"is_openbsd": false,
"thread_id": "20260225112439.27276-1-luis@igalia.com.mbox.gz"
} |
lkml_critique | lkml | Export (and rename) extend_arg() and fuse_ext_size() as these functions
are useful for using extension headers in other places.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++-------
fs/fuse/fuse_i.h | 7 +++++++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c... | null | null | null | [RFC PATCH v3 2/8] fuse: export extend_arg() and factor out fuse_ext_size() | The implementation of this compound operation allows atomic_open() to use
file handle. It also introduces a new MKOBJ_HANDLE operation that will
handle the file system object creation and will return the file handle.
The atomicity of the operation (create + open) needs to be handled in
user-space (e.g. the handling o... | {
"author": "Luis Henriques <luis@igalia.com>",
"date": "Wed, 25 Feb 2026 11:24:39 +0000",
"is_openbsd": false,
"thread_id": "20260225112439.27276-1-luis@igalia.com.mbox.gz"
} |
lkml_critique | lkml | Export (and rename) extend_arg() and fuse_ext_size() as these functions
are useful for using extension headers in other places.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++-------
fs/fuse/fuse_i.h | 7 +++++++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c... | null | null | null | [RFC PATCH v3 2/8] fuse: export extend_arg() and factor out fuse_ext_size() | The implementation of lookup_handle+statx compound operation extends the
lookup operation so that a file handle is be passed into the kernel. It
also needs to include an extra inarg, so that the parent directory file
handle can be sent to user-space. This extra inarg is added as an extension
header to the request.
B... | {
"author": "Luis Henriques <luis@igalia.com>",
"date": "Wed, 25 Feb 2026 11:24:37 +0000",
"is_openbsd": false,
"thread_id": "20260225112439.27276-1-luis@igalia.com.mbox.gz"
} |
lkml_critique | lkml | Export (and rename) extend_arg() and fuse_ext_size() as these functions
are useful for using extension headers in other places.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++-------
fs/fuse/fuse_i.h | 7 +++++++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c... | null | null | null | [RFC PATCH v3 2/8] fuse: export extend_arg() and factor out fuse_ext_size() | On Wed, Feb 25, 2026 at 11:24:31AM +0000, Luis Henriques wrote:
I, personally, appreciate the fact that you sent this out, so I can understand how
you are using the compounds for this real world problem, and it gives me confidence
that I'm not completely off with the compounds.
Do you by any chance have implemented ... | {
"author": "Horst Birthelmer <horst@birthelmer.de>",
"date": "Wed, 25 Feb 2026 16:14:56 +0100",
"is_openbsd": false,
"thread_id": "20260225112439.27276-1-luis@igalia.com.mbox.gz"
} |
lkml_critique | lkml | Export (and rename) extend_arg() and fuse_ext_size() as these functions
are useful for using extension headers in other places.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++-------
fs/fuse/fuse_i.h | 7 +++++++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c... | null | null | null | [RFC PATCH v3 2/8] fuse: export extend_arg() and factor out fuse_ext_size() | Hi Luis,
On Wed, Feb 25, 2026 at 11:24:39AM +0000, Luis Henriques wrote:
Just to clarify for myself and maybe others.
You want this to be processed atomic on the fuse server and never
be separated by the upcoming 'decode and send separate' code in the
kernel?
Is that really necessarry? What would the consequences be,... | {
"author": "Horst Birthelmer <horst@birthelmer.de>",
"date": "Wed, 25 Feb 2026 16:08:10 +0100",
"is_openbsd": false,
"thread_id": "20260225112439.27276-1-luis@igalia.com.mbox.gz"
} |
lkml_critique | lkml | Export (and rename) extend_arg() and fuse_ext_size() as these functions
are useful for using extension headers in other places.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++-------
fs/fuse/fuse_i.h | 7 +++++++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c... | null | null | null | [RFC PATCH v3 2/8] fuse: export extend_arg() and factor out fuse_ext_size() | Hey Horst,
On Wed, Feb 25 2026, Horst Birthelmer wrote:
I do have _something_ for testing, yes. Obviously, I will eventually
share it but I wasn't planning to share it at this stage yet (it's ugly
and full of debug code). But if you'd like to have a look I can do a quick
clean-up and push it somewhere.
Cheers,
--... | {
"author": "Luis Henriques <luis@igalia.com>",
"date": "Wed, 25 Feb 2026 17:06:08 +0000",
"is_openbsd": false,
"thread_id": "20260225112439.27276-1-luis@igalia.com.mbox.gz"
} |
lkml_critique | lkml | Export (and rename) extend_arg() and fuse_ext_size() as these functions
are useful for using extension headers in other places.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++-------
fs/fuse/fuse_i.h | 7 +++++++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c... | null | null | null | [RFC PATCH v3 2/8] fuse: export extend_arg() and factor out fuse_ext_size() | Hi!
On Wed, Feb 25 2026, Horst Birthelmer wrote:
No, you're right -- it's unlikely that this flag is required. If I
remember correctly from the discussion, the flags and what they mean is
one of the things still not written in stone for the compound operations,
right?
Regarding this compound specifically, what I w... | {
"author": "Luis Henriques <luis@igalia.com>",
"date": "Wed, 25 Feb 2026 17:26:45 +0000",
"is_openbsd": false,
"thread_id": "20260225112439.27276-1-luis@igalia.com.mbox.gz"
} |
lkml_critique | lkml | Export (and rename) extend_arg() and fuse_ext_size() as these functions
are useful for using extension headers in other places.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++-------
fs/fuse/fuse_i.h | 7 +++++++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c... | null | null | null | [RFC PATCH v3 2/8] fuse: export extend_arg() and factor out fuse_ext_size() | On Wed, Feb 25, 2026 at 12:25 PM Luis Henriques <luis@igalia.com> wrote:
Considering that fuse has long used uint64_t fh as the convention
for a file id all over the code, it would be better to pick a different
convention for fuse file handle, perhaps ffh, or fhandle?
I don't remember what we concluded last time, bu... | {
"author": "Amir Goldstein <amir73il@gmail.com>",
"date": "Wed, 25 Feb 2026 19:06:39 +0100",
"is_openbsd": false,
"thread_id": "20260225112439.27276-1-luis@igalia.com.mbox.gz"
} |
lkml_critique | lkml | Export (and rename) extend_arg() and fuse_ext_size() as these functions
are useful for using extension headers in other places.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++-------
fs/fuse/fuse_i.h | 7 +++++++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c... | null | null | null | [RFC PATCH v3 2/8] fuse: export extend_arg() and factor out fuse_ext_size() | Hi Amir,
On Wed, Feb 25 2026, Amir Goldstein wrote:
Good point, I'll make sure next revision will follow a different
convention.
You're right, I should have pointed that out in the cover letter at least.
In the previous version that maximum size was indeed provided by the
server. But from the discussion here [0] ... | {
"author": "Luis Henriques <luis@igalia.com>",
"date": "Thu, 26 Feb 2026 09:54:53 +0000",
"is_openbsd": false,
"thread_id": "20260225112439.27276-1-luis@igalia.com.mbox.gz"
} |
lkml_critique | lkml | Export (and rename) extend_arg() and fuse_ext_size() as these functions
are useful for using extension headers in other places.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++-------
fs/fuse/fuse_i.h | 7 +++++++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c... | null | null | null | [RFC PATCH v3 2/8] fuse: export extend_arg() and factor out fuse_ext_size() | On Thu, Feb 26, 2026 at 10:54 AM Luis Henriques <luis@igalia.com> wrote:
file handle on stack only makes sense for small pre allocated size.
If the server has full control over handle size, then that is not relevant.
At some point we will need to address the fact that the most common
case is for very small file handl... | {
"author": "Amir Goldstein <amir73il@gmail.com>",
"date": "Thu, 26 Feb 2026 11:08:02 +0100",
"is_openbsd": false,
"thread_id": "20260225112439.27276-1-luis@igalia.com.mbox.gz"
} |
lkml_critique | lkml | Export (and rename) extend_arg() and fuse_ext_size() as these functions
are useful for using extension headers in other places.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++-------
fs/fuse/fuse_i.h | 7 +++++++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c... | null | null | null | [RFC PATCH v3 2/8] fuse: export extend_arg() and factor out fuse_ext_size() | On Thu, 26 Feb 2026 at 11:08, Amir Goldstein <amir73il@gmail.com> wrote:
I thought the point was that the file handle is available in
fi->handle and doesn't need to be allocated/copied. Instead
extensions could be done with an argument vector, like this:
--- a/fs/fuse/fuse_i.h
+++ b/fs/fuse/fuse_i.h
@@ -326,6 +326... | {
"author": "Miklos Szeredi <miklos@szeredi.hu>",
"date": "Thu, 26 Feb 2026 11:29:42 +0100",
"is_openbsd": false,
"thread_id": "20260225112439.27276-1-luis@igalia.com.mbox.gz"
} |
lkml_critique | lkml | Export (and rename) extend_arg() and fuse_ext_size() as these functions
are useful for using extension headers in other places.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++-------
fs/fuse/fuse_i.h | 7 +++++++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c... | null | null | null | [RFC PATCH v3 2/8] fuse: export extend_arg() and factor out fuse_ext_size() | On Thu, Feb 26 2026, Amir Goldstein wrote:
Thanks, I had took a look into it before -- I think you had pointed it to
me!. But I agree that this is something that can be handled once I have
most of the other things sorted out.
Cheers,
--
Luís | {
"author": "Luis Henriques <luis@igalia.com>",
"date": "Thu, 26 Feb 2026 10:33:01 +0000",
"is_openbsd": false,
"thread_id": "20260225112439.27276-1-luis@igalia.com.mbox.gz"
} |
lkml_critique | lkml | Export (and rename) extend_arg() and fuse_ext_size() as these functions
are useful for using extension headers in other places.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++-------
fs/fuse/fuse_i.h | 7 +++++++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c... | null | null | null | [RFC PATCH v3 2/8] fuse: export extend_arg() and factor out fuse_ext_size() | On Thu, Feb 26 2026, Miklos Szeredi wrote:
Right now the code is using extensions in the lookup_handle operation
inargs, and only if a file handle is available for the parent inode.
Are you saying that outargs should also use extensions for getting the
file handle in a lookup_handle?
Cheers,
--
Luís | {
"author": "Luis Henriques <luis@igalia.com>",
"date": "Thu, 26 Feb 2026 15:06:51 +0000",
"is_openbsd": false,
"thread_id": "20260225112439.27276-1-luis@igalia.com.mbox.gz"
} |
lkml_critique | lkml | Export (and rename) extend_arg() and fuse_ext_size() as these functions
are useful for using extension headers in other places.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++-------
fs/fuse/fuse_i.h | 7 +++++++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c... | null | null | null | [RFC PATCH v3 2/8] fuse: export extend_arg() and factor out fuse_ext_size() | On Thu, 26 Feb 2026 at 16:07, Luis Henriques <luis@igalia.com> wrote:
No.
I'm saying that extend_arg() thing is messy and a using vectored args
for extensions (same as we do for normal input arguments) might be
better.
Thanks,
Miklos | {
"author": "Miklos Szeredi <miklos@szeredi.hu>",
"date": "Thu, 26 Feb 2026 16:44:45 +0100",
"is_openbsd": false,
"thread_id": "20260225112439.27276-1-luis@igalia.com.mbox.gz"
} |
lkml_critique | lkml | Export (and rename) extend_arg() and fuse_ext_size() as these functions
are useful for using extension headers in other places.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++-------
fs/fuse/fuse_i.h | 7 +++++++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c... | null | null | null | [RFC PATCH v3 2/8] fuse: export extend_arg() and factor out fuse_ext_size() | On Thu, Feb 26 2026, Miklos Szeredi wrote:
It is indeed a messy interface. I'll have a look into it and see how to
modify it to accommodate your suggestion. And thanks for your patience ;-)
Cheers,
--
Luís | {
"author": "Luis Henriques <luis@igalia.com>",
"date": "Thu, 26 Feb 2026 16:17:20 +0000",
"is_openbsd": false,
"thread_id": "20260225112439.27276-1-luis@igalia.com.mbox.gz"
} |
lkml_critique | lkml | Export (and rename) extend_arg() and fuse_ext_size() as these functions
are useful for using extension headers in other places.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++-------
fs/fuse/fuse_i.h | 7 +++++++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c... | null | null | null | [RFC PATCH v3 2/8] fuse: export extend_arg() and factor out fuse_ext_size() | On Wed, 25 Feb 2026 at 12:25, Luis Henriques <luis@igalia.com> wrote:
Example please.
Thanks,
Miklos | {
"author": "Miklos Szeredi <miklos@szeredi.hu>",
"date": "Fri, 27 Feb 2026 16:41:31 +0100",
"is_openbsd": false,
"thread_id": "20260225112439.27276-1-luis@igalia.com.mbox.gz"
} |
lkml_critique | lkml | Export (and rename) extend_arg() and fuse_ext_size() as these functions
are useful for using extension headers in other places.
Signed-off-by: Luis Henriques <luis@igalia.com>
---
fs/fuse/dir.c | 9 ++-------
fs/fuse/fuse_i.h | 7 +++++++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c... | null | null | null | [RFC PATCH v3 2/8] fuse: export extend_arg() and factor out fuse_ext_size() | On Wed, 25 Feb 2026 at 12:25, Luis Henriques <luis@igalia.com> wrote:
And now the timeout is skipped for the !outarg.nodeid case...
Thanks,
Miklos | {
"author": "Miklos Szeredi <miklos@szeredi.hu>",
"date": "Fri, 27 Feb 2026 16:46:43 +0100",
"is_openbsd": false,
"thread_id": "20260225112439.27276-1-luis@igalia.com.mbox.gz"
} |
lkml_critique | lkml | Move logical operators to the end of the previous line
to fix checkpatch warnings.
Signed-off-by: Mariyam Shahid <mariyam.shahid135@gmail.com>
---
drivers/staging/rtl8723bs/core/rtw_ap.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw_ap.c b/drivers/... | null | null | null | [PATCH] staging: rtl8723bs: Fix logical continuation placement | On Thu Feb 26, 2026 at 3:38 AM CST, Mariyam Shahid wrote:
...
This should be:
if (!(pmlmepriv->ht_op_mode & IEEE80211_HT_OP_MODE_NON_GF_STA_PRSNT) &&
pmlmepriv->num_sta_ht_no_gf) {
Also, my email is "ethantidmore06@gmail.com" I believe you used a wrong
email.
Thanks,
ET | {
"author": "\"Ethan Tidmore\" <ethantidmore06@gmail.com>",
"date": "Thu, 26 Feb 2026 19:31:34 -0600",
"is_openbsd": false,
"thread_id": "DGPUAEKP8SCX.3AUUXG0PMXF8H@gmail.com.mbox.gz"
} |
lkml_critique | lkml | Move logical operators to the end of the previous line
to fix checkpatch warnings.
Signed-off-by: Mariyam Shahid <mariyam.shahid135@gmail.com>
---
drivers/staging/rtl8723bs/core/rtw_ap.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw_ap.c b/drivers/... | null | null | null | [PATCH] staging: rtl8723bs: Fix logical continuation placement | On Thu, Feb 26, 2026 at 07:31:34PM -0600, Ethan Tidmore wrote:
Ideally, it would be aligned.
if (!(pmlmepriv->ht_op_mode & IEEE80211_HT_OP_MODE_NON_GF_STA_PRSNT) &&
pmlmepriv->num_sta_ht_no_gf) {
[tab][space * 4]pmlmepriv->num_sta_ht_no_gf) {
regards,
dan carpenter | {
"author": "Dan Carpenter <dan.carpenter@linaro.org>",
"date": "Fri, 27 Feb 2026 10:12:46 +0300",
"is_openbsd": false,
"thread_id": "DGPUAEKP8SCX.3AUUXG0PMXF8H@gmail.com.mbox.gz"
} |
lkml_critique | lkml | Move logical operators to the end of the previous line
to fix checkpatch warnings.
Signed-off-by: Mariyam Shahid <mariyam.shahid135@gmail.com>
---
drivers/staging/rtl8723bs/core/rtw_ap.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw_ap.c b/drivers/... | null | null | null | [PATCH] staging: rtl8723bs: Fix logical continuation placement | On Fri Feb 27, 2026 at 1:12 AM CST, Dan Carpenter wrote:
...
That's what I meant I guess my email client mangled it? I'll just
demonstrate it like you did here for now on.
Thanks,
ET | {
"author": "\"Ethan Tidmore\" <ethantidmore06@gmail.com>",
"date": "Fri, 27 Feb 2026 09:12:12 -0600",
"is_openbsd": false,
"thread_id": "DGPUAEKP8SCX.3AUUXG0PMXF8H@gmail.com.mbox.gz"
} |
lkml_critique | lkml | The blamed commit introduced support for specifying individual lanes as
OF nodes in the device, and these can have status = "disabled".
When that happens, for_each_available_child_of_node() skips them and
lynx_28g_probe_lane() -> devm_phy_create() is not called, so lane->phy
will be NULL. Yet it will be dereferenced i... | null | null | null | [PATCH phy-fixes] phy: lynx-28g: skip CDR lock workaround for lanes disabled in the device tree | On Thu, 26 Feb 2026 20:28:53 +0200, Vladimir Oltean wrote:
Applied, thanks!
[1/1] phy: lynx-28g: skip CDR lock workaround for lanes disabled in the device tree
commit: a258d843a3e4cb687da19437f8f81fee55ad7d35
Best regards,
--
~Vinod | {
"author": "Vinod Koul <vkoul@kernel.org>",
"date": "Fri, 27 Feb 2026 20:55:10 +0530",
"is_openbsd": false,
"thread_id": "177220591001.320398.14824622688771745554.b4-ty@kernel.org.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 27 | On Wed, 27 Feb 2008 17:03:00 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
The astute will notice that the pata tree has been renamed to ide as this
better reflects reality (according to Andrew).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/ | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Wed, 27 Feb 2008 17:09:39 +1100",
"is_openbsd": false,
"thread_id": "aaGvJPrwc9oSHr6F@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 27 | On Wed, 27 Feb 2008 17:03:00 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
So who's missing now?
I have:
git-acpi
git-agpgart
git-alsa
git-arm
git-arm-master
git-audit-master
git-avr32
git-backlight
git-battery
git-block
git-bluetooth
git-cifs
git-cpufreq
git-cryptodev
git-drm
git-dvb
git-gfs2-nmw
git-hid
gi... | {
"author": "Andrew Morton <akpm@linux-foundation.org>",
"date": "Tue, 26 Feb 2008 23:00:59 -0800",
"is_openbsd": false,
"thread_id": "aaGvJPrwc9oSHr6F@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 27 | On Tue, 26 Feb 2008 23:00:59 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
Of this list, I *don't* have:
But on the plus side I also have:
blackfin
dlm
libata-dev (same as git-libata-all?)
m68k
tests
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Thu, 28 Feb 2008 01:06:26 +1100",
"is_openbsd": false,
"thread_id": "aaGvJPrwc9oSHr6F@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 27 | On Wednesday 27 February 2008 9:06:26 am Stephen Rothwell wrote:
<akpm@linux-foundation.org> wrote:
...
I keep the labeled networking patches for the upcoming (in this case
2.6.26) kernel here:
* git://git.infradead.org/users/pcmoore/lblnet-2.6_testing
Patches for the current kernel (in this case 2.6.25) live he... | {
"author": "Paul Moore <paul.moore@hp.com>",
"date": "Wed, 27 Feb 2008 09:43:52 -0500",
"is_openbsd": false,
"thread_id": "aaGvJPrwc9oSHr6F@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 27 | Hi Paul,
On Wed, 27 Feb 2008 09:43:52 -0500 Paul Moore <paul.moore@hp.com> wrote:
Added in anticipation, thanks.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Thu, 28 Feb 2008 02:31:53 +1100",
"is_openbsd": false,
"thread_id": "aaGvJPrwc9oSHr6F@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 27 | On Wednesday 27 February 2008 10:31:53 am Stephen Rothwell wrote:
wrote:
Thanks, sorry for not sending mail sooner.
--
paul moore
linux security @ hp | {
"author": "Paul Moore <paul.moore@hp.com>",
"date": "Wed, 27 Feb 2008 11:06:41 -0500",
"is_openbsd": false,
"thread_id": "aaGvJPrwc9oSHr6F@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 27 | Stephen Rothwell wrote:
Intentionally different. libata-dev.git#NEXT is for linux-next, and
libata-dev.git#ALL is for -mm.
Jeff | {
"author": "Jeff Garzik <jeff@garzik.org>",
"date": "Wed, 27 Feb 2008 12:30:59 -0500",
"is_openbsd": false,
"thread_id": "aaGvJPrwc9oSHr6F@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 27 | On Thu, Feb 28, 2008 at 01:06:26AM +1100, Stephen Rothwell wrote:
Hi Stephen,
please add:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git next
This contains a subset of the patches in the ext4 patch set which we
are explicitly planning on pushing to Linus at the next merge window.
It actually pro... | {
"author": "Theodore Tso <tytso@MIT.EDU>",
"date": "Wed, 27 Feb 2008 14:55:25 -0500",
"is_openbsd": false,
"thread_id": "aaGvJPrwc9oSHr6F@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 27 | Hi Jeff,
On Wed, 27 Feb 2008 12:30:59 -0500 Jeff Garzik <jeff@garzik.org> wrote:
Excellent. Thanks for that.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/ | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Thu, 28 Feb 2008 09:54:26 +1100",
"is_openbsd": false,
"thread_id": "aaGvJPrwc9oSHr6F@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 27 | Hi Ted,
On Wed, 27 Feb 2008 14:55:25 -0500 Theodore Tso <tytso@MIT.EDU> wrote:
Added, thanks.
That's what we want.
Thanks, the less conflicts I have to fix the better. :-) I guess over
time patches will migrate into your next branch or they will appear there
after the next Linus release.
--
Cheers,
Stephen Ro... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Thu, 28 Feb 2008 10:06:18 +1100",
"is_openbsd": false,
"thread_id": "aaGvJPrwc9oSHr6F@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 27 | Hi all,
Changes since 20120224:
My fixes tree contains:
x86, efi: Fix unaligned access and endian issues
The tegra tree gained a conflict against the arm tree.
The pci tree gained a conflict against the mips tree and a build failure
for which I applied a patch.
The net-next tree gained a conflict against Linus' t... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Mon, 27 Feb 2012 18:20:29 +1100",
"is_openbsd": false,
"thread_id": "aaGvJPrwc9oSHr6F@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 27 | Hi all,
Please do not add any work destined for v3.10 to your -next included
branches until after Linus has release v3.9-rc1.
Changes since 20130226:
The drm tree lost its build failure.
The renesas tree gained a conflict against Linus' tree.
The akpm tree gained a conflict against the vfs tree and lost a few
patc... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Wed, 27 Feb 2013 13:44:06 +1100",
"is_openbsd": false,
"thread_id": "aaGvJPrwc9oSHr6F@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 27 | Hi all,
This tree fails (more than usual) the powerpc allyesconfig build.
Changes since 20140226:
The powerpc tree still had its build failure.
The libata tree lost its build failure.
The mfd-lj tree still had its build failure so I used the version from
next-20140210.
The drm-tegra tree gained a build failure so... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Thu, 27 Feb 2014 17:03:46 +1100",
"is_openbsd": false,
"thread_id": "aaGvJPrwc9oSHr6F@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 27 | Hi all,
Changes since 20150226:
New Tree: rpi
The drm-intel tree gained a conflict against the drm-intel-fixes tree.
The rcu tree gained a build failure so I used the version from
next-20150226.
The clk tree lost its build failure but gained another so I used the
version from next-20150225.
Non-merge commits (rel... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Fri, 27 Feb 2015 15:49:17 +1100",
"is_openbsd": false,
"thread_id": "aaGvJPrwc9oSHr6F@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 27 | Hi all,
Please do not add any material intended for v4.12 to your linux-next
included branches until after v4.11-rc1 has been released.
Changes since 20170224:
The vfs tree gained conflicts agains Linus' and the f2fs trees and a
build failure for which I added a fix patch.
The drm tree lost its build failure.
The ... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Mon, 27 Feb 2017 14:34:36 +1100",
"is_openbsd": false,
"thread_id": "aaGvJPrwc9oSHr6F@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 27 | Hi all,
Changes since 20180226:
The akpm-current tree gained conflicts against the ext3 tree.
Non-merge commits (relative to Linus' tree): 3516
4224 files changed, 161343 insertions(+), 103609 deletions(-)
----------------------------------------------------------------------------
I have created today's linux-ne... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Tue, 27 Feb 2018 15:03:45 +1100",
"is_openbsd": false,
"thread_id": "aaGvJPrwc9oSHr6F@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 27 | Hi all,
Changes since 20190226:
The mmc-fixes tree still has its build failure for which I reverted a commit.
The hwmon-staging tree lost its build failure.
The net-next tree gained a conflict against the rdma tree.
The vhost tree gained a conflict against the iommu tree.
Non-merge commits (relative to Linus' tre... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Wed, 27 Feb 2019 17:44:27 +1100",
"is_openbsd": false,
"thread_id": "aaGvJPrwc9oSHr6F@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 27 | Hi all,
Changes since 20200226:
The hwmon-fixes tree lost its build failure.
The amlogic tree still had its build failure so I used a supplied patch.
The rdma tree lost its build failure.
The regulator tree lost its build failure.
The akpm-current tree gained a conflict against the kvms390 tree.
The akpm tree lo... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Thu, 27 Feb 2020 15:22:23 +1100",
"is_openbsd": false,
"thread_id": "aaGvJPrwc9oSHr6F@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 27 | Hi all,
Please do not add any v6.4 related commits to your linux-next included
branches until after v6.3-rc1 has been released.
Changes since 20230225:
The ext4 tree still had its complex conflict against the mm-stable
tree, so I used the ext4 tree from next-20230217 again.
The modules tree gained a conflict agains... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Mon, 27 Feb 2023 12:18:13 +1100",
"is_openbsd": false,
"thread_id": "aaGvJPrwc9oSHr6F@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 27 | Hi all,
Changes since 20240226:
Removed tree: drm-ci it is finished with
The perf tree lost its build failure.
The loongarch tree gained a conflict against the arm64 tree.
The vfs-brauner tree gained a conflict against the xfs tree.
The backlight tree still had its build failure so I used the version from
next-20... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Tue, 27 Feb 2024 17:04:18 +1100",
"is_openbsd": false,
"thread_id": "aaGvJPrwc9oSHr6F@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 27 | Hi all,
Changes since 20250226:
The btrfs tree gained a build failure so I used the version from
next-20250226.
The mm tree still had its build failure for which I applied a patch.
Non-merge commits (relative to Linus' tree): 6128
6719 files changed, 338938 insertions(+), 127769 deletions(-)
---------------------... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Thu, 27 Feb 2025 18:25:17 +1100",
"is_openbsd": false,
"thread_id": "aaGvJPrwc9oSHr6F@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 27 | Hi all,
Changes since 20260226:
The net-next tree acquired a conflict with the mm-unstable tree.
The amdgpu tree acquired a conflict with the drm-fixes tree.
The hid tree acquired a build failure in the final merge which wasn't
resolved properly today.
Non-merge commits (relative to Linus' tree): 2376
2756 files ... | {
"author": "Mark Brown <broonie@kernel.org>",
"date": "Fri, 27 Feb 2026 14:50:12 +0000",
"is_openbsd": false,
"thread_id": "aaGvJPrwc9oSHr6F@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Remove the following unnecessary forward declarations from fs.h, which
improves maintainability.
- struct hd_geometry: became unused in fs.h when
block_device_operations was moved to blkdev.h in commit 08f858512151
("[PATCH] move block_device_operations to blkdev.h"). The forward
declaration is now added to blkd... | null | null | null | [PATCH v2] fs: remove stale and duplicate forward declarations | On Thu 26-02-26 20:18:58, Yuto Ohnuki wrote:
Makes sense. Thanks. Feel free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR | {
"author": "Jan Kara <jack@suse.cz>",
"date": "Fri, 27 Feb 2026 16:41:40 +0100",
"is_openbsd": false,
"thread_id": "tzjqeyms46zvrcl4ai7hes4unshkdqnr4kcbj4hjfmrj7nlpve@ujg2satvhk4u.mbox.gz"
} |
lkml_critique | lkml | Guest-controlled counter indices received via SBI ecalls are used to
index into the PMC array. Sanitize them with array_index_nospec()
to prevent speculative out-of-bounds access.
Similar to x86 commit 13c5183a4e64 ("KVM: x86: Protect MSR-based
index computations in pmu.h from Spectre-v1/L1TF attacks").
Fixes: 8f0153... | null | null | null | [PATCH 4/4] KVM: riscv: Fix Spectre-v1 in PMU counter access | User-controlled indices are used to index into floating-point registers.
Sanitize them with array_index_nospec() to prevent speculative
out-of-bounds access.
Signed-off-by: Lukas Gerlach <lukas.gerlach@cispa.de>
---
arch/riscv/kvm/vcpu_fp.c | 17 +++++++++++++----
1 file changed, 13 insertions(+), 4 deletions(-)
dif... | {
"author": "Lukas Gerlach <lukas.gerlach@cispa.de>",
"date": "Thu, 26 Feb 2026 15:19:00 +0100",
"is_openbsd": false,
"thread_id": "20260227151247.18602-1-lukas.gerlach@cispa.de.mbox.gz"
} |
lkml_critique | lkml | Guest-controlled counter indices received via SBI ecalls are used to
index into the PMC array. Sanitize them with array_index_nospec()
to prevent speculative out-of-bounds access.
Similar to x86 commit 13c5183a4e64 ("KVM: x86: Protect MSR-based
index computations in pmu.h from Spectre-v1/L1TF attacks").
Fixes: 8f0153... | null | null | null | [PATCH 4/4] KVM: riscv: Fix Spectre-v1 in PMU counter access | User-controlled register indices from the ONE_REG ioctl are used to
index into arrays of register values. Sanitize them with
array_index_nospec() to prevent speculative out-of-bounds access.
Signed-off-by: Lukas Gerlach <lukas.gerlach@cispa.de>
---
arch/riscv/kvm/vcpu_onereg.c | 36 ++++++++++++++++++++++++++++-------... | {
"author": "Lukas Gerlach <lukas.gerlach@cispa.de>",
"date": "Thu, 26 Feb 2026 15:18:58 +0100",
"is_openbsd": false,
"thread_id": "20260227151247.18602-1-lukas.gerlach@cispa.de.mbox.gz"
} |
lkml_critique | lkml | Guest-controlled counter indices received via SBI ecalls are used to
index into the PMC array. Sanitize them with array_index_nospec()
to prevent speculative out-of-bounds access.
Similar to x86 commit 13c5183a4e64 ("KVM: x86: Protect MSR-based
index computations in pmu.h from Spectre-v1/L1TF attacks").
Fixes: 8f0153... | null | null | null | [PATCH 4/4] KVM: riscv: Fix Spectre-v1 in PMU counter access | This series adds array_index_nospec() to RISC-V KVM to prevent
speculative out-of-bounds access to kernel memory.
Similar fixes exist for x86 (ioapic, lapic, PMU) and arm64 (vgic).
Signed-off-by: Lukas Gerlach <lukas.gerlach@cispa.de>
---
Lukas Gerlach (4):
KVM: riscv: Fix Spectre-v1 in ONE_REG register access
... | {
"author": "Lukas Gerlach <lukas.gerlach@cispa.de>",
"date": "Thu, 26 Feb 2026 15:18:57 +0100",
"is_openbsd": false,
"thread_id": "20260227151247.18602-1-lukas.gerlach@cispa.de.mbox.gz"
} |
lkml_critique | lkml | Guest-controlled counter indices received via SBI ecalls are used to
index into the PMC array. Sanitize them with array_index_nospec()
to prevent speculative out-of-bounds access.
Similar to x86 commit 13c5183a4e64 ("KVM: x86: Protect MSR-based
index computations in pmu.h from Spectre-v1/L1TF attacks").
Fixes: 8f0153... | null | null | null | [PATCH 4/4] KVM: riscv: Fix Spectre-v1 in PMU counter access | User-controlled indices are used to access AIA CSR registers.
Sanitize them with array_index_nospec() to prevent speculative
out-of-bounds access.
Similar to x86 commit 8c86405f606c ("KVM: x86: Protect
ioapic_read_indirect() from Spectre-v1/L1TF attacks") and arm64
commit 41b87599c743 ("KVM: arm/arm64: vgic: fix possi... | {
"author": "Lukas Gerlach <lukas.gerlach@cispa.de>",
"date": "Thu, 26 Feb 2026 15:18:59 +0100",
"is_openbsd": false,
"thread_id": "20260227151247.18602-1-lukas.gerlach@cispa.de.mbox.gz"
} |
lkml_critique | lkml | Guest-controlled counter indices received via SBI ecalls are used to
index into the PMC array. Sanitize them with array_index_nospec()
to prevent speculative out-of-bounds access.
Similar to x86 commit 13c5183a4e64 ("KVM: x86: Protect MSR-based
index computations in pmu.h from Spectre-v1/L1TF attacks").
Fixes: 8f0153... | null | null | null | [PATCH 4/4] KVM: riscv: Fix Spectre-v1 in PMU counter access | 2026-02-26T15:19:01+01:00, Lukas Gerlach <lukas.gerlach@cispa.de>:
This one also covers a non-speculation bug, since the previous condition
used cidx > RISCV_KVM_MAX_COUNTER. :) I'll send a patch for that.
I noticed a few other places where mis-speculation is possible,
see below; can you explain why they don't need ... | {
"author": "=?utf-8?q?Radim_Kr=C4=8Dm=C3=A1=C5=99?=\n <radim.krcmar@oss.qualcomm.com>",
"date": "Fri, 27 Feb 2026 13:28:51 +0000",
"is_openbsd": false,
"thread_id": "20260227151247.18602-1-lukas.gerlach@cispa.de.mbox.gz"
} |
lkml_critique | lkml | Guest-controlled counter indices received via SBI ecalls are used to
index into the PMC array. Sanitize them with array_index_nospec()
to prevent speculative out-of-bounds access.
Similar to x86 commit 13c5183a4e64 ("KVM: x86: Protect MSR-based
index computations in pmu.h from Spectre-v1/L1TF attacks").
Fixes: 8f0153... | null | null | null | [PATCH 4/4] KVM: riscv: Fix Spectre-v1 in PMU counter access | Thanks for the review!
Nice catch, thanks for sending the fix.
They do, I missed those. Will send a v2 incorporating all four sites.
Thanks,
Lukas | {
"author": "Lukas Gerlach <lukas.gerlach@cispa.de>",
"date": "Fri, 27 Feb 2026 16:12:47 +0100",
"is_openbsd": false,
"thread_id": "20260227151247.18602-1-lukas.gerlach@cispa.de.mbox.gz"
} |
lkml_critique | lkml | The serdes device_node is obtained using of_get_child_by_name(),
which increments the reference count. However, it is never put,
leading to a reference leak.
Add the missing of_node_put() calls to ensure the reference count is
properly balanced.
Fixes: 7ae14cf581f2 ("phy: ti: j721e-wiz: Implement DisplayPort mode to ... | null | null | null | [PATCH v2] phy: ti: j721e-wiz: Fix device node reference leak in
wiz_get_lane_phy_types() | …
…
* Would you like to complete the exception handling by using another goto chain?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/coding-style.rst?h=v6.19#n526
* How do you think about to increase the application of scope-based resource management
by additional upd... | {
"author": "Markus Elfring <Markus.Elfring@web.de>",
"date": "Fri, 13 Feb 2026 09:09:55 +0100",
"is_openbsd": false,
"thread_id": "177220591507.320398.1632943326172969051.b4-ty@kernel.org.mbox.gz"
} |
lkml_critique | lkml | The serdes device_node is obtained using of_get_child_by_name(),
which increments the reference count. However, it is never put,
leading to a reference leak.
Add the missing of_node_put() calls to ensure the reference count is
properly balanced.
Fixes: 7ae14cf581f2 ("phy: ti: j721e-wiz: Implement DisplayPort mode to ... | null | null | null | [PATCH v2] phy: ti: j721e-wiz: Fix device node reference leak in
wiz_get_lane_phy_types() | On Thu, Feb 12, 2026 at 06:39:19PM +0800, Felix Gu wrote:
Reviewed-by: Vladimir Oltean <olteanv@gmail.com> | {
"author": "Vladimir Oltean <olteanv@gmail.com>",
"date": "Fri, 13 Feb 2026 12:47:09 +0200",
"is_openbsd": false,
"thread_id": "177220591507.320398.1632943326172969051.b4-ty@kernel.org.mbox.gz"
} |
lkml_critique | lkml | The serdes device_node is obtained using of_get_child_by_name(),
which increments the reference count. However, it is never put,
leading to a reference leak.
Add the missing of_node_put() calls to ensure the reference count is
properly balanced.
Fixes: 7ae14cf581f2 ("phy: ti: j721e-wiz: Implement DisplayPort mode to ... | null | null | null | [PATCH v2] phy: ti: j721e-wiz: Fix device node reference leak in
wiz_get_lane_phy_types() | On Fri, Feb 13, 2026 at 09:09:55AM +0100, Markus Elfring wrote:
While gotos have their place, here it seems simpler not to use them.
Felix would have needed to move the "int ret" variable from the
for_each_child_of_node_scoped() scope to the function scope, and
initialize it with 0. All that is unnecessary complexity ... | {
"author": "Vladimir Oltean <olteanv@gmail.com>",
"date": "Fri, 13 Feb 2026 12:46:29 +0200",
"is_openbsd": false,
"thread_id": "177220591507.320398.1632943326172969051.b4-ty@kernel.org.mbox.gz"
} |
lkml_critique | lkml | The serdes device_node is obtained using of_get_child_by_name(),
which increments the reference count. However, it is never put,
leading to a reference leak.
Add the missing of_node_put() calls to ensure the reference count is
properly balanced.
Fixes: 7ae14cf581f2 ("phy: ti: j721e-wiz: Implement DisplayPort mode to ... | null | null | null | [PATCH v2] phy: ti: j721e-wiz: Fix device node reference leak in
wiz_get_lane_phy_types() | On Thu, 12 Feb 2026 18:39:19 +0800, Felix Gu wrote:
Applied, thanks!
[1/1] phy: ti: j721e-wiz: Fix device node reference leak in wiz_get_lane_phy_types()
commit: 584b457f4166293bdfa50f930228e9fb91a38392
Best regards,
--
~Vinod | {
"author": "Vinod Koul <vkoul@kernel.org>",
"date": "Fri, 27 Feb 2026 20:55:15 +0530",
"is_openbsd": false,
"thread_id": "177220591507.320398.1632943326172969051.b4-ty@kernel.org.mbox.gz"
} |
lkml_critique | lkml | Qualcomm kaanapali platform have a newer generation of video IP iris4.
The hardware have evolved mostly with respect to higher number of power
domains as well as multiple clock sources.
Considering iris as a client driver, it adds the handling for multiple
stream ids from VPU via iommu-map.
This series is depend o... | null | null | null | [PATCH v2 0/7] media: iris: add support for kaanapali platform | Kaanapali SOC brings in the new generation of video IP i.e iris4. When
compared to previous generation, iris3x, it has,
- separate power domains for stream and pixel processing hardware blocks
(bse and vpp).
- additional power domain for apv codec.
- power domains for individual pipes (VPPx).
- different clocks and r... | {
"author": "Vikash Garodia <vikash.garodia@oss.qualcomm.com>",
"date": "Fri, 27 Feb 2026 19:41:17 +0530",
"is_openbsd": false,
"thread_id": "177220692821.4084988.9709880172251199727.robh@kernel.org.mbox.gz"
} |
lkml_critique | lkml | Qualcomm kaanapali platform have a newer generation of video IP iris4.
The hardware have evolved mostly with respect to higher number of power
domains as well as multiple clock sources.
Considering iris as a client driver, it adds the handling for multiple
stream ids from VPU via iommu-map.
This series is depend o... | null | null | null | [PATCH v2 0/7] media: iris: add support for kaanapali platform | Currently the driver switches the vcodec GDSC to hardware (HW) mode
before firmware load and boot sequence. GDSC can be powered off, keeping
in hw mode, thereby the vcodec registers programmed in TrustZone (TZ)
carry default (reset) values.
Move the transition to HW mode after firmware load and boot sequence.
The bug ... | {
"author": "Vikash Garodia <vikash.garodia@oss.qualcomm.com>",
"date": "Fri, 27 Feb 2026 19:41:18 +0530",
"is_openbsd": false,
"thread_id": "177220692821.4084988.9709880172251199727.robh@kernel.org.mbox.gz"
} |
lkml_critique | lkml | Qualcomm kaanapali platform have a newer generation of video IP iris4.
The hardware have evolved mostly with respect to higher number of power
domains as well as multiple clock sources.
Considering iris as a client driver, it adds the handling for multiple
stream ids from VPU via iommu-map.
This series is depend o... | null | null | null | [PATCH v2 0/7] media: iris: add support for kaanapali platform | Add iris vpu bus support and hooks the new bus into the iommu_buses
list. Iris devices need their own bus so that each iris device can run
its own dma_configure() logic.
Co-developed-by: Vishnu Reddy <busanna.reddy@oss.qualcomm.com>
Signed-off-by: Vishnu Reddy <busanna.reddy@oss.qualcomm.com>
Signed-off-by: Vikash Gar... | {
"author": "Vikash Garodia <vikash.garodia@oss.qualcomm.com>",
"date": "Fri, 27 Feb 2026 19:41:19 +0530",
"is_openbsd": false,
"thread_id": "177220692821.4084988.9709880172251199727.robh@kernel.org.mbox.gz"
} |
lkml_critique | lkml | Qualcomm kaanapali platform have a newer generation of video IP iris4.
The hardware have evolved mostly with respect to higher number of power
domains as well as multiple clock sources.
Considering iris as a client driver, it adds the handling for multiple
stream ids from VPU via iommu-map.
This series is depend o... | null | null | null | [PATCH v2 0/7] media: iris: add support for kaanapali platform | Introduce different context banks(CB) and the associated buffer region.
Different stream IDs from VPU would be associated to one of these CB.
Multiple CBs are needed to increase the IOVA for the video usecases like
higher concurrent sessions.
Co-developed-by: Vishnu Reddy <busanna.reddy@oss.qualcomm.com>
Signed-off-by... | {
"author": "Vikash Garodia <vikash.garodia@oss.qualcomm.com>",
"date": "Fri, 27 Feb 2026 19:41:20 +0530",
"is_openbsd": false,
"thread_id": "177220692821.4084988.9709880172251199727.robh@kernel.org.mbox.gz"
} |
lkml_critique | lkml | Qualcomm kaanapali platform have a newer generation of video IP iris4.
The hardware have evolved mostly with respect to higher number of power
domains as well as multiple clock sources.
Considering iris as a client driver, it adds the handling for multiple
stream ids from VPU via iommu-map.
This series is depend o... | null | null | null | [PATCH v2 0/7] media: iris: add support for kaanapali platform | Depending on the buffer type (input, output, internal and interface
queues), associated context bank is selected, if available. Fallback to
parent device for backward compatibility.
Co-developed-by: Vishnu Reddy <busanna.reddy@oss.qualcomm.com>
Signed-off-by: Vishnu Reddy <busanna.reddy@oss.qualcomm.com>
Signed-off-by... | {
"author": "Vikash Garodia <vikash.garodia@oss.qualcomm.com>",
"date": "Fri, 27 Feb 2026 19:41:21 +0530",
"is_openbsd": false,
"thread_id": "177220692821.4084988.9709880172251199727.robh@kernel.org.mbox.gz"
} |
lkml_critique | lkml | Qualcomm kaanapali platform have a newer generation of video IP iris4.
The hardware have evolved mostly with respect to higher number of power
domains as well as multiple clock sources.
Considering iris as a client driver, it adds the handling for multiple
stream ids from VPU via iommu-map.
This series is depend o... | null | null | null | [PATCH v2 0/7] media: iris: add support for kaanapali platform | The H265 decoder line buffer size calculation for iris4 (VPU4) was
previously reusing the iris3 formula. While this works for most
resolutions, certain configurations require a larger buffer size on
iris4, causing firmware errors during decode. This resolves firmware
failures seen with specific test vectors on kaanapal... | {
"author": "Vikash Garodia <vikash.garodia@oss.qualcomm.com>",
"date": "Fri, 27 Feb 2026 19:41:22 +0530",
"is_openbsd": false,
"thread_id": "177220692821.4084988.9709880172251199727.robh@kernel.org.mbox.gz"
} |
lkml_critique | lkml | Qualcomm kaanapali platform have a newer generation of video IP iris4.
The hardware have evolved mostly with respect to higher number of power
domains as well as multiple clock sources.
Considering iris as a client driver, it adds the handling for multiple
stream ids from VPU via iommu-map.
This series is depend o... | null | null | null | [PATCH v2 0/7] media: iris: add support for kaanapali platform | Add support for the kaanapali platform by re-using the SM8550
definitions and using the vpu4 ops.
Move the configurations that differs in a per-SoC platform header, that
will contain SoC specific data.
Co-developed-by: Vishnu Reddy <busanna.reddy@oss.qualcomm.com>
Signed-off-by: Vishnu Reddy <busanna.reddy@oss.qualcom... | {
"author": "Vikash Garodia <vikash.garodia@oss.qualcomm.com>",
"date": "Fri, 27 Feb 2026 19:41:23 +0530",
"is_openbsd": false,
"thread_id": "177220692821.4084988.9709880172251199727.robh@kernel.org.mbox.gz"
} |
lkml_critique | lkml | Qualcomm kaanapali platform have a newer generation of video IP iris4.
The hardware have evolved mostly with respect to higher number of power
domains as well as multiple clock sources.
Considering iris as a client driver, it adds the handling for multiple
stream ids from VPU via iommu-map.
This series is depend o... | null | null | null | [PATCH v2 0/7] media: iris: add support for kaanapali platform | On Fri, 27 Feb 2026 19:41:17 +0530, Vikash Garodia wrote:
My bot found errors running 'make dt_binding_check' on your patch:
yamllint warnings/errors:
dtschema/dtc warnings/errors:
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/pci/qcom,pcie-sdm845.example.dtb: pcie@1c00000 (qcom,pcie-sdm845... | {
"author": "\"Rob Herring (Arm)\" <robh@kernel.org>",
"date": "Fri, 27 Feb 2026 09:42:08 -0600",
"is_openbsd": false,
"thread_id": "177220692821.4084988.9709880172251199727.robh@kernel.org.mbox.gz"
} |
lkml_critique | lkml | Qualcomm kaanapali platform have a newer generation of video IP iris4.
The hardware have evolved mostly with respect to higher number of power
domains as well as multiple clock sources.
Considering iris as a client driver, it adds the handling for multiple
stream ids from VPU via iommu-map.
This series is depend o... | null | null | null | [PATCH v2 0/7] media: iris: add support for kaanapali platform | On 27/02/2026 14:11, Vikash Garodia wrote:
For the record this series is blocked on this:
https://lore.kernel.org/all/20260226074245.3098486-1-vijayanand.jitta@oss.qualcomm.com/
---
bod | {
"author": "Bryan O'Donoghue <bryan.odonoghue@linaro.org>",
"date": "Fri, 27 Feb 2026 15:42:17 +0000",
"is_openbsd": false,
"thread_id": "177220692821.4084988.9709880172251199727.robh@kernel.org.mbox.gz"
} |
lkml_critique | lkml | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | null | null | null | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | Export liveupdate_enabled(), liveupdate_register_file_handler(), and
liveupdate_unregister_file_handler(). All of these will be used by
vfio-pci in a subsequent commit, which can be built as a module.
Signed-off-by: David Matlack <dmatlack@google.com>
---
kernel/liveupdate/luo_core.c | 1 +
kernel/liveupdate/luo_file... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:48 +0000",
"is_openbsd": false,
"thread_id": "20260227084658.3767d801@shazbot.org.mbox.gz"
} |
lkml_critique | lkml | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | null | null | null | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | Inherit bus numbers from the previous kernel during a Live Update when
one or more PCI devices are being preserved. This is necessary so that
preserved devices can DMA through the IOMMU during a Live Update
(changing bus numbers would break IOMMU translation).
Signed-off-by: David Matlack <dmatlack@google.com>
---
dr... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:50 +0000",
"is_openbsd": false,
"thread_id": "20260227084658.3767d801@shazbot.org.mbox.gz"
} |
lkml_critique | lkml | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | null | null | null | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | Add an API to enable the PCI subsystem to track all devices that are
preserved across a Live Update, including both incoming devices (passed
from the previous kernel) and outgoing devices (passed to the next
kernel).
Use PCI segment number and BDF to keep track of devices across Live
Update. This means the kernel must... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:49 +0000",
"is_openbsd": false,
"thread_id": "20260227084658.3767d801@shazbot.org.mbox.gz"
} |
lkml_critique | lkml | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | null | null | null | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | From: Vipin Sharma <vipinsh@google.com>
Register a live update file handler for vfio-pci device files. Add stub
implementations of all required callbacks so that registration does not
fail (i.e. to avoid breaking git-bisect).
This file handler will be extended in subsequent commits to enable a
device bound to vfio-pc... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:51 +0000",
"is_openbsd": false,
"thread_id": "20260227084658.3767d801@shazbot.org.mbox.gz"
} |
lkml_critique | lkml | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | null | null | null | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | From: Vipin Sharma <vipinsh@google.com>
Implement the live update file handler callbacks to preserve a vfio-pci
device across a Live Update. Subsequent commits will enable userspace to
then retrieve this file after the Live Update.
Live Update support is scoped only to cdev files (i.e. not
VFIO_GROUP_GET_DEVICE_FD fi... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:52 +0000",
"is_openbsd": false,
"thread_id": "20260227084658.3767d801@shazbot.org.mbox.gz"
} |
lkml_critique | lkml | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | null | null | null | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | From: Vipin Sharma <vipinsh@google.com>
Enable userspace to retrieve preserved VFIO device files from VFIO after
a Live Update by implementing the retrieve() and finish() file handler
callbacks.
Use an anonymous inode when creating the file, since the retrieved
device file is not opened through any particular cdev in... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:53 +0000",
"is_openbsd": false,
"thread_id": "20260227084658.3767d801@shazbot.org.mbox.gz"
} |
lkml_critique | lkml | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | null | null | null | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | Notify the PCI subsystem about devices vfio-pci is preserving across
Live Update by registering the vfio-pci liveupdate file handler with the
PCI subsystem's FLB handler.
Notably this will ensure that devices preserved through vfio-pci will
have their PCI bus numbers preserved across Live Update, allowing VFIO
to use ... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:54 +0000",
"is_openbsd": false,
"thread_id": "20260227084658.3767d801@shazbot.org.mbox.gz"
} |
lkml_critique | lkml | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | null | null | null | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | Enforce that files for incoming (preserved by previous kernel) VFIO
devices are retrieved via LIVEUPDATE_SESSION_RETRIEVE_FD rather than by
opening the corresponding VFIO character device or via
VFIO_GROUP_GET_DEVICE_FD.
Both of these methods would result in VFIO initializing the device
without access to the preserved... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:55 +0000",
"is_openbsd": false,
"thread_id": "20260227084658.3767d801@shazbot.org.mbox.gz"
} |
lkml_critique | lkml | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | null | null | null | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | Stash a pointer to a device's incoming Live Updated state in struct
vfio_pci_core_device. This will enable subsequent commits to use the
preserved state when initializing the device.
To enable VFIO to safely access this pointer during device enablement,
require that the device is fully enabled before returning true fr... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:56 +0000",
"is_openbsd": false,
"thread_id": "20260227084658.3767d801@shazbot.org.mbox.gz"
} |
lkml_critique | lkml | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | null | null | null | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | From: Vipin Sharma <vipinsh@google.com>
Do not reset the device when a Live Update preserved vfio-pci device is
retrieved and first enabled. vfio_pci_liveupdate_freeze() guarantees the
device is reset prior to Live Update, so there's no reason to reset it
again after Live Update.
Since VFIO normally uses the initial ... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:57 +0000",
"is_openbsd": false,
"thread_id": "20260227084658.3767d801@shazbot.org.mbox.gz"
} |
lkml_critique | lkml | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | null | null | null | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | Add documentation for preserving VFIO device files across a Live Update,
as well as some generic file preservation documentation. This
documentation will be extended in the future as new types of files are
supported and new dependency/ordering requirements are added.
Signed-off-by: David Matlack <dmatlack@google.com>
... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:58 +0000",
"is_openbsd": false,
"thread_id": "20260227084658.3767d801@shazbot.org.mbox.gz"
} |
lkml_critique | lkml | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | null | null | null | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | From: Vipin Sharma <vipinsh@google.com>
Move luo_test_utils.[ch] into a lib/ directory and pull the rules to
build them out into a separate make script. This will enable these
utilities to be also built by and used within other selftests (such as
VFIO) in subsequent commits.
No functional change intended.
Signed-off... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:59 +0000",
"is_openbsd": false,
"thread_id": "20260227084658.3767d801@shazbot.org.mbox.gz"
} |
lkml_critique | lkml | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | null | null | null | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | From: Vipin Sharma <vipinsh@google.com>
Add helper functions to preserve and retrieve file descriptors from an
LUO session. These will be used be used in subsequent commits to
preserve FDs other than memfd.
No functional change intended.
Signed-off-by: Vipin Sharma <vipinsh@google.com>
Co-developed-by: David Matlack... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:25:00 +0000",
"is_openbsd": false,
"thread_id": "20260227084658.3767d801@shazbot.org.mbox.gz"
} |
lkml_critique | lkml | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | null | null | null | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | Add a selftest to exercise preserving a various VFIO files through
/dev/liveupdate. Ensure that VFIO cdev device files can be preserved and
everything else (group-based device files, group files, and container
files) all fail.
Signed-off-by: David Matlack <dmatlack@google.com>
---
tools/testing/selftests/vfio/Makefil... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:25:03 +0000",
"is_openbsd": false,
"thread_id": "20260227084658.3767d801@shazbot.org.mbox.gz"
} |
lkml_critique | lkml | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | null | null | null | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | From: Vipin Sharma <vipinsh@google.com>
Import and build liveupdate selftest library in VFIO selftests.
It allows to use liveupdate ioctls in VFIO selftests
Signed-off-by: Vipin Sharma <vipinsh@google.com>
Signed-off-by: David Matlack <dmatlack@google.com>
---
tools/testing/selftests/vfio/Makefile | 11 ++++++++---
... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:25:01 +0000",
"is_openbsd": false,
"thread_id": "20260227084658.3767d801@shazbot.org.mbox.gz"
} |
lkml_critique | lkml | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | null | null | null | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | Add Makefile support for TEST_GEN_PROGS_EXTENDED targets. These tests
are not run by default.
TEST_GEN_PROGS_EXTENDED will be used for Live Update selftests in
subsequent commits. These selftests must be run manually because they
require the user/runner to perform additional actions, such as kexec,
during the test.
S... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:25:02 +0000",
"is_openbsd": false,
"thread_id": "20260227084658.3767d801@shazbot.org.mbox.gz"
} |
lkml_critique | lkml | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | null | null | null | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | From: Vipin Sharma <vipinsh@google.com>
Use the given VFIO cdev FD to initialize vfio_pci_device in VFIO
selftests. Add the assertion to make sure that passed cdev FD is not
used with legacy VFIO APIs. If VFIO cdev FD is provided then do not open
the device instead use the FD for any interaction with the device.
This... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:25:04 +0000",
"is_openbsd": false,
"thread_id": "20260227084658.3767d801@shazbot.org.mbox.gz"
} |
lkml_critique | lkml | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | null | null | null | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | Expose the list of iommu_modes to enable tests that want to iterate
through all possible iommu modes.
Signed-off-by: David Matlack <dmatlack@google.com>
---
tools/testing/selftests/vfio/lib/include/libvfio/iommu.h | 2 ++
tools/testing/selftests/vfio/lib/iommu.c | 4 +++-
2 files changed, 5 insertions... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:25:06 +0000",
"is_openbsd": false,
"thread_id": "20260227084658.3767d801@shazbot.org.mbox.gz"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.