mbox

[0/6] kernel-yocto: consolidated pull request

Message ID cover.1746548780.git.bruce.ashfield@gmail.com
State Not Applicable, archived
Headers show

Pull-request

https://git.yoctoproject.org/poky-contrib zedd/kernel

Message

Bruce Ashfield May 6, 2025, 4:32 p.m. UTC
From: Bruce Ashfield <bruce.ashfield@gmail.com>

Hi Richard,

Now that I'm back at my desk, here are the queued -stable, configuration
and feature changes that I have queued.

I'll be sending -stable updates to the LTS branches as well.

Note: once patch #1 is in the tree and doesn't need any more tweaks, I'll
send a documenation update. This is the patch that we need to enable the
modular initrd work in kernel-yocto references.

Cheers,

Bruce

The following changes since commit 601b05a298c0847e96b8f5f71e50d057e2833382:

  mesa: Fix header search paths (2025-05-05 18:02:48 +0100)

are available in the Git repository at:

  https://git.yoctoproject.org/poky-contrib zedd/kernel
  https://git.yoctoproject.org/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (6):
  kernel-yocto: allow annotated options to be modified
  linux-yocto-dev: update to v6.15
  linux-yocto/6.12: update to v6.12.24
  linux-yocto/6.12: update to v6.12.25
  linux-yocto/6.12: bsp/genericarm64: modular configuration updates
  linux-yocto/6.12: update to v6.12.27

 meta/classes-recipe/kernel-yocto.bbclass      |  7 ++++-
 .../kern-tools/kern-tools-native_git.bb       |  2 +-
 meta/recipes-kernel/linux/linux-yocto-dev.bb  |  4 +--
 .../linux/linux-yocto-rt_6.12.bb              |  6 ++--
 .../linux/linux-yocto-tiny_6.12.bb            |  6 ++--
 meta/recipes-kernel/linux/linux-yocto_6.12.bb | 28 +++++++++----------
 6 files changed, 29 insertions(+), 24 deletions(-)

Comments

Mathieu Dubois-Briand May 7, 2025, 7:42 a.m. UTC | #1
On Tue May 6, 2025 at 6:32 PM CEST, Bruce Ashfield via lists.openembedded.org wrote:
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
>
> Hi Richard,
>
> Now that I'm back at my desk, here are the queued -stable, configuration
> and feature changes that I have queued.
>
> I'll be sending -stable updates to the LTS branches as well.
>
> Note: once patch #1 is in the tree and doesn't need any more tweaks, I'll
> send a documenation update. This is the patch that we need to enable the
> modular initrd work in kernel-yocto references.
>
> Cheers,
>
> Bruce
>

Hi Bruce,

I took this series in my branch and everything seems to be fine so far,
except for a warning:

WARNING: linux-yocto-tiny-6.12.27+git-r0 do_kernel_configcheck: [kernel config]: specified values did not make it into the kernel's final configuration:

    [NOTE]: 'CONFIG_CRYPTO_CHACHA20_NEON' last val (y) and .config val (n) do not match
    [INFO]: CONFIG_CRYPTO_CHACHA20_NEON : n

https://autobuilder.yoctoproject.org/valkyrie/#/builders/50/builds/1565
Richard Purdie May 7, 2025, 7:58 a.m. UTC | #2
On Wed, 2025-05-07 at 09:42 +0200, Mathieu Dubois-Briand wrote:
> On Tue May 6, 2025 at 6:32 PM CEST, Bruce Ashfield via lists.openembedded.org wrote:
> > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> > 
> > Hi Richard,
> > 
> > Now that I'm back at my desk, here are the queued -stable, configuration
> > and feature changes that I have queued.
> > 
> > I'll be sending -stable updates to the LTS branches as well.
> > 
> > Note: once patch #1 is in the tree and doesn't need any more tweaks, I'll
> > send a documenation update. This is the patch that we need to enable the
> > modular initrd work in kernel-yocto references.
> 
> I took this series in my branch and everything seems to be fine so far,
> except for a warning:
> 
> WARNING: linux-yocto-tiny-6.12.27+git-r0 do_kernel_configcheck: [kernel config]: specified values did not make it into the kernel's final configuration:
> 
>     [NOTE]: 'CONFIG_CRYPTO_CHACHA20_NEON' last val (y) and .config val (n) do not match
>     [INFO]: CONFIG_CRYPTO_CHACHA20_NEON : n
> 
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/50/builds/1565

There are a few, it likely depends which build built a component first.
I think there are three groups of failures, I've listed them all for
completeness:

Another qemuarm poky-tiny:
https://autobuilder.yoctoproject.org/valkyrie/?#/builders/50/builds/1564
qemuarm:
https://autobuilder.yoctoproject.org/valkyrie/?#/builders/16/builds/1563
qemuarm-alt:
https://autobuilder.yoctoproject.org/valkyrie/?#/builders/74/builds/1532
qemuarm nodistro:
https://autobuilder.yoctoproject.org/valkyrie/?#/builders/40/builds/1531


lttng-tools ptest failure:
https://autobuilder.yoctoproject.org/valkyrie/?#/builders/61/builds/1445


genericarm64:
https://autobuilder.yoctoproject.org/valkyrie/?#/builders/60/builds/1549
genericarm64-alt:
https://autobuilder.yoctoproject.org/valkyrie/?#/builders/22/builds/1552

Cheers,

Richard
Richard Purdie May 7, 2025, 11:18 a.m. UTC | #3
On Wed, 2025-05-07 at 08:58 +0100, Richard Purdie via
lists.openembedded.org wrote:
> On Wed, 2025-05-07 at 09:42 +0200, Mathieu Dubois-Briand wrote:
> > On Tue May 6, 2025 at 6:32 PM CEST, Bruce Ashfield via
> > lists.openembedded.org wrote:
> > > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> > > 
> > > Hi Richard,
> > > 
> > > Now that I'm back at my desk, here are the queued -stable,
> > > configuration
> > > and feature changes that I have queued.
> > > 
> > > I'll be sending -stable updates to the LTS branches as well.
> > > 
> > > Note: once patch #1 is in the tree and doesn't need any more
> > > tweaks, I'll
> > > send a documenation update. This is the patch that we need to
> > > enable the
> > > modular initrd work in kernel-yocto references.
> > 
> > I took this series in my branch and everything seems to be fine so
> > far,
> > except for a warning:
> > 
> > WARNING: linux-yocto-tiny-6.12.27+git-r0 do_kernel_configcheck:
> > [kernel config]: specified values did not make it into the kernel's
> > final configuration:
> > 
> >     [NOTE]: 'CONFIG_CRYPTO_CHACHA20_NEON' last val (y) and .config
> > val (n) do not match
> >     [INFO]: CONFIG_CRYPTO_CHACHA20_NEON : n
> > 
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/50/builds/1565
> 
> There are a few, it likely depends which build built a component
> first.
> I think there are three groups of failures, I've listed them all for
> completeness:
> 
> Another qemuarm poky-tiny:
> https://autobuilder.yoctoproject.org/valkyrie/?#/builders/50/builds/1564
> qemuarm:
> https://autobuilder.yoctoproject.org/valkyrie/?#/builders/16/builds/1563
> qemuarm-alt:
> https://autobuilder.yoctoproject.org/valkyrie/?#/builders/74/builds/1532
> qemuarm nodistro:
> https://autobuilder.yoctoproject.org/valkyrie/?#/builders/40/builds/1531
> 
> 
> lttng-tools ptest failure:
> https://autobuilder.yoctoproject.org/valkyrie/?#/builders/61/builds/1445

The ptest failure didn't appear on a second run so it is an
intermittent AB issue rather than anything specific to this patch
series.

Cheers,

Richard
Mikko Rapeli May 7, 2025, 11:39 a.m. UTC | #4
Hi,

On Wed, May 07, 2025 at 12:18:03PM +0100, Richard Purdie via lists.openembedded.org wrote:
> On Wed, 2025-05-07 at 08:58 +0100, Richard Purdie via
> lists.openembedded.org wrote:
> > On Wed, 2025-05-07 at 09:42 +0200, Mathieu Dubois-Briand wrote:
> > > On Tue May 6, 2025 at 6:32 PM CEST, Bruce Ashfield via
> > > lists.openembedded.org wrote:
> > > > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> > > > 
> > > > Hi Richard,
> > > > 
> > > > Now that I'm back at my desk, here are the queued -stable,
> > > > configuration
> > > > and feature changes that I have queued.
> > > > 
> > > > I'll be sending -stable updates to the LTS branches as well.
> > > > 
> > > > Note: once patch #1 is in the tree and doesn't need any more
> > > > tweaks, I'll
> > > > send a documenation update. This is the patch that we need to
> > > > enable the
> > > > modular initrd work in kernel-yocto references.
> > > 
> > > I took this series in my branch and everything seems to be fine so
> > > far,
> > > except for a warning:
> > > 
> > > WARNING: linux-yocto-tiny-6.12.27+git-r0 do_kernel_configcheck:
> > > [kernel config]: specified values did not make it into the kernel's
> > > final configuration:
> > > 
> > > ��� [NOTE]: 'CONFIG_CRYPTO_CHACHA20_NEON' last val (y) and .config
> > > val (n) do not match
> > > ��� [INFO]: CONFIG_CRYPTO_CHACHA20_NEON : n
> > > 
> > > https://autobuilder.yoctoproject.org/valkyrie/#/builders/50/builds/1565
> > 
> > There are a few, it likely depends which build built a component
> > first.
> > I think there are three groups of failures, I've listed them all for
> > completeness:
> > 
> > Another qemuarm poky-tiny:
> > https://autobuilder.yoctoproject.org/valkyrie/?#/builders/50/builds/1564
> > qemuarm:
> > https://autobuilder.yoctoproject.org/valkyrie/?#/builders/16/builds/1563
> > qemuarm-alt:
> > https://autobuilder.yoctoproject.org/valkyrie/?#/builders/74/builds/1532
> > qemuarm nodistro:
> > https://autobuilder.yoctoproject.org/valkyrie/?#/builders/40/builds/1531
> > 
> > 
> > lttng-tools ptest failure:
> > https://autobuilder.yoctoproject.org/valkyrie/?#/builders/61/builds/1445
> 
> The ptest failure didn't appear on a second run so it is an
> intermittent AB issue rather than anything specific to this patch
> series.

So it looks like missing CRYPTO_LIB_CHACHA_INTERNAL=m with
CRYPTO_CHACHA20_NEON=m is the only problem on qemuarm
and genericarm64

I can send a patch if Bruce doesn't already have this.
I wonder where this came from since I did not see this before.
Maybe in the point release updates?

Cheers,

-Mikko
Bruce Ashfield May 7, 2025, 1:03 p.m. UTC | #5
On Wed, May 7, 2025 at 7:39 AM Mikko Rapeli <mikko.rapeli@linaro.org> wrote:

> Hi,
>
> On Wed, May 07, 2025 at 12:18:03PM +0100, Richard Purdie via
> lists.openembedded.org wrote:
> > On Wed, 2025-05-07 at 08:58 +0100, Richard Purdie via
> > lists.openembedded.org wrote:
> > > On Wed, 2025-05-07 at 09:42 +0200, Mathieu Dubois-Briand wrote:
> > > > On Tue May 6, 2025 at 6:32 PM CEST, Bruce Ashfield via
> > > > lists.openembedded.org wrote:
> > > > > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> > > > >
> > > > > Hi Richard,
> > > > >
> > > > > Now that I'm back at my desk, here are the queued -stable,
> > > > > configuration
> > > > > and feature changes that I have queued.
> > > > >
> > > > > I'll be sending -stable updates to the LTS branches as well.
> > > > >
> > > > > Note: once patch #1 is in the tree and doesn't need any more
> > > > > tweaks, I'll
> > > > > send a documenation update. This is the patch that we need to
> > > > > enable the
> > > > > modular initrd work in kernel-yocto references.
> > > >
> > > > I took this series in my branch and everything seems to be fine so
> > > > far,
> > > > except for a warning:
> > > >
> > > > WARNING: linux-yocto-tiny-6.12.27+git-r0 do_kernel_configcheck:
> > > > [kernel config]: specified values did not make it into the kernel's
> > > > final configuration:
> > > >
> > > >     [NOTE]: 'CONFIG_CRYPTO_CHACHA20_NEON' last val (y) and .config
> > > > val (n) do not match
> > > >     [INFO]: CONFIG_CRYPTO_CHACHA20_NEON : n
> > > >
> > > >
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/50/builds/1565
> > >
> > > There are a few, it likely depends which build built a component
> > > first.
> > > I think there are three groups of failures, I've listed them all for
> > > completeness:
> > >
> > > Another qemuarm poky-tiny:
> > >
> https://autobuilder.yoctoproject.org/valkyrie/?#/builders/50/builds/1564
> > > qemuarm:
> > >
> https://autobuilder.yoctoproject.org/valkyrie/?#/builders/16/builds/1563
> > > qemuarm-alt:
> > >
> https://autobuilder.yoctoproject.org/valkyrie/?#/builders/74/builds/1532
> > > qemuarm nodistro:
> > >
> https://autobuilder.yoctoproject.org/valkyrie/?#/builders/40/builds/1531
> > >
> > >
> > > lttng-tools ptest failure:
> > >
> https://autobuilder.yoctoproject.org/valkyrie/?#/builders/61/builds/1445
> >
> > The ptest failure didn't appear on a second run so it is an
> > intermittent AB issue rather than anything specific to this patch
> > series.
>
> So it looks like missing CRYPTO_LIB_CHACHA_INTERNAL=m with
> CRYPTO_CHACHA20_NEON=m is the only problem on qemuarm
> and genericarm64
>
> I can send a patch if Bruce doesn't already have this.
> I wonder where this came from since I did not see this before.
> Maybe in the point release updates?
>

I see your patch. Thanks!

I'll do a bit of root cause analysis when applying it shortly. I obviously
didn't
see it either in my local builds.

Bruce



>
> Cheers,
>
> -Mikko
>
Fabio Estevam May 15, 2025, 4:06 p.m. UTC | #6
Hi Mikko,

On Wed, May 7, 2025 at 8:39 AM Mikko Rapeli via lists.openembedded.org
<mikko.rapeli=linaro.org@lists.openembedded.org> wrote:

> So it looks like missing CRYPTO_LIB_CHACHA_INTERNAL=m with
> CRYPTO_CHACHA20_NEON=m is the only problem on qemuarm
> and genericarm64
>
> I can send a patch if Bruce doesn't already have this.
> I wonder where this came from since I did not see this before.
> Maybe in the point release updates?

This is caused by commit 67727c5764a8 ("crypto: lib/Kconfig - Hide
arch options from user"), which landed in 6.12.26.

I have submitted a fix for it:

https://lore.kernel.org/linux-arm-kernel/20250515154136.435685-1-festevam@gmail.com/