source large_stringclasses 2
values | subject large_stringclasses 112
values | code large_stringclasses 112
values | critique large_stringlengths 61 3.04M ⌀ | metadata dict |
|---|---|---|---|---|
lkml | [PATCH 0/2] module: Remove SHA-1 support for module signing | SHA-1 is considered deprecated and insecure due to vulnerabilities that can
lead to hash collisions. Most distributions have already been using SHA-2
for module signing because of this. The default was also changed last year
from SHA-1 to SHA-512 in f3b93547b91a ("module: sign with sha512 instead of
sha1 by default"). ... | The PKCS#7 code in sign-file allows for signing only with SHA-1. Since
SHA-1 support for module signing has been removed, drop PKCS#7 support in
favor of using only CMS.
The use of the PKCS#7 code is selected by the following:
#if defined(LIBRESSL_VERSION_NUMBER) || \
OPENSSL_VERSION_NUMBER < 0x10000000L || \
de... | {
"author": "Petr Pavlu <petr.pavlu@suse.com>",
"date": "Tue, 11 Nov 2025 16:48:32 +0100",
"thread_id": "20251111154923.978181-1-petr.pavlu@suse.com.mbox.gz"
} |
lkml | [PATCH 0/2] module: Remove SHA-1 support for module signing | SHA-1 is considered deprecated and insecure due to vulnerabilities that can
lead to hash collisions. Most distributions have already been using SHA-2
for module signing because of this. The default was also changed last year
from SHA-1 to SHA-512 in f3b93547b91a ("module: sign with sha512 instead of
sha1 by default"). ... | Hi Petr,
On Tue, Nov 11, 2025 at 7:49 AM Petr Pavlu <petr.pavlu@suse.com> wrote:
It looks like GKI just uses the defaults here. Overall, Android
doesn't rely on module signing for security, it's only used to
differentiate between module types. Dropping SHA-1 support sounds like
a good idea to me.
For the series:
R... | {
"author": "Sami Tolvanen <samitolvanen@google.com>",
"date": "Tue, 11 Nov 2025 08:22:34 -0800",
"thread_id": "20251111154923.978181-1-petr.pavlu@suse.com.mbox.gz"
} |
lkml | [PATCH 0/2] module: Remove SHA-1 support for module signing | SHA-1 is considered deprecated and insecure due to vulnerabilities that can
lead to hash collisions. Most distributions have already been using SHA-2
for module signing because of this. The default was also changed last year
from SHA-1 to SHA-512 in f3b93547b91a ("module: sign with sha512 instead of
sha1 by default"). ... | On Tue, 2025-11-11 at 16:48 +0100, Petr Pavlu wrote:
The change log is a bit alarmist. CMS really *is* PKCS7 and most
literature will refer to CMS as PKCS7. What you're really deprecating
is the use of the PKCS7_sign() API which can only produce SHA-1
Signatures ... openssl is fully capable of producing any hash PKC... | {
"author": "James Bottomley <James.Bottomley@HansenPartnership.com>",
"date": "Tue, 11 Nov 2025 11:53:34 -0500",
"thread_id": "20251111154923.978181-1-petr.pavlu@suse.com.mbox.gz"
} |
lkml | [PATCH 0/2] module: Remove SHA-1 support for module signing | SHA-1 is considered deprecated and insecure due to vulnerabilities that can
lead to hash collisions. Most distributions have already been using SHA-2
for module signing because of this. The default was also changed last year
from SHA-1 to SHA-512 in f3b93547b91a ("module: sign with sha512 instead of
sha1 by default"). ... | On Tue, Nov 11, 2025 at 04:48:31PM +0100, Petr Pavlu wrote:
Agreed.
Reviewed-by: Aaron Tomlin <atomlin@atomlin.com>
--
Aaron Tomlin | {
"author": "Aaron Tomlin <atomlin@atomlin.com>",
"date": "Tue, 11 Nov 2025 17:37:28 -0500",
"thread_id": "20251111154923.978181-1-petr.pavlu@suse.com.mbox.gz"
} |
lkml | [PATCH 0/2] module: Remove SHA-1 support for module signing | SHA-1 is considered deprecated and insecure due to vulnerabilities that can
lead to hash collisions. Most distributions have already been using SHA-2
for module signing because of this. The default was also changed last year
from SHA-1 to SHA-512 in f3b93547b91a ("module: sign with sha512 instead of
sha1 by default"). ... | On 11/11/25 5:53 PM, James Bottomley wrote:
Ok, I plan to update the description to the following in v2:
sign-file: Use only the OpenSSL CMS API for signing
The USE_PKCS7 code in sign-file utilizes PKCS7_sign(), which allows signing
only with SHA-1. Since SHA-1 support for module signing has been removed,
drop the u... | {
"author": "Petr Pavlu <petr.pavlu@suse.com>",
"date": "Wed, 12 Nov 2025 14:51:24 +0100",
"thread_id": "20251111154923.978181-1-petr.pavlu@suse.com.mbox.gz"
} |
lkml | [PATCH 0/2] module: Remove SHA-1 support for module signing | SHA-1 is considered deprecated and insecure due to vulnerabilities that can
lead to hash collisions. Most distributions have already been using SHA-2
for module signing because of this. The default was also changed last year
from SHA-1 to SHA-512 in f3b93547b91a ("module: sign with sha512 instead of
sha1 by default"). ... | On Wed, 2025-11-12 at 14:51 +0100, Petr Pavlu wrote:
Much better, thanks!
Regards,
James | {
"author": "James Bottomley <James.Bottomley@HansenPartnership.com>",
"date": "Wed, 12 Nov 2025 10:05:57 -0500",
"thread_id": "20251111154923.978181-1-petr.pavlu@suse.com.mbox.gz"
} |
lkml | [PATCH 0/2] module: Remove SHA-1 support for module signing | SHA-1 is considered deprecated and insecure due to vulnerabilities that can
lead to hash collisions. Most distributions have already been using SHA-2
for module signing because of this. The default was also changed last year
from SHA-1 to SHA-512 in f3b93547b91a ("module: sign with sha512 instead of
sha1 by default"). ... | Petr Pavlu <petr.pavlu@suse.com> wrote:
We're looking at moving to ML-DSA, and the CMS support there is slightly dodgy
at the moment, so we need to hold off a bit on this change.
Patch 1, removing the option to sign with SHA-1 from the kernel is fine, but
doesn't stop things that are signed with SHA-1 from being ver... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Wed, 12 Nov 2025 15:36:57 +0000",
"thread_id": "20251111154923.978181-1-petr.pavlu@suse.com.mbox.gz"
} |
lkml | [PATCH 0/2] module: Remove SHA-1 support for module signing | SHA-1 is considered deprecated and insecure due to vulnerabilities that can
lead to hash collisions. Most distributions have already been using SHA-2
for module signing because of this. The default was also changed last year
from SHA-1 to SHA-512 in f3b93547b91a ("module: sign with sha512 instead of
sha1 by default"). ... | On Wed, 2025-11-12 at 15:36 +0000, David Howells wrote:
How will removing PKCS7_sign, which can only do sha1 signatures affect
that? Is the dodginess that the PKCS7_... API is better than CMS_...
for PQS at the moment? In which case we could pretty much do a rip and
replace of the CMS_ API if necessary, but that woul... | {
"author": "James Bottomley <James.Bottomley@HansenPartnership.com>",
"date": "Wed, 12 Nov 2025 10:47:23 -0500",
"thread_id": "20251111154923.978181-1-petr.pavlu@suse.com.mbox.gz"
} |
lkml | [PATCH 0/2] module: Remove SHA-1 support for module signing | SHA-1 is considered deprecated and insecure due to vulnerabilities that can
lead to hash collisions. Most distributions have already been using SHA-2
for module signing because of this. The default was also changed last year
from SHA-1 to SHA-512 in f3b93547b91a ("module: sign with sha512 instead of
sha1 by default"). ... | James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
OpenSSL-3.5.1's ML-DSA support isn't completely right - in particular
CMS_NOATTR is not currently supported. I believe there is a fix in the works
there, but I doubt it has made it to all the distributions yet. I'm only
asking that we hold off a cycle; ... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Wed, 12 Nov 2025 15:52:40 +0000",
"thread_id": "20251111154923.978181-1-petr.pavlu@suse.com.mbox.gz"
} |
lkml | [PATCH 0/2] module: Remove SHA-1 support for module signing | SHA-1 is considered deprecated and insecure due to vulnerabilities that can
lead to hash collisions. Most distributions have already been using SHA-2
for module signing because of this. The default was also changed last year
from SHA-1 to SHA-512 in f3b93547b91a ("module: sign with sha512 instead of
sha1 by default"). ... | On Wed, 2025-11-12 at 15:52 +0000, David Howells wrote:
I get that PQC in openssl-3.5 is highly experimental, but that merely
means we tell people not to use it for a while. However, what I don't
see is how this impacts PKCS7_sign removal. The CMS API can do a sha1
signature if that's what people want and keeping th... | {
"author": "James Bottomley <James.Bottomley@HansenPartnership.com>",
"date": "Wed, 12 Nov 2025 10:58:31 -0500",
"thread_id": "20251111154923.978181-1-petr.pavlu@suse.com.mbox.gz"
} |
lkml | [PATCH 0/2] module: Remove SHA-1 support for module signing | SHA-1 is considered deprecated and insecure due to vulnerabilities that can
lead to hash collisions. Most distributions have already been using SHA-2
for module signing because of this. The default was also changed last year
from SHA-1 to SHA-512 in f3b93547b91a ("module: sign with sha512 instead of
sha1 by default"). ... | On Tue, 11 Nov 2025 16:48:30 +0100, Petr Pavlu wrote:
Applied to modules-next, thanks!
[1/2] module: Remove SHA-1 support for module signing
commit: 148519a06304af4e6fbb82f20e1a4480e2c1b126
[2/2] sign-file: Use only the OpenSSL CMS API for signing
commit: d7afd65b4acc775df872af30948dd7c196587169
Best reg... | {
"author": "Sami Tolvanen <samitolvanen@google.com>",
"date": "Mon, 22 Dec 2025 20:24:17 +0000",
"thread_id": "20251111154923.978181-1-petr.pavlu@suse.com.mbox.gz"
} |
lkml | [PATCH 0/2] module: Remove SHA-1 support for module signing | SHA-1 is considered deprecated and insecure due to vulnerabilities that can
lead to hash collisions. Most distributions have already been using SHA-2
for module signing because of this. The default was also changed last year
from SHA-1 to SHA-512 in f3b93547b91a ("module: sign with sha512 instead of
sha1 by default"). ... | Here's an alternative patch that will allow PKCS#7 with the hash specified on
the command line, removing the SHA1 restriction.
David
---
sign-file, pkcs7: Honour the hash parameter to sign-file
Currently, the sign-file program rejects anything other than "sha1" as the
hash parameter if it is going to produce a PKCS#7... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 02 Feb 2026 11:24:22 +0000",
"thread_id": "20251111154923.978181-1-petr.pavlu@suse.com.mbox.gz"
} |
lkml | [PATCH 0/2] module: Remove SHA-1 support for module signing | SHA-1 is considered deprecated and insecure due to vulnerabilities that can
lead to hash collisions. Most distributions have already been using SHA-2
for module signing because of this. The default was also changed last year
from SHA-1 to SHA-512 in f3b93547b91a ("module: sign with sha512 instead of
sha1 by default"). ... | David Howells <dhowells@redhat.com> wrote:
Apologies, that line was so I could debug it and should've been removed.
David | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 02 Feb 2026 11:27:39 +0000",
"thread_id": "20251111154923.978181-1-petr.pavlu@suse.com.mbox.gz"
} |
lkml | [PATCH 0/2] module: Remove SHA-1 support for module signing | SHA-1 is considered deprecated and insecure due to vulnerabilities that can
lead to hash collisions. Most distributions have already been using SHA-2
for module signing because of this. The default was also changed last year
from SHA-1 to SHA-512 in f3b93547b91a ("module: sign with sha512 instead of
sha1 by default"). ... | On 2/2/26 12:24 PM, David Howells wrote:
Is it worth keeping this sign-file code that uses the OpenSSL PKCS7 API
instead of having only one variant that uses the newer CMS API?
--
Thanks,
Petr | {
"author": "Petr Pavlu <petr.pavlu@suse.com>",
"date": "Mon, 2 Feb 2026 13:25:06 +0100",
"thread_id": "20251111154923.978181-1-petr.pavlu@suse.com.mbox.gz"
} |
lkml | [PATCH 0/2] module: Remove SHA-1 support for module signing | SHA-1 is considered deprecated and insecure due to vulnerabilities that can
lead to hash collisions. Most distributions have already been using SHA-2
for module signing because of this. The default was also changed last year
from SHA-1 to SHA-512 in f3b93547b91a ("module: sign with sha512 instead of
sha1 by default"). ... | On Mon, Feb 2, 2026 at 4:25 AM Petr Pavlu <petr.pavlu@suse.com> wrote:
I agree that keeping only the CMS variant makes more sense. However,
David, please let me know if you'd prefer that I drop the patch
removing PKCS7 support from sign-file for now. I assumed you had no
further objections since the discussion in the ... | {
"author": "Sami Tolvanen <samitolvanen@google.com>",
"date": "Mon, 2 Feb 2026 09:01:19 -0800",
"thread_id": "20251111154923.978181-1-petr.pavlu@suse.com.mbox.gz"
} |
lkml | [PATCH v2 0/4] Improve Hyper-V memory deposit error handling | This series extends the MSHV driver to properly handle additional
memory-related error codes from the Microsoft Hypervisor by depositing
memory pages when needed.
Currently, when the hypervisor returns HV_STATUS_INSUFFICIENT_MEMORY
during partition creation, the driver calls hv_call_deposit_pages() to
provide the nece... | Replace direct comparisons of hv_result(status) against
HV_STATUS_INSUFFICIENT_MEMORY with a new hv_result_needs_memory() helper
function.
This improves code readability and provides a consistent and extendable
interface for checking out-of-memory conditions in hypercall results.
No functional changes intended.
Signe... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Mon, 02 Feb 2026 17:58:57 +0000",
"thread_id": "177005514902.120041.13078117373390753930.stgit@skinsburskii-cloud-desktop.internal.cloudapp.net.mbox.gz"
} |
lkml | [PATCH v2 0/4] Improve Hyper-V memory deposit error handling | This series extends the MSHV driver to properly handle additional
memory-related error codes from the Microsoft Hypervisor by depositing
memory pages when needed.
Currently, when the hypervisor returns HV_STATUS_INSUFFICIENT_MEMORY
during partition creation, the driver calls hv_call_deposit_pages() to
provide the nece... | Introduce hv_deposit_memory_node() and hv_deposit_memory() helper
functions to handle memory deposition with proper error handling.
The new hv_deposit_memory_node() function takes the hypervisor status
as a parameter and validates it before depositing pages. It checks for
HV_STATUS_INSUFFICIENT_MEMORY specifically and... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Mon, 02 Feb 2026 17:59:03 +0000",
"thread_id": "177005514902.120041.13078117373390753930.stgit@skinsburskii-cloud-desktop.internal.cloudapp.net.mbox.gz"
} |
lkml | [PATCH v2 0/4] Improve Hyper-V memory deposit error handling | This series extends the MSHV driver to properly handle additional
memory-related error codes from the Microsoft Hypervisor by depositing
memory pages when needed.
Currently, when the hypervisor returns HV_STATUS_INSUFFICIENT_MEMORY
during partition creation, the driver calls hv_call_deposit_pages() to
provide the nece... | The HV_STATUS_INSUFFICIENT_CONTIGUOUS_MEMORY status indicates that the
hypervisor lacks sufficient contiguous memory for its internal allocations.
When this status is encountered, allocate and deposit
HV_MAX_CONTIGUOUS_ALLOCATION_PAGES contiguous pages to the hypervisor.
HV_MAX_CONTIGUOUS_ALLOCATION_PAGES is defined i... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Mon, 02 Feb 2026 17:59:09 +0000",
"thread_id": "177005514902.120041.13078117373390753930.stgit@skinsburskii-cloud-desktop.internal.cloudapp.net.mbox.gz"
} |
lkml | [PATCH v2 0/4] Improve Hyper-V memory deposit error handling | This series extends the MSHV driver to properly handle additional
memory-related error codes from the Microsoft Hypervisor by depositing
memory pages when needed.
Currently, when the hypervisor returns HV_STATUS_INSUFFICIENT_MEMORY
during partition creation, the driver calls hv_call_deposit_pages() to
provide the nece... | When creating guest partition objects, the hypervisor may fail to
allocate root partition pages and return an insufficient memory status.
In this case, deposit memory using the root partition ID instead.
Note: This error should never occur in a guest of L1VH partition context.
Signed-off-by: Stanislav Kinsburskii <sk... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Mon, 02 Feb 2026 17:59:14 +0000",
"thread_id": "177005514902.120041.13078117373390753930.stgit@skinsburskii-cloud-desktop.internal.cloudapp.net.mbox.gz"
} |
lkml | [RFC PATCH 0/5] Separate compound page from folio | Hi all,
Based on my discussion with Jason about device private folio
reinitialization[1], I realize that the concepts of compound page and folio
are mixed together and confusing, as people think a compound page is equal
to a folio. This is not true, since a compound page means a group of
pages is managed as a whole an... | The page allocated in io_mem_alloc_compound() is actually used as a folio
later in io_region_mmap(). So allocate a folio instead of a compound page
and rename io_mem_alloc_compound() to io_mem_alloc_folio().
This prepares for code separation of compound page and folio in a follow-up
commit.
Signed-off-by: Zi Yan <ziy... | {
"author": "Zi Yan <ziy@nvidia.com>",
"date": "Thu, 29 Jan 2026 22:48:14 -0500",
"thread_id": "20260130034818.472804-1-ziy@nvidia.com.mbox.gz"
} |
lkml | [RFC PATCH 0/5] Separate compound page from folio | Hi all,
Based on my discussion with Jason about device private folio
reinitialization[1], I realize that the concepts of compound page and folio
are mixed together and confusing, as people think a compound page is equal
to a folio. This is not true, since a compound page means a group of
pages is managed as a whole an... | Current code uses folio_set_large_rmappable() on after-split folios, but
these folios should be treated as compound pages and converted to folios
with page_rmappable_folio().
This prepares for code separation of compound page and folio in a follow-up
commit.
Signed-off-by: Zi Yan <ziy@nvidia.com>
---
mm/huge_memory.... | {
"author": "Zi Yan <ziy@nvidia.com>",
"date": "Thu, 29 Jan 2026 22:48:15 -0500",
"thread_id": "20260130034818.472804-1-ziy@nvidia.com.mbox.gz"
} |
lkml | [RFC PATCH 0/5] Separate compound page from folio | Hi all,
Based on my discussion with Jason about device private folio
reinitialization[1], I realize that the concepts of compound page and folio
are mixed together and confusing, as people think a compound page is equal
to a folio. This is not true, since a compound page means a group of
pages is managed as a whole an... | Commit f708f6970cc9 ("mm/hugetlb: fix kernel NULL pointer dereference when
migrating hugetlb folio") fixed a NULL pointer dereference when
folio_undo_large_rmappable(), now folio_unqueue_deferred_list(), is used on
hugetlb to clear deferred_list. It cleared large_rmappable flag on hugetlb.
hugetlb is rmappable, thus cl... | {
"author": "Zi Yan <ziy@nvidia.com>",
"date": "Thu, 29 Jan 2026 22:48:16 -0500",
"thread_id": "20260130034818.472804-1-ziy@nvidia.com.mbox.gz"
} |
lkml | [RFC PATCH 0/5] Separate compound page from folio | Hi all,
Based on my discussion with Jason about device private folio
reinitialization[1], I realize that the concepts of compound page and folio
are mixed together and confusing, as people think a compound page is equal
to a folio. This is not true, since a compound page means a group of
pages is managed as a whole an... | A compound page is not a folio. Using struct folio in compound_nr() and
compound_order() is misleading. Use struct page and refer to the right
subpage of a compound page to set compound page order. compound_nr() is
calculated using compound_order() instead of reading folio->_nr_pages.
Signed-off-by: Zi Yan <ziy@nvidia... | {
"author": "Zi Yan <ziy@nvidia.com>",
"date": "Thu, 29 Jan 2026 22:48:17 -0500",
"thread_id": "20260130034818.472804-1-ziy@nvidia.com.mbox.gz"
} |
lkml | [RFC PATCH 0/5] Separate compound page from folio | Hi all,
Based on my discussion with Jason about device private folio
reinitialization[1], I realize that the concepts of compound page and folio
are mixed together and confusing, as people think a compound page is equal
to a folio. This is not true, since a compound page means a group of
pages is managed as a whole an... | A compound page is not a folio. Using struct folio in prep_compound_head()
causes confusion, since the input page is not a folio. The compound page to
folio conversion happens in page_rmappable_folio(). So move folio code from
prep_compound_head() to page_rmappable_folio().
After the change, a compound page no longer ... | {
"author": "Zi Yan <ziy@nvidia.com>",
"date": "Thu, 29 Jan 2026 22:48:18 -0500",
"thread_id": "20260130034818.472804-1-ziy@nvidia.com.mbox.gz"
} |
lkml | [RFC PATCH 0/5] Separate compound page from folio | Hi all,
Based on my discussion with Jason about device private folio
reinitialization[1], I realize that the concepts of compound page and folio
are mixed together and confusing, as people think a compound page is equal
to a folio. This is not true, since a compound page means a group of
pages is managed as a whole an... | syzbot ci has tested the following series
[v1] Separate compound page from folio
https://lore.kernel.org/all/20260130034818.472804-1-ziy@nvidia.com
* [RFC PATCH 1/5] io_uring: allocate folio in io_mem_alloc_compound() and function rename
* [RFC PATCH 2/5] mm/huge_memory: use page_rmappable_folio() to convert after-spl... | {
"author": "syzbot ci <syzbot+ci7f632827e1b1c91b@syzkaller.appspotmail.com>",
"date": "Fri, 30 Jan 2026 00:15:47 -0800",
"thread_id": "20260130034818.472804-1-ziy@nvidia.com.mbox.gz"
} |
lkml | [RFC PATCH 0/5] Separate compound page from folio | Hi all,
Based on my discussion with Jason about device private folio
reinitialization[1], I realize that the concepts of compound page and folio
are mixed together and confusing, as people think a compound page is equal
to a folio. This is not true, since a compound page means a group of
pages is managed as a whole an... | On 30 Jan 2026, at 3:15, syzbot ci wrote:
The issue comes from alloc_one_pg_vec_page() in net/packet/af_packet.c.
It allocates a compound page with __GFP_COMP, but latter does vm_insert_page()
in packet_mmap(), using it as a folio.
The fix below is a hack. We will need a get_free_folios() instead.
I will check all _... | {
"author": "Zi Yan <ziy@nvidia.com>",
"date": "Fri, 30 Jan 2026 11:39:40 -0500",
"thread_id": "20260130034818.472804-1-ziy@nvidia.com.mbox.gz"
} |
lkml | [RFC PATCH 0/5] Separate compound page from folio | Hi all,
Based on my discussion with Jason about device private folio
reinitialization[1], I realize that the concepts of compound page and folio
are mixed together and confusing, as people think a compound page is equal
to a folio. This is not true, since a compound page means a group of
pages is managed as a whole an... | On 2026/1/30 11:48, Zi Yan wrote:
Nit:
Since we're switching to folio_alloc(), which already adds __GFP_COMP
internally, the "else if (order)" part above can be dropped while at it.
IIUC, for order == 0, __GFP_COMP gets ignored anyway:
- prep_new_page() won't call prep_compound_page() (since order is zero)
- p... | {
"author": "Lance Yang <lance.yang@linux.dev>",
"date": "Sat, 31 Jan 2026 23:30:35 +0800",
"thread_id": "20260130034818.472804-1-ziy@nvidia.com.mbox.gz"
} |
lkml | [RFC PATCH 0/5] Separate compound page from folio | Hi all,
Based on my discussion with Jason about device private folio
reinitialization[1], I realize that the concepts of compound page and folio
are mixed together and confusing, as people think a compound page is equal
to a folio. This is not true, since a compound page means a group of
pages is managed as a whole an... | On 31 Jan 2026, at 10:30, Lance Yang wrote:
Sure. Will update it in the next version. Thanks.
--
Best Regards,
Yan, Zi | {
"author": "Zi Yan <ziy@nvidia.com>",
"date": "Sat, 31 Jan 2026 21:04:53 -0500",
"thread_id": "20260130034818.472804-1-ziy@nvidia.com.mbox.gz"
} |
lkml | [RFC PATCH 0/5] Separate compound page from folio | Hi all,
Based on my discussion with Jason about device private folio
reinitialization[1], I realize that the concepts of compound page and folio
are mixed together and confusing, as people think a compound page is equal
to a folio. This is not true, since a compound page means a group of
pages is managed as a whole an... | On 1/30/26 11:48 AM, Zi Yan wrote:
IIUC, this will break the semantics of the is_transparent_hugepage() and
might trigger a split of a hugetlb folio, right?
static inline bool is_transparent_hugepage(const struct folio *folio)
{
if (!folio_test_large(folio))
return false;
return is_huge_zero_folio(folio) ||
f... | {
"author": "Baolin Wang <baolin.wang@linux.alibaba.com>",
"date": "Mon, 2 Feb 2026 11:59:39 +0800",
"thread_id": "20260130034818.472804-1-ziy@nvidia.com.mbox.gz"
} |
lkml | [RFC PATCH 0/5] Separate compound page from folio | Hi all,
Based on my discussion with Jason about device private folio
reinitialization[1], I realize that the concepts of compound page and folio
are mixed together and confusing, as people think a compound page is equal
to a folio. This is not true, since a compound page means a group of
pages is managed as a whole an... | On 1 Feb 2026, at 22:59, Baolin Wang wrote:
Oh, I missed this. I will check all folio_test_large_rmappable() callers
and filter out hugetlb if necessary.
Thank you for pointing this out.
Best Regards,
Yan, Zi | {
"author": "Zi Yan <ziy@nvidia.com>",
"date": "Mon, 02 Feb 2026 12:11:45 -0500",
"thread_id": "20260130034818.472804-1-ziy@nvidia.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The "qup-memory" interconnect path is optional and may not be defined
in all device trees. Unroll the loop-based ICC path initialization to
allow specific error handling for each path type.
The "qup-core" and "qup-config" paths remain mandatory and will fail
probe if missing, while "qup-memory" is now handled as optio... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:10 +0530",
"thread_id": "20260202180922.1692428-12-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | Add a new function geni_icc_set_bw_ab() that allows callers to set
average bandwidth values for all ICC (Interconnect) paths in a single
call. This function takes separate parameters for core, config, and DDR
average bandwidth values and applies them to the respective ICC paths.
This provides a more convenient API for... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:11 +0530",
"thread_id": "20260202180922.1692428-12-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The GENI Serial Engine drivers (I2C, SPI, and SERIAL) currently duplicate
code for initializing shared resources such as clocks and interconnect
paths.
Introduce a new helper API, geni_se_resources_init(), to centralize this
initialization logic, improving modularity and simplifying the probe
function.
Signed-off-by:... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:12 +0530",
"thread_id": "20260202180922.1692428-12-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | Currently, core clk is handled individually in protocol drivers like
the I2C driver. Move this clock management to the common clock APIs
(geni_se_clks_on/off) that are already present in the common GENI SE
driver to maintain consistency across all protocol drivers.
Core clk is now properly managed alongside the other ... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:13 +0530",
"thread_id": "20260202180922.1692428-12-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The GENI SE protocol drivers (I2C, SPI, UART) implement similar resource
activation/deactivation sequences independently, leading to code
duplication.
Introduce geni_se_resources_activate()/geni_se_resources_deactivate() to
power on/off resources.The activate function enables ICC, clocks, and TLMM
whereas the deactiva... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:14 +0530",
"thread_id": "20260202180922.1692428-12-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The GENI Serial Engine drivers (I2C, SPI, and SERIAL) currently handle
the attachment of power domains. This often leads to duplicated code
logic across different driver probe functions.
Introduce a new helper API, geni_se_domain_attach(), to centralize
the logic for attaching "power" and "perf" domains to the GENI SE... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:15 +0530",
"thread_id": "20260202180922.1692428-12-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The GENI Serial Engine (SE) drivers (I2C, SPI, and SERIAL) currently
manage performance levels and operating points directly. This resulting
in code duplication across drivers. such as configuring a specific level
or find and apply an OPP based on a clock frequency.
Introduce two new helper APIs, geni_se_set_perf_leve... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:16 +0530",
"thread_id": "20260202180922.1692428-12-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | Add DT bindings for the QUP GENI I2C controller on sa8255p platforms.
SA8255p platform abstracts resources such as clocks, interconnect and
GPIO pins configuration in Firmware. SCMI power and perf protocol
are utilized to request resource configurations.
SA8255p platform does not require the Serial Engine (SE) common... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:17 +0530",
"thread_id": "20260202180922.1692428-12-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | Moving the serial engine setup to geni_i2c_init() API for a cleaner
probe function and utilizes the PM runtime API to control resources
instead of direct clock-related APIs for better resource management.
Enables reusability of the serial engine initialization like
hibernation and deep sleep features where hardware co... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:18 +0530",
"thread_id": "20260202180922.1692428-12-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | Refactor the resource initialization in geni_i2c_probe() by introducing
a new geni_i2c_resources_init() function and utilizing the common
geni_se_resources_init() framework and clock frequency mapping, making the
probe function cleaner.
Acked-by: Viken Dadhaniya <viken.dadhaniya@oss.qualcomm.com>
Signed-off-by: Pravee... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:19 +0530",
"thread_id": "20260202180922.1692428-12-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | To manage GENI serial engine resources during runtime power management,
drivers currently need to call functions for ICC, clock, and
SE resource operations in both suspend and resume paths, resulting in
code duplication across drivers.
The new geni_se_resources_activate() and geni_se_resources_deactivate()
helper APIs... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:20 +0530",
"thread_id": "20260202180922.1692428-12-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | To avoid repeatedly fetching and checking platform data across various
functions, store the struct of_device_id data directly in the i2c
private structure. This change enhances code maintainability and reduces
redundancy.
Acked-by: Viken Dadhaniya <viken.dadhaniya@oss.qualcomm.com>
Signed-off-by: Praveen Talari <prave... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:21 +0530",
"thread_id": "20260202180922.1692428-12-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:22 +0530",
"thread_id": "20260202180922.1692428-12-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH] staging: sm750fb: rename Bpp to bpp | Rename the Bpp parameter to bpp to avoid CamelCase, as reported by
checkpatch.pl.
Signed-off-by: yehudis9982 <y0533159982@gmail.com>
---
drivers/staging/sm750fb/sm750_accel.c | 22 +++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/drivers/staging/sm750fb/sm750_accel.c b/drivers/st... | On Mon, Feb 02, 2026 at 04:54:13PM +0200, yehudis9982 wrote:
What does "bpp" stand for? Perhaps spell it out further?
thanks,
greg k-h | {
"author": "Greg KH <gregkh@linuxfoundation.org>",
"date": "Mon, 2 Feb 2026 16:01:17 +0100",
"thread_id": "20260202171243.133935-1-y0533159982@gmail.com.mbox.gz"
} |
lkml | [PATCH] staging: sm750fb: rename Bpp to bpp | Rename the Bpp parameter to bpp to avoid CamelCase, as reported by
checkpatch.pl.
Signed-off-by: yehudis9982 <y0533159982@gmail.com>
---
drivers/staging/sm750fb/sm750_accel.c | 22 +++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/drivers/staging/sm750fb/sm750_accel.c b/drivers/st... | Rename the Bpp parameter to bytes_per_pixel for clarity and to avoid CamelCase, as reported by checkpatch.pl.
Signed-off-by: yehudis9982 <y0533159982@gmail.com>
---
drivers/staging/sm750fb/sm750_accel.c | 26 +++++++++++++-------------
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/drivers/staging/sm... | {
"author": "yehudis9982 <y0533159982@gmail.com>",
"date": "Mon, 2 Feb 2026 18:46:45 +0200",
"thread_id": "20260202171243.133935-1-y0533159982@gmail.com.mbox.gz"
} |
lkml | [PATCH] staging: sm750fb: rename Bpp to bpp | Rename the Bpp parameter to bpp to avoid CamelCase, as reported by
checkpatch.pl.
Signed-off-by: yehudis9982 <y0533159982@gmail.com>
---
drivers/staging/sm750fb/sm750_accel.c | 22 +++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/drivers/staging/sm750fb/sm750_accel.c b/drivers/st... | Rename the Bpp parameter to bytes_per_pixel for clarity and to avoid CamelCase, as reported by checkpatch.pl.
Signed-off-by: yehudis9982 <y0533159982@gmail.com>
---
drivers/staging/sm750fb/sm750_accel.c | 26 +++++++++++++-------------
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/drivers/staging/sm... | {
"author": "yehudis9982 <y0533159982@gmail.com>",
"date": "Mon, 2 Feb 2026 18:57:18 +0200",
"thread_id": "20260202171243.133935-1-y0533159982@gmail.com.mbox.gz"
} |
lkml | [PATCH] staging: sm750fb: rename Bpp to bpp | Rename the Bpp parameter to bpp to avoid CamelCase, as reported by
checkpatch.pl.
Signed-off-by: yehudis9982 <y0533159982@gmail.com>
---
drivers/staging/sm750fb/sm750_accel.c | 22 +++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/drivers/staging/sm750fb/sm750_accel.c b/drivers/st... | Rename the Bpp parameter to bytes_per_pixel for clarity and to avoid CamelCase, as reported by checkpatch.pl.
Signed-off-by: yehudis9982 <y0533159982@gmail.com>
---
drivers/staging/sm750fb/sm750_accel.c | 26 +++++++++++++-------------
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/drivers/staging/sm... | {
"author": "yehudis9982 <y0533159982@gmail.com>",
"date": "Mon, 2 Feb 2026 19:12:43 +0200",
"thread_id": "20260202171243.133935-1-y0533159982@gmail.com.mbox.gz"
} |
lkml | [PATCH v3 0/3] Convert 64-bit x86/mm/pat to ptdescs | x86/mm/pat should be using ptdescs. One line has already been
converted to pagetable_free(), while the allocation sites use
get_free_pages(). This causes issues separately allocating ptdescs
from struct page.
These patches convert the allocation/free sites to use ptdescs. In
the short term, this helps enable Matthew's... | In order to separately allocate ptdescs from pages, we need all allocation
and free sites to use the appropriate functions. Convert these pte
allocation/free sites to use ptdescs.
Signed-off-by: Vishal Moola (Oracle) <vishal.moola@gmail.com>
---
arch/x86/mm/pat/set_memory.c | 15 +++++++++------
1 file changed, 9 ins... | {
"author": "\"Vishal Moola (Oracle)\" <vishal.moola@gmail.com>",
"date": "Mon, 2 Feb 2026 09:20:03 -0800",
"thread_id": "20260202172005.683870-2-vishal.moola@gmail.com.mbox.gz"
} |
lkml | [PATCH v3 0/3] Convert 64-bit x86/mm/pat to ptdescs | x86/mm/pat should be using ptdescs. One line has already been
converted to pagetable_free(), while the allocation sites use
get_free_pages(). This causes issues separately allocating ptdescs
from struct page.
These patches convert the allocation/free sites to use ptdescs. In
the short term, this helps enable Matthew's... | In order to separately allocate ptdescs from pages, we need all allocation
and free sites to use the appropriate functions.
split_large_page() allocates a page to be used as a page table. This
should be allocating a ptdesc, so convert it.
Signed-off-by: Vishal Moola (Oracle) <vishal.moola@gmail.com>
---
arch/x86/mm/... | {
"author": "\"Vishal Moola (Oracle)\" <vishal.moola@gmail.com>",
"date": "Mon, 2 Feb 2026 09:20:05 -0800",
"thread_id": "20260202172005.683870-2-vishal.moola@gmail.com.mbox.gz"
} |
lkml | [PATCH v3 0/3] Convert 64-bit x86/mm/pat to ptdescs | x86/mm/pat should be using ptdescs. One line has already been
converted to pagetable_free(), while the allocation sites use
get_free_pages(). This causes issues separately allocating ptdescs
from struct page.
These patches convert the allocation/free sites to use ptdescs. In
the short term, this helps enable Matthew's... | In order to separately allocate ptdescs from pages, we need all allocation
and free sites to use the appropriate functions. Convert these pmd
allocation/free sites to use ptdescs.
populate_pgd() also allocates pagetables that may later be freed by
try_to_free_pmd_page(), so allocate ptdescs there as well.
Signed-off-... | {
"author": "\"Vishal Moola (Oracle)\" <vishal.moola@gmail.com>",
"date": "Mon, 2 Feb 2026 09:20:04 -0800",
"thread_id": "20260202172005.683870-2-vishal.moola@gmail.com.mbox.gz"
} |
lkml | [PATCH net-next v4 0/9] dpll: Core improvements and ice E825-C SyncE support | This series introduces Synchronous Ethernet (SyncE) support for the Intel
E825-C Ethernet controller. Unlike previous generations where DPLL
connections were implicitly assumed, the E825-C architecture relies
on the platform firmware (ACPI) to describe the physical connections
between the Ethernet controller and extern... | Extend the DPLL core to support associating a DPLL pin with a firmware
node. This association is required to allow other subsystems (such as
network drivers) to locate and request specific DPLL pins defined in
the Device Tree or ACPI.
* Add a .fwnode field to the struct dpll_pin
* Introduce dpll_pin_fwnode_set() helpe... | {
"author": "Ivan Vecera <ivecera@redhat.com>",
"date": "Mon, 2 Feb 2026 18:16:30 +0100",
"thread_id": "20260202171638.17427-5-ivecera@redhat.com.mbox.gz"
} |
lkml | [PATCH net-next v4 0/9] dpll: Core improvements and ice E825-C SyncE support | This series introduces Synchronous Ethernet (SyncE) support for the Intel
E825-C Ethernet controller. Unlike previous generations where DPLL
connections were implicitly assumed, the E825-C architecture relies
on the platform firmware (ACPI) to describe the physical connections
between the Ethernet controller and extern... | Associate the registered DPLL pin with its firmware node by calling
dpll_pin_fwnode_set().
This links the created pin object to its corresponding DT/ACPI node
in the DPLL core. Consequently, this enables consumer drivers (such as
network drivers) to locate and request this specific pin using the
fwnode_dpll_pin_find()... | {
"author": "Ivan Vecera <ivecera@redhat.com>",
"date": "Mon, 2 Feb 2026 18:16:31 +0100",
"thread_id": "20260202171638.17427-5-ivecera@redhat.com.mbox.gz"
} |
lkml | [PATCH net-next v4 0/9] dpll: Core improvements and ice E825-C SyncE support | This series introduces Synchronous Ethernet (SyncE) support for the Intel
E825-C Ethernet controller. Unlike previous generations where DPLL
connections were implicitly assumed, the E825-C architecture relies
on the platform firmware (ACPI) to describe the physical connections
between the Ethernet controller and extern... | From: Petr Oros <poros@redhat.com>
Currently, the DPLL subsystem reports events (creation, deletion, changes)
to userspace via Netlink. However, there is no mechanism for other kernel
components to be notified of these events directly.
Add a raw notifier chain to the DPLL core protected by dpll_lock. This
allows othe... | {
"author": "Ivan Vecera <ivecera@redhat.com>",
"date": "Mon, 2 Feb 2026 18:16:32 +0100",
"thread_id": "20260202171638.17427-5-ivecera@redhat.com.mbox.gz"
} |
lkml | [PATCH net-next v4 0/9] dpll: Core improvements and ice E825-C SyncE support | This series introduces Synchronous Ethernet (SyncE) support for the Intel
E825-C Ethernet controller. Unlike previous generations where DPLL
connections were implicitly assumed, the E825-C architecture relies
on the platform firmware (ACPI) to describe the physical connections
between the Ethernet controller and extern... | Allow drivers to register DPLL pins without manually specifying a pin
index.
Currently, drivers must provide a unique pin index when calling
dpll_pin_get(). This works well for hardware-mapped pins but creates
friction for drivers handling virtual pins or those without a strict
hardware indexing scheme.
Introduce DPL... | {
"author": "Ivan Vecera <ivecera@redhat.com>",
"date": "Mon, 2 Feb 2026 18:16:33 +0100",
"thread_id": "20260202171638.17427-5-ivecera@redhat.com.mbox.gz"
} |
lkml | [PATCH net-next v4 0/9] dpll: Core improvements and ice E825-C SyncE support | This series introduces Synchronous Ethernet (SyncE) support for the Intel
E825-C Ethernet controller. Unlike previous generations where DPLL
connections were implicitly assumed, the E825-C architecture relies
on the platform firmware (ACPI) to describe the physical connections
between the Ethernet controller and extern... | Add parsing for the "mux" string in the 'connection-type' pin property
mapping it to DPLL_PIN_TYPE_MUX.
Recognizing this type in the driver allows these pins to be taken as
parent pins for pin-on-pin pins coming from different modules (e.g.
network drivers).
Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@intel... | {
"author": "Ivan Vecera <ivecera@redhat.com>",
"date": "Mon, 2 Feb 2026 18:16:34 +0100",
"thread_id": "20260202171638.17427-5-ivecera@redhat.com.mbox.gz"
} |
lkml | [PATCH net-next v4 0/9] dpll: Core improvements and ice E825-C SyncE support | This series introduces Synchronous Ethernet (SyncE) support for the Intel
E825-C Ethernet controller. Unlike previous generations where DPLL
connections were implicitly assumed, the E825-C architecture relies
on the platform firmware (ACPI) to describe the physical connections
between the Ethernet controller and extern... | Refactor the reference counting mechanism for DPLL devices and pins to
improve consistency and prevent potential lifetime issues.
Introduce internal helpers __dpll_{device,pin}_{hold,put}() to
centralize reference management.
Update the internal XArray reference helpers (dpll_xa_ref_*) to
automatically grab a referen... | {
"author": "Ivan Vecera <ivecera@redhat.com>",
"date": "Mon, 2 Feb 2026 18:16:35 +0100",
"thread_id": "20260202171638.17427-5-ivecera@redhat.com.mbox.gz"
} |
lkml | [PATCH net-next v4 0/9] dpll: Core improvements and ice E825-C SyncE support | This series introduces Synchronous Ethernet (SyncE) support for the Intel
E825-C Ethernet controller. Unlike previous generations where DPLL
connections were implicitly assumed, the E825-C architecture relies
on the platform firmware (ACPI) to describe the physical connections
between the Ethernet controller and extern... | Add support for the REF_TRACKER infrastructure to the DPLL subsystem.
When enabled, this allows developers to track and debug reference counting
leaks or imbalances for dpll_device and dpll_pin objects. It records stack
traces for every get/put operation and exposes this information via
debugfs at:
/sys/kernel/debug... | {
"author": "Ivan Vecera <ivecera@redhat.com>",
"date": "Mon, 2 Feb 2026 18:16:36 +0100",
"thread_id": "20260202171638.17427-5-ivecera@redhat.com.mbox.gz"
} |
lkml | [PATCH net-next v4 0/9] dpll: Core improvements and ice E825-C SyncE support | This series introduces Synchronous Ethernet (SyncE) support for the Intel
E825-C Ethernet controller. Unlike previous generations where DPLL
connections were implicitly assumed, the E825-C architecture relies
on the platform firmware (ACPI) to describe the physical connections
between the Ethernet controller and extern... | Update existing DPLL drivers to utilize the DPLL reference count
tracking infrastructure.
Add dpll_tracker fields to the drivers' internal device and pin
structures. Pass pointers to these trackers when calling
dpll_device_get/put() and dpll_pin_get/put().
This allows developers to inspect the specific references hel... | {
"author": "Ivan Vecera <ivecera@redhat.com>",
"date": "Mon, 2 Feb 2026 18:16:37 +0100",
"thread_id": "20260202171638.17427-5-ivecera@redhat.com.mbox.gz"
} |
lkml | [PATCH net-next v4 0/9] dpll: Core improvements and ice E825-C SyncE support | This series introduces Synchronous Ethernet (SyncE) support for the Intel
E825-C Ethernet controller. Unlike previous generations where DPLL
connections were implicitly assumed, the E825-C architecture relies
on the platform firmware (ACPI) to describe the physical connections
between the Ethernet controller and extern... | From: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Implement SyncE support for the E825-C Ethernet controller using the
DPLL subsystem. Unlike E810, the E825-C architecture relies on platform
firmware (ACPI) to describe connections between the NIC's recovered clock
outputs and external DPLL inputs.
Implement... | {
"author": "Ivan Vecera <ivecera@redhat.com>",
"date": "Mon, 2 Feb 2026 18:16:38 +0100",
"thread_id": "20260202171638.17427-5-ivecera@redhat.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | Move struct bpf_struct_ops_link's definition into bpf.h,
where other custom bpf links definitions are.
It's necessary to access its members from outside of generic
bpf_struct_ops implementation, which will be done by following
patches in the series.
Signed-off-by: Roman Gushchin <roman.gushchin@linux.dev>
---
includ... | {
"author": "Roman Gushchin <roman.gushchin@linux.dev>",
"date": "Mon, 26 Jan 2026 18:44:04 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | Introduce an ability to attach bpf struct_ops'es to cgroups.
a user passes a BPF_F_CGROUP_FD flag and specifies the target cgroup
fd while creating a struct_ops link. As the result, the bpf struct_ops
link will be created and attached to a cgroup.
The cgroup.bpf structure maintains a list of attached struct ops links... | {
"author": "Roman Gushchin <roman.gushchin@linux.dev>",
"date": "Mon, 26 Jan 2026 18:44:05 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | bpf_map__attach_struct_ops() returns -EINVAL instead of -ENOMEM
on the memory allocation failure. Fix it.
Fixes: 590a00888250 ("bpf: libbpf: Add STRUCT_OPS support")
Signed-off-by: Roman Gushchin <roman.gushchin@linux.dev>
---
tools/lib/bpf/libbpf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/... | {
"author": "Roman Gushchin <roman.gushchin@linux.dev>",
"date": "Mon, 26 Jan 2026 18:44:06 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | Introduce bpf_map__attach_struct_ops_opts(), an extended version of
bpf_map__attach_struct_ops(), which takes additional struct
bpf_struct_ops_opts argument.
This allows to pass a target_fd argument and the BPF_F_CGROUP_FD flag
and attach the struct ops to a cgroup as a result.
Signed-off-by: Roman Gushchin <roman.gu... | {
"author": "Roman Gushchin <roman.gushchin@linux.dev>",
"date": "Mon, 26 Jan 2026 18:44:07 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | Struct oom_control is used to describe the OOM context.
It's memcg field defines the scope of OOM: it's NULL for global
OOMs and a valid memcg pointer for memcg-scoped OOMs.
Teach bpf verifier to recognize it as trusted or NULL pointer.
It will provide the bpf OOM handler a trusted memcg pointer,
which for example is r... | {
"author": "Roman Gushchin <roman.gushchin@linux.dev>",
"date": "Mon, 26 Jan 2026 18:44:08 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | mem_cgroup_get_from_ino() can be reused by the BPF OOM implementation,
but currently depends on CONFIG_SHRINKER_DEBUG. Remove this dependency.
Signed-off-by: Roman Gushchin <roman.gushchin@linux.dev>
Acked-by: Michal Hocko <mhocko@suse.com>
---
include/linux/memcontrol.h | 4 ++--
mm/memcontrol.c | 2 --
2... | {
"author": "Roman Gushchin <roman.gushchin@linux.dev>",
"date": "Mon, 26 Jan 2026 18:44:09 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | Introduce a bpf struct ops for implementing custom OOM handling
policies.
It's possible to load one bpf_oom_ops for the system and one
bpf_oom_ops for every memory cgroup. In case of a memcg OOM, the
cgroup tree is traversed from the OOM'ing memcg up to the root and
corresponding BPF OOM handlers are executed until so... | {
"author": "Roman Gushchin <roman.gushchin@linux.dev>",
"date": "Mon, 26 Jan 2026 18:44:10 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | Introduce bpf_oom_kill_process() bpf kfunc, which is supposed
to be used by BPF OOM programs. It allows to kill a process
in exactly the same way the OOM killer does: using the OOM reaper,
bumping corresponding memcg and global statistics, respecting
memory.oom.group etc.
On success, it sets the oom_control's bpf_memo... | {
"author": "Roman Gushchin <roman.gushchin@linux.dev>",
"date": "Mon, 26 Jan 2026 18:44:11 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | Introduce bpf_out_of_memory() bpf kfunc, which allows to declare
an out of memory events and trigger the corresponding kernel OOM
handling mechanism.
It takes a trusted memcg pointer (or NULL for system-wide OOMs)
as an argument, as well as the page order.
If the BPF_OOM_FLAGS_WAIT_ON_OOM_LOCK flag is not set, only o... | {
"author": "Roman Gushchin <roman.gushchin@linux.dev>",
"date": "Mon, 26 Jan 2026 18:44:12 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | Export tsk_is_oom_victim() helper as a BPF kfunc.
It's very useful to avoid redundant oom kills.
Signed-off-by: Roman Gushchin <roman.gushchin@linux.dev>
Suggested-by: Michal Hocko <mhocko@suse.com>
---
mm/oom_kill.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/mm/oom_kill.c b/mm/oom_kill.c
ind... | {
"author": "Roman Gushchin <roman.gushchin@linux.dev>",
"date": "Mon, 26 Jan 2026 18:44:13 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | Implement read_cgroup_file() helper to read from cgroup control files,
e.g. statistics.
Signed-off-by: Roman Gushchin <roman.gushchin@linux.dev>
---
tools/testing/selftests/bpf/cgroup_helpers.c | 45 ++++++++++++++++++++
tools/testing/selftests/bpf/cgroup_helpers.h | 3 ++
2 files changed, 48 insertions(+)
diff --g... | {
"author": "Roman Gushchin <roman.gushchin@linux.dev>",
"date": "Mon, 26 Jan 2026 18:44:14 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | Implement a kselftest for the OOM handling functionality.
The OOM handling policy which is implemented in BPF is to
kill all tasks belonging to the biggest leaf cgroup, which
doesn't contain unkillable tasks (tasks with oom_score_adj
set to -1000). Pagecache size is excluded from the accounting.
The test creates a hi... | {
"author": "Roman Gushchin <roman.gushchin@linux.dev>",
"date": "Mon, 26 Jan 2026 18:44:15 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | Add a trace point to psi_avgs_work().
It can be used to attach a bpf handler which can monitor
PSI values system-wide or for specific cgroup(s) and
potentially perform some actions, e.g. declare an OOM.
Signed-off-by: Roman Gushchin <roman.gushchin@linux.dev>
---
include/trace/events/psi.h | 27 +++++++++++++++++++++... | {
"author": "Roman Gushchin <roman.gushchin@linux.dev>",
"date": "Mon, 26 Jan 2026 18:44:16 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | To allow a more efficient filtering of cgroups in the psi work
tracepoint handler, let's add a u64 cgroup_id field to the psi_group
structure. For system PSI, 0 will be used.
Signed-off-by: Roman Gushchin <roman.gushchin@linux.dev>
---
include/linux/psi_types.h | 4 ++++
kernel/sched/psi.c | 1 +
2 files chang... | {
"author": "Roman Gushchin <roman.gushchin@linux.dev>",
"date": "Mon, 26 Jan 2026 18:44:17 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | Allow calling bpf_out_of_memory() from a PSI tracepoint to enable
PSI-based OOM killer policies.
Signed-off-by: Roman Gushchin <roman.gushchin@linux.dev>
---
mm/oom_kill.c | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/mm/oom_kill.c b/mm/oom_kill.c
index 53f9f9674658..276cf8a34449 10064... | {
"author": "Roman Gushchin <roman.gushchin@linux.dev>",
"date": "Mon, 26 Jan 2026 18:44:18 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | [ ... ]
^^^^^^^^^^^^^^^^^^^^^^^^
This isn't a bug, but should this say "Buffer to store data read from the
file" or "Buffer to read into"? The current wording suggests data is read
from the buffer, but the code reads from the file into the buffer. Compare
with write_cgroup_file() which says "Buffer to write... | {
"author": "bot+bpf-ci@kernel.org",
"date": "Tue, 27 Jan 2026 03:08:46 +0000 (UTC)",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | [ ... ]
Can this code access st_link after it has been freed?
Once st_link->cgroup is set to NULL, if another CPU concurrently closes
the link FD, bpf_struct_ops_map_link_dealloc() will see st_link->cgroup
as NULL, skip the cgroup_bpf_detach_struct_ops() call, and proceed to
kfree(st_link). Then the bpf_link_inc_not... | {
"author": "bot+bpf-ci@kernel.org",
"date": "Tue, 27 Jan 2026 03:08:48 +0000 (UTC)",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | [ ... ]
The code reads flags and target_fd from opts, but the expected_revision field
declared in struct bpf_struct_ops_opts is never read. Looking at similar opts
structures (bpf_cgroup_opts, bpf_tcx_opts, bpf_netkit_opts), they all pass
expected_revision to bpf_link_create_opts. For example:
link_create_opts.c... | {
"author": "bot+bpf-ci@kernel.org",
"date": "Tue, 27 Jan 2026 03:08:49 +0000 (UTC)",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | On Tue, Jan 27, 2026 at 10:47 AM Roman Gushchin
<roman.gushchin@linux.dev> wrote:
Since both fdinfo and link_info show the cgroup ID, why not use
BPF_F_CGROUP_ID for better alignment?
We may need to support other structs in the future.
Could we implement a more generic solution, such as:
int type; // cg... | {
"author": "Yafang Shao <laoar.shao@gmail.com>",
"date": "Tue, 27 Jan 2026 13:49:18 +0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | On Tue, Jan 27, 2026 at 10:46 AM Roman Gushchin
<roman.gushchin@linux.dev> wrote:
Feel free to add:
Acked-by: Yafang Shao <laoar.shao@gmail.com>
--
Regards
Yafang | {
"author": "Yafang Shao <laoar.shao@gmail.com>",
"date": "Tue, 27 Jan 2026 13:50:31 +0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | On Tue, Jan 27, 2026 at 10:53 AM Roman Gushchin
<roman.gushchin@linux.dev> wrote:
Acked-by: Yafang Shao <laoar.shao@gmail.com>
--
Regards
Yafang | {
"author": "Yafang Shao <laoar.shao@gmail.com>",
"date": "Tue, 27 Jan 2026 13:52:41 +0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | On Tue, Jan 27, 2026 at 10:49 AM Roman Gushchin
<roman.gushchin@linux.dev> wrote:
Acked-by: Yafang Shao <laoar.shao@gmail.com>
--
Regards
Yafang | {
"author": "Yafang Shao <laoar.shao@gmail.com>",
"date": "Tue, 27 Jan 2026 14:06:20 +0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | On Tue, Jan 27, 2026 at 10:49 AM Roman Gushchin
<roman.gushchin@linux.dev> wrote:
Given that mem_cgroup_ino() pairs with mem_cgroup_get_from_ino(),
should we also define mem_cgroup_ino() outside CONFIG_SHRINKER_DEBUG?
--
Regards
Yafang | {
"author": "Yafang Shao <laoar.shao@gmail.com>",
"date": "Tue, 27 Jan 2026 14:12:17 +0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | On Mon 26-01-26 18:44:03, Roman Gushchin wrote:
Are you planning to write any highlevel documentation on how to use the
existing infrastructure to implement proper/correct OOM handlers with
these generic interfaces?
--
Michal Hocko
SUSE Labs | {
"author": "Michal Hocko <mhocko@suse.com>",
"date": "Tue, 27 Jan 2026 10:02:38 +0100",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | On Mon 26-01-26 18:44:10, Roman Gushchin wrote:
I still find this dual reporting a bit confusing. I can see your
intention in having a pre-defined "releasers" of the memory to trust BPF
handlers more but they do have access to oc->bpf_memory_freed so they
can manipulate it. Therefore an additional level of protection ... | {
"author": "Michal Hocko <mhocko@suse.com>",
"date": "Tue, 27 Jan 2026 10:38:42 +0100",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | On 1/26/26 6:44 PM, Roman Gushchin wrote:
The filter callback is registered for BPF_PROG_TYPE_STRUCT_OPS. It is
checking if a kfunc_id is allowed for other struct_ops progs also, e.g.
the bpf-tcp-cc struct_ops progs.
The 'return -EACCES' should be the cause of the "calling kernel function
XXX is not allowed" err... | {
"author": "Martin KaFai Lau <martin.lau@linux.dev>",
"date": "Tue, 27 Jan 2026 12:21:03 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | Martin KaFai Lau <martin.lau@linux.dev> writes:
Oh, I see.. It's a bit surprising that these .filter() functions
have non-local effects...
Will fix in v4.
Thank you, Martin! | {
"author": "Roman Gushchin <roman.gushchin@linux.dev>",
"date": "Tue, 27 Jan 2026 20:47:11 +0000",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | Michal Hocko <mhocko@suse.com> writes:
What do you expect from such a document, can you, please, elaborate?
I'm asking because the main promise of bpf is to provide some sort
of a safe playground, so anyone can experiment with writing their
bpf implementations (like sched_ext schedulers or bpf oom policies)
with mini... | {
"author": "Roman Gushchin <roman.gushchin@linux.dev>",
"date": "Tue, 27 Jan 2026 21:01:48 +0000",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | Michal Hocko <mhocko@suse.com> writes:
No, they can't. They have only a read-only access.
It's a good question, I see your point...
Basically we want to give a handler an option to exit with "I promise,
some memory will be freed soon" without doing anything destructive.
But keeping it save at the same time.
I don'... | {
"author": "Roman Gushchin <roman.gushchin@linux.dev>",
"date": "Tue, 27 Jan 2026 21:12:56 +0000",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | Hi Roman,
On Mon, Jan 26, 2026 at 6:50 PM Roman Gushchin <roman.gushchin@linux.dev> wrote:
[snip]
I was worried about concurrency with cgroup ops until I saw
cgroup_bpf_detach_struct_ops() takes cgroup_lock() internally (since
you take it inline sometimes below I falsely assumed it wasn't
present). In any case, I'm w... | {
"author": "Josh Don <joshdon@google.com>",
"date": "Tue, 27 Jan 2026 19:10:35 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | Thanks Roman!
On Mon, Jan 26, 2026 at 6:51 PM Roman Gushchin <roman.gushchin@linux.dev> wrote:
If bpf claims to have freed memory but didn't actually do so, that
seems like something potentially worth alerting to. Perhaps something
to add to the oom header output? | {
"author": "Josh Don <joshdon@google.com>",
"date": "Tue, 27 Jan 2026 19:26:57 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | On Tue 27-01-26 21:12:56, Roman Gushchin wrote:
Could you explain this a bit more. This must be some BPF magic because
they are getting a standard pointer to oom_control.
Yes, something like OOM_BACKOFF, OOM_PROCESSED, OOM_FAILED.
Counters usually do not work very well for async operations. In this
case there is ... | {
"author": "Michal Hocko <mhocko@suse.com>",
"date": "Wed, 28 Jan 2026 09:00:45 +0100",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | On Tue 27-01-26 21:01:48, Roman Gushchin wrote:
Sure. Essentially an expected structure of the handler. What is the API
it can use, what is has to do and what it must not do. Essentially a
single place you can read and get enough information to start developing
your oom handler.
Examples are really great but having ... | {
"author": "Michal Hocko <mhocko@suse.com>",
"date": "Wed, 28 Jan 2026 09:06:14 +0100",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | Once additional point I forgot to mention previously
On Mon 26-01-26 18:44:10, Roman Gushchin wrote:
Should this check for is_sysrq_oom and always use the in kernel OOM
handling for Sysrq triggered ooms as a failsafe measure?
--
Michal Hocko
SUSE Labs | {
"author": "Michal Hocko <mhocko@suse.com>",
"date": "Wed, 28 Jan 2026 12:19:42 +0100",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | On Mon, Jan 26, 2026 at 06:44:05PM -0800, Roman Gushchin wrote:
Assigning 0 to cgrp_id would technically be incorrect, right? Like,
cgroup_id() for !CONFIG_CGROUPS default to returning 1, and for
CONFIG_CGROUPS the ID allocation is done via the idr_alloc_cyclic()
API using a range between 1 and INT_MAX. Perhaps here i... | {
"author": "Matt Bobrowski <mattbobrowski@google.com>",
"date": "Wed, 28 Jan 2026 11:25:31 +0000",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | On Mon, Jan 26, 2026 at 06:44:04PM -0800, Roman Gushchin wrote:
Looks OK to me:
Acked-by: Matt Bobrowski <mattbobrowski@google.com> | {
"author": "Matt Bobrowski <mattbobrowski@google.com>",
"date": "Wed, 28 Jan 2026 11:28:48 +0000",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | On Wed, Jan 28, 2026 at 12:06 AM Michal Hocko <mhocko@suse.com> wrote:
Production ready bpf-oom program(s) must be part of this set.
We've seen enough attempts to add bpf st_ops in various parts of
the kernel without providing realistic bpf progs that will drive
those hooks. It's great to have flexibility and people n... | {
"author": "Alexei Starovoitov <alexei.starovoitov@gmail.com>",
"date": "Wed, 28 Jan 2026 08:59:34 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | Alexei Starovoitov <alexei.starovoitov@gmail.com> writes:
In my case it's not about hiding, it's a chicken and egg problem:
the upstream first model contradicts with the idea to include the
production results into the patchset. In other words, I want to settle
down the interface before shipping something to prod.
I ... | {
"author": "Roman Gushchin <roman.gushchin@linux.dev>",
"date": "Wed, 28 Jan 2026 10:23:34 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | Michal Hocko <mhocko@suse.com> writes:
Yes, but bpf programs (unlike kernel modules) are going through the
verifier when being loaded to the kernel. The verifier ensures that
programs are safe: e.g. they can't access memory outside of safe areas,
they can't can infinite loops, dereference a NULL pointer etc.
So even... | {
"author": "Roman Gushchin <roman.gushchin@linux.dev>",
"date": "Wed, 28 Jan 2026 10:44:46 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | Josh Don <joshdon@google.com> writes:
Hi Josh!
Sure, good point.
Agree, will add.
Thanks! | {
"author": "Roman Gushchin <roman.gushchin@linux.dev>",
"date": "Wed, 28 Jan 2026 10:52:05 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH bpf-next v3 00/17] mm: BPF OOM | This patchset adds an ability to customize the out of memory
handling using bpf.
It focuses on two parts:
1) OOM handling policy,
2) PSI-based OOM invocation.
The idea to use bpf for customizing the OOM handling is not new, but
unlike the previous proposal [1], which augmented the existing task
ranking policy, this o... | Michal Hocko <mhocko@suse.com> writes:
Yep, good point. Will implement in v4.
Thanks! | {
"author": "Roman Gushchin <roman.gushchin@linux.dev>",
"date": "Wed, 28 Jan 2026 10:53:20 -0800",
"thread_id": "CAADnVQL3+huSAwoYRexoSDaLRK+nEsY6UUnVSmhk_sGYUYsO7Q@mail.gmail.com.mbox.gz"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.