| Message ID | cover.1755784780.git.bruce.ashfield@gmail.com |
|---|---|
| State | Not Applicable, archived |
| Headers | show |
On Thu Aug 21, 2025 at 4:03 PM CEST, Bruce Ashfield via lists.openembedded.org wrote: > From: Bruce Ashfield <bruce.ashfield@gmail.com> > > Richard, > > Here's the next set of updates to the linux-yocto kernel. > > The plan is to introduce 6.16 as the latest reference kernel, and keep > 6.12 around (since it is a LTS). > > This isn't ready to be the default for builds, but it has passed my > core-iamge-kernel-dev testing, so I wanted to make the recipes available > as visibility to where we are headed for the release (plus, I'm out of > the office on holidays until the first week of September, so making it > the default would be a bad idea from me being able to support issues). > Hi Bruce, Thanks for the series. I understand this isn't fully ready, but I did launch a full build anyway: most builders succeed, we just have one warning on config fragments: WARNING: linux-yocto-6.16.2+git-r0 do_kernel_configcheck: [kernel config]: specified values did not make it into the kernel's final configuration: ... [INFO]: config 'CONFIG_CRYPTO_LIB_CHACHA' was set, but it wasn't assignable, check (parent) dependencies ... [INFO]: config 'CONFIG_CRYPTO_CHACHA20_NEON' was set, but it wasn't assignable, check (parent) dependencies ... [INFO]: the following symbols were not found in the active configuration: - CONFIG_CRYPTO_SHA2_ARM_CE - CONFIG_CRYPTO_CRC32_ARM_CE https://autobuilder.yoctoproject.org/valkyrie/#/builders/40/builds/2248 Best regards, Mathieu
On Fri, Aug 22, 2025 at 12:52 PM Mathieu Dubois-Briand < mathieu.dubois-briand@bootlin.com> wrote: > On Thu Aug 21, 2025 at 4:03 PM CEST, Bruce Ashfield via > lists.openembedded.org wrote: > > From: Bruce Ashfield <bruce.ashfield@gmail.com> > > > > Richard, > > > > Here's the next set of updates to the linux-yocto kernel. > > > > The plan is to introduce 6.16 as the latest reference kernel, and keep > > 6.12 around (since it is a LTS). > > > > This isn't ready to be the default for builds, but it has passed my > > core-iamge-kernel-dev testing, so I wanted to make the recipes available > > as visibility to where we are headed for the release (plus, I'm out of > > the office on holidays until the first week of September, so making it > > the default would be a bad idea from me being able to support issues). > > > > Hi Bruce, > > Thanks for the series. > > I understand this isn't fully ready, but I did launch a full build > anyway: most builders succeed, we just have one warning on config > fragments: > > WARNING: linux-yocto-6.16.2+git-r0 do_kernel_configcheck: [kernel config]: > specified values did not make it into the kernel's final configuration: > ... > [INFO]: config 'CONFIG_CRYPTO_LIB_CHACHA' was set, but it wasn't > assignable, check (parent) dependencies > ... > [INFO]: config 'CONFIG_CRYPTO_CHACHA20_NEON' was set, but it wasn't > assignable, check (parent) dependencies > ... > [INFO]: the following symbols were not found in the active configuration: > - CONFIG_CRYPTO_SHA2_ARM_CE > - CONFIG_CRYPTO_CRC32_ARM_CE > > https://autobuilder.yoctoproject.org/valkyrie/#/builders/40/builds/2248 I always find it odd that I can't click on any of the AB tabs (in the link you sent) and see what the MACHINE value is for that build. I looked at the writeconfig step of the build and it looks to be qemuarm. Which is odd, since I'm not seeing the same warning for that here. When I'm back from holidays next week, I'll have a closer look. Bruce > > > Best regards, > Mathieu > > -- > Mathieu Dubois-Briand, Bootlin > Embedded Linux and Kernel engineering > https://bootlin.com > >
On Tue Aug 26, 2025 at 4:03 AM CEST, Bruce Ashfield wrote: > On Fri, Aug 22, 2025 at 12:52 PM Mathieu Dubois-Briand < > mathieu.dubois-briand@bootlin.com> wrote: > >> On Thu Aug 21, 2025 at 4:03 PM CEST, Bruce Ashfield via >> lists.openembedded.org wrote: >> > From: Bruce Ashfield <bruce.ashfield@gmail.com> >> > >> > Richard, >> > >> > Here's the next set of updates to the linux-yocto kernel. >> > >> > The plan is to introduce 6.16 as the latest reference kernel, and keep >> > 6.12 around (since it is a LTS). >> > >> > This isn't ready to be the default for builds, but it has passed my >> > core-iamge-kernel-dev testing, so I wanted to make the recipes available >> > as visibility to where we are headed for the release (plus, I'm out of >> > the office on holidays until the first week of September, so making it >> > the default would be a bad idea from me being able to support issues). >> > >> >> Hi Bruce, >> >> Thanks for the series. >> >> I understand this isn't fully ready, but I did launch a full build >> anyway: most builders succeed, we just have one warning on config >> fragments: >> >> WARNING: linux-yocto-6.16.2+git-r0 do_kernel_configcheck: [kernel config]: >> specified values did not make it into the kernel's final configuration: >> ... >> [INFO]: config 'CONFIG_CRYPTO_LIB_CHACHA' was set, but it wasn't >> assignable, check (parent) dependencies >> ... >> [INFO]: config 'CONFIG_CRYPTO_CHACHA20_NEON' was set, but it wasn't >> assignable, check (parent) dependencies >> ... >> [INFO]: the following symbols were not found in the active configuration: >> - CONFIG_CRYPTO_SHA2_ARM_CE >> - CONFIG_CRYPTO_CRC32_ARM_CE >> >> https://autobuilder.yoctoproject.org/valkyrie/#/builders/40/builds/2248 > > > I always find it odd that I can't click on any of the AB tabs (in the link > you sent) and see what the MACHINE value is for that build. > Hum, that's raising an interesting point, I had the same issue at the very beginning. I'm now familiar with each steps and know where I have to look at, but maybe we can do something better about it. I will add this idea somewhere on my TODO list. > I looked at the writeconfig step of the build and it looks to be qemuarm. > Which is odd, since I'm not seeing the same warning for that here. > Yes, I confirm, we have MACHINE = "qemuarm". Best regards, Mathieu
On Mon, 2025-08-25 at 23:03 -0300, Bruce Ashfield wrote: > > > On Fri, Aug 22, 2025 at 12:52 PM Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> wrote: > > On Thu Aug 21, 2025 at 4:03 PM CEST, Bruce Ashfield via lists.openembedded.org wrote: > > > From: Bruce Ashfield <bruce.ashfield@gmail.com> > > > > > > Richard, > > > > > > Here's the next set of updates to the linux-yocto kernel. > > > > > > The plan is to introduce 6.16 as the latest reference kernel, and keep > > > 6.12 around (since it is a LTS). > > > > > > This isn't ready to be the default for builds, but it has passed my > > > core-iamge-kernel-dev testing, so I wanted to make the recipes available > > > as visibility to where we are headed for the release (plus, I'm out of > > > the office on holidays until the first week of September, so making it > > > the default would be a bad idea from me being able to support issues). > > > > > > > Hi Bruce, > > > > Thanks for the series. > > > > I understand this isn't fully ready, but I did launch a full build > > anyway: most builders succeed, we just have one warning on config > > fragments: > > > > WARNING: linux-yocto-6.16.2+git-r0 do_kernel_configcheck: [kernel config]: specified values did not make it into the kernel's final configuration: > > ... > > [INFO]: config 'CONFIG_CRYPTO_LIB_CHACHA' was set, but it wasn't assignable, check (parent) dependencies > > ... > > [INFO]: config 'CONFIG_CRYPTO_CHACHA20_NEON' was set, but it wasn't assignable, check (parent) dependencies > > ... > > [INFO]: the following symbols were not found in the active configuration: > > - CONFIG_CRYPTO_SHA2_ARM_CE > > - CONFIG_CRYPTO_CRC32_ARM_CE > > > > https://autobuilder.yoctoproject.org/valkyrie/#/builders/40/builds/2248 > > > > I always find it odd that I can't click on any of the AB tabs (in the link you sent) and see what the MACHINE value is for that build. > > I looked at the writeconfig step of the build and it looks to be qemuarm. Which is odd, since I'm not seeing the same warning for that here. > > When I'm back from holidays next week, I'll have a closer look. FWIW if you look for the "Write config" step (step 10 in the above link) and expand that, it says MACHINE = "qemuarm". It is only hitting that build as it is a nodistro build and hence has a floating kernel version. I somehow got the patches the wrong way around and merged the ones with the warning but we'll manage with that for now until you're back. Cheers, Richard
On Tue, Aug 26, 2025 at 4:15 AM Richard Purdie < richard.purdie@linuxfoundation.org> wrote: > On Mon, 2025-08-25 at 23:03 -0300, Bruce Ashfield wrote: > > > > > > On Fri, Aug 22, 2025 at 12:52 PM Mathieu Dubois-Briand < > mathieu.dubois-briand@bootlin.com> wrote: > > > On Thu Aug 21, 2025 at 4:03 PM CEST, Bruce Ashfield via > lists.openembedded.org wrote: > > > > From: Bruce Ashfield <bruce.ashfield@gmail.com> > > > > > > > > Richard, > > > > > > > > Here's the next set of updates to the linux-yocto kernel. > > > > > > > > The plan is to introduce 6.16 as the latest reference kernel, and > keep > > > > 6.12 around (since it is a LTS). > > > > > > > > This isn't ready to be the default for builds, but it has passed my > > > > core-iamge-kernel-dev testing, so I wanted to make the recipes > available > > > > as visibility to where we are headed for the release (plus, I'm out > of > > > > the office on holidays until the first week of September, so making > it > > > > the default would be a bad idea from me being able to support > issues). > > > > > > > > > > Hi Bruce, > > > > > > Thanks for the series. > > > > > > I understand this isn't fully ready, but I did launch a full build > > > anyway: most builders succeed, we just have one warning on config > > > fragments: > > > > > > WARNING: linux-yocto-6.16.2+git-r0 do_kernel_configcheck: [kernel > config]: specified values did not make it into the kernel's final > configuration: > > > ... > > > [INFO]: config 'CONFIG_CRYPTO_LIB_CHACHA' was set, but it wasn't > assignable, check (parent) dependencies > > > ... > > > [INFO]: config 'CONFIG_CRYPTO_CHACHA20_NEON' was set, but it wasn't > assignable, check (parent) dependencies > > > ... > > > [INFO]: the following symbols were not found in the active > configuration: > > > - CONFIG_CRYPTO_SHA2_ARM_CE > > > - CONFIG_CRYPTO_CRC32_ARM_CE > > > > > > > https://autobuilder.yoctoproject.org/valkyrie/#/builders/40/builds/2248 > > > > > > > I always find it odd that I can't click on any of the AB tabs (in the > link you sent) and see what the MACHINE value is for that build. > > > > I looked at the writeconfig step of the build and it looks to be > qemuarm. Which is odd, since I'm not seeing the same warning for that here. > > > > When I'm back from holidays next week, I'll have a closer look. > > FWIW if you look for the "Write config" step (step 10 in the above > link) and expand that, it says MACHINE = "qemuarm". > > It is only hitting that build as it is a nodistro build and hence has a > floating kernel version. > Hmm. I'm of course forcing 6.16 and the latest revs in all my builds, I'd think that in theory I should be able see the same thing even with the poky distro. I can inspect the configs and see the options in question, so I'm going to go about recreating it that way versus trying to do a different clone and distro configuration. As you guessed, I have very limited time at a keyboard this week, so it will take a bit for me to follow up. Bruce > > I somehow got the patches the wrong way around and merged the ones with > the warning but we'll manage with that for now until you're back. > > Cheers, > > Richard > > >
From: Bruce Ashfield <bruce.ashfield@gmail.com> Richard, Here's the next set of updates to the linux-yocto kernel. The plan is to introduce 6.16 as the latest reference kernel, and keep 6.12 around (since it is a LTS). This isn't ready to be the default for builds, but it has passed my core-iamge-kernel-dev testing, so I wanted to make the recipes available as visibility to where we are headed for the release (plus, I'm out of the office on holidays until the first week of September, so making it the default would be a bad idea from me being able to support issues). We also have a -stable update to 6.12. Bruce The following changes since commit 5424fc6186877e1949a818307f43578b81c493ae: lttng-tools: Disable slow tests to fix ptest runs (2025-08-19 11:48:50 +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 (4): linux-yocto: introduce 6.16 reference kernels linux-yocto/6.16: update CVE exclusions (6.16.2) linux-yocto/6.12: update to v6.12.42 linux-yocto/6.12: update CVE exclusions (6.12.42) .../linux/cve-exclusion_6.12.inc | 264 +- .../linux/cve-exclusion_6.16.inc | 14804 ++++++++++++++++ .../linux/linux-yocto-rt_6.12.bb | 6 +- .../linux/linux-yocto-rt_6.16.bb | 48 + .../linux/linux-yocto-tiny_6.12.bb | 6 +- .../linux/linux-yocto-tiny_6.16.bb | 33 + meta/recipes-kernel/linux/linux-yocto_6.12.bb | 28 +- meta/recipes-kernel/linux/linux-yocto_6.16.bb | 79 + 8 files changed, 15238 insertions(+), 30 deletions(-) create mode 100644 meta/recipes-kernel/linux/cve-exclusion_6.16.inc create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb create mode 100644 meta/recipes-kernel/linux/linux-yocto_6.16.bb