On Tue, 2026-07-21 at 23:51 -0400, [email protected] wrote:
> From: Bruce Ashfield <[email protected]>
> 
> linux-yocto-dev did not set KCONF_BSP_AUDIT_LEVEL, so it inherited the
> kernel-yocto.bbclass default of 0. That silently suppresses the 'invalid
> fragment elements' and 'redefinition' audit categories: do_kernel_configcheck
> still runs and still writes .kernel-meta/cfg/{invalid,redefinition}.txt, but
> nothing is ever reported to the user.
> 
> This was hiding real breakage. Five config options removed upstream in v7.1
> (CONFIG_HAMRADIO, CONFIG_CRYPTO_MICHAEL_MIC, CONFIG_ISDN, CONFIG_ISDN_CAPI,
> CONFIG_NF_CT_PROTO_UDPLITE) sat stale in the kernel-cache fragments for a
> full release cycle without a single warning.
> 
> The versioned recipes already set this (linux-yocto and linux-yocto-rt use
> 1, linux-yocto-tiny uses 2); the dev recipe being the sole exception is
> backwards, since the dev kernel tracks a moving upstream and is precisely
> where dropped symbols should surface first.
> 
> Set it to 1 to match linux-yocto.
> 
> Signed-off-by: Bruce Ashfield <[email protected]>
> ---
>  meta/recipes-kernel/linux/linux-yocto-dev.bb | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb 
> b/meta/recipes-kernel/linux/linux-yocto-dev.bb
> index f82f3c326b..ef6e1e0759 100644
> --- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
> @@ -16,6 +16,7 @@ include recipes-kernel/linux/linux-yocto-dev-revisions.inc
>  
>  KBRANCH = "v7.2/standard/base"
>  KMETA = "kernel-meta"
> +KCONF_BSP_AUDIT_LEVEL = "1"


Should we change the default now this is well established?

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#241601): 
https://lists.openembedded.org/g/openembedded-core/message/241601
Mute This Topic: https://lists.openembedded.org/mt/120389226/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to