Skip to contentSkip to conversation

linux-yocto/6.16: cfg: fix audit warnings

PATCH In review [email protected] 3 participants 4 messages Sep 10, 2025 – Sep 15, 2025

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 linux-yocto/6.16: cfg: fix audit warnings

From: Bruce Ashfield <[email protected]>

Integrating the following commit(s) to linux-yocto/.:

1/4 [
Author: Bruce Ashfield
Email: [email protected]
Subject: guest: make DRM guest options arch specific
Date: Wed, 10 Sep 2025 13:38:37 -0400

We only need some of the extended DRM options if the guest is x86-64 or arm64, otherwise, we get configuration warnings as the options are not valid.

Restrict the architectures and we get a clean configuration and can build packages like vboxguestdrivers.

]

2/4 [
Author: Bruce Ashfield
Email: [email protected]
Subject: debug-sched: drop SCHED_DEBUG
Date: Wed, 10 Sep 2025 14:51:19 -0400

Yes, we could drop the entire fragment, but then users of it would get config errors unessarily. We keep it to ensure that CONFIG_PROC is around in small configurations.

This is dropped due to:

commit b52173065e0aad82a31863bb5f63ebe46f7eb657
Author: Ingo Molnar <[email protected]>
Date: Mon Mar 17 11:42:56 2025 +0100

sched/debug: Remove CONFIG_SCHED_DEBUG

For more than a decade, CONFIG_SCHED_DEBUG=y has been enabled in all the major Linux distributions:

/boot/config-6.11.0-19-generic:CONFIG_SCHED_DEBUG=y

The reason is that while originally CONFIG_SCHED_DEBUG started out as a debugging feature, over the years (decades ...) it has grown various bits of statistics, instrumentation and control knobs that are useful for sysadmin and general software development purposes as well.

But within the kernel we still pretend that there's a choice, and sometimes code that is seemingly 'debug only' creates overhead that should be optimized in reality.

So make it all official and make CONFIG_SCHED_DEBUG unconditional.

Now that all uses of CONFIG_SCHED_DEBUG are removed from the code by previous patches, remove the Kconfig option as well.

Cc Peter Zijlstra <[email protected]>
Cc Juri Lelli <[email protected]>
Cc Vincent Guittot <[email protected]>
Cc Dietmar Eggemann <[email protected]>
Cc Steven Rostedt <[email protected]>
Cc Ben Segall <[email protected]>
Cc Mel Gorman <[email protected]>
Cc Valentin Schneider <[email protected]>
Cc Linus Torvalds <[email protected]>

]

3/4 [
Author: Bruce Ashfield
Email: [email protected]
Subject: x86: drop CONFIG_HIGHPTE
Date: Wed, 10 Sep 2025 15:05:46 -0400

commit 0081fdeccbf610499b79784998b1fd36783209dd
Author: Arnd Bergmann <[email protected]>
Date: Wed Feb 26 22:37:11 2025 +0100

x86/mm: Drop support for CONFIG_HIGHPTE

With the maximum amount of RAM now 4GB, there is very little point to still have PTE pages in highmem. Drop this for simplification.

The only other architecture supporting HIGHPTE is 32-bit arm, and once that feature is removed as well, the highpte logic can be dropped from common code as well.

]

4/4 [
Author: Bruce Ashfield
Email: [email protected]
Subject: hostap: drop obselete LIB80211
Date: Wed, 10 Sep 2025 15:19:37 -0400

These options are no longer valid in 6.16+

commit 02f220b5267042d0de649614eec84ded8aeecb4f
Author: Johannes Berg <[email protected]>
Date: Mon Oct 7 20:26:55 2024 +0200

wifi: ipw2x00/lib80211: move remaining lib80211 into libipw

There's already much code in libipw that used to be shared with more drivers, but now with the prior cleanups, those old Intel ipw2x00 drivers are also the only ones using whatever is now left of lib80211. Move lib80211 entirely into libipw.

]

---

Richard,

Apply these on top of all my previous patches.

They fix the overly agressive DRM options I enabled and address some of the warnings in other configurations that had slipped through.

There may still be some issues lurking, but this will definitely improve things.

Bruce

 meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_6.16.bb      | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb +1 -1
index 7725bcf20b..b86748d7d5 100644
@@ -15,7 +15,7 @@ python () {
 }
 
 SRCREV_machine ?= "c631c6cf05de829937afe048e6ae2fea15634cc8"
-SRCREV_meta ?= "5b4b90bbad3ada455c7c124bf704c519c6013aa1"
+SRCREV_meta ?= "6cd9824a84b5fd5c8557208a787252e31a063436"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine;protocol=https \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-6.16;destsuffix=${KMETA};protocol=https"
meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb +1 -1
index befced7a98..254e6727fe 100644
@@ -18,7 +18,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "01bcf423b031a36a070c7a983e45992e634fceb7"
-SRCREV_meta ?= "5b4b90bbad3ada455c7c124bf704c519c6013aa1"
+SRCREV_meta ?= "6cd9824a84b5fd5c8557208a787252e31a063436"
 
 PV = "${LINUX_VERSION}+git"
 
meta/recipes-kernel/linux/linux-yocto_6.16.bb +1 -1
index 2ea54a5301..a773d8a426 100644
@@ -29,7 +29,7 @@ SRCREV_machine:qemux86 ?= "01bcf423b031a36a070c7a983e45992e634fceb7"
 SRCREV_machine:qemux86-64 ?= "01bcf423b031a36a070c7a983e45992e634fceb7"
 SRCREV_machine:qemumips64 ?= "2459c29bf2c3d221fd6d3222c7200b368156986e"
 SRCREV_machine ?= "01bcf423b031a36a070c7a983e45992e634fceb7"
-SRCREV_meta ?= "5b4b90bbad3ada455c7c124bf704c519c6013aa1"
+SRCREV_meta ?= "6cd9824a84b5fd5c8557208a787252e31a063436"
 
 # set your preferred provider of linux-yocto to 'linux-yocto-upstream', and you'll
 # get the <version>/base branch, which is pure upstream -stable, and the same
Signature · 1 line
2.39.2
#1 lore raw
Quoted 7 lines · On Wed, 2025-09-10 at 15:39 -0400, [email protected] wrote:

Apply these on top of all my previous patches.

They fix the overly agressive DRM options I enabled and address some of the warnings in other configurations that had slipped through.

There may still be some issues lurking, but this will definitely improve things.

Thanks, this definitely looks better.

There are still config warnings for meta-agl-core and meta-arm:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/55/builds/2218
https://autobuilder.yoctoproject.org/valkyrie/#/builders/75/builds/2254
(copying people)

There is also a reproducibility issue in perf:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/2469
https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20250910-yq6y7z5s/packages/diff-html/

I did a bit of digging on that one and sent out a possible patch.

I've merged the current queue of 6.16 patches in since we'd be doing it eventually and I decided it would be easier to get people to collaborate on the remaining issues with the patches merged.

Cheers,

Richard

#2 lore raw
Quoted 9 lines · Richard Purdie
Quoted 7 lines · On Wed, 2025-09-10 at 15:39 -0400, [email protected] wrote:

Apply these on top of all my previous patches.

They fix the overly agressive DRM options I enabled and address some of the warnings in other configurations that had slipped through.

There may still be some issues lurking, but this will definitely improve things.

Quoted 7 lines

Thanks, this definitely looks better.

There are still config warnings for meta-agl-core and meta-arm:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/55/builds/2218
https://autobuilder.yoctoproject.org/valkyrie/#/builders/75/builds/2254
(copying people)

I scanned the AGL one yesterday and removed one of the obsolete options from the kernel-cache fragments. But the rest of the warnings come from other places, so I didn't get to tracking down where they are in the AGL layers. If no-one can do it in the short term, I can have a look.

The meta-arm one was CONFIG_SCHED_DEBUG, I removed it from
the kernel-cache fragments, but if it is still showing in your build, there must be another fragment that is adding it from somewhere in the layers. My same offer exists for meta-arm, I can track it down if no one else has time.

Quoted 5 lines

There is also a reproducibility issue in perf:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/2469

Quoted 9 lines

https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20250910-yq6y7z5s/packages/diff-html/

I did a bit of digging on that one and sent out a possible patch.

I've merged the current queue of 6.16 patches in since we'd be doing it eventually and I decided it would be easier to get people to collaborate on the remaining issues with the patches merged.

Agreed!

Bruce

Quoted 5 lines

Cheers,

Richard

Signature · 3 lines
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II
#3 lore raw
In reply to Richard Purdie
Quoted 9 lines · Richard Purdie
Quoted 7 lines · On Wed, 2025-09-10 at 15:39 -0400, [email protected] wrote:

Apply these on top of all my previous patches.

They fix the overly agressive DRM options I enabled and address some of the warnings in other configurations that had slipped through.

There may still be some issues lurking, but this will definitely improve things.

Quoted 6 lines

Thanks, this definitely looks better.

There are still config warnings for meta-agl-core and meta-arm:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/55/builds/2218
https://autobuilder.yoctoproject.org/valkyrie/#/builders/75/builds/2254
(copying people)

[snip]

I believe the meta-agl-core warnings should be addressed with the changes I just pushed.

Scott