mbox

[00/10] kernel-yocto: consolidated pull request

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

Pull-request

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

Message

Bruce Ashfield Aug. 1, 2024, 3:08 p.m. UTC
From: Bruce Ashfield <bruce.ashfield@gmail.com>

Hi all,

Here's the next batch of kernel updates. Obviously the -stable
updates to 6.1 are routine, but the larger changes are the
introduction of the 6.10 kernel as a new / validated reference
version.

Some notes:

  - I've included the poky/poky-tiny preferred version bumps
    in this pull request for simplicity. Yes, I know they go
    to meta-yocto, but it is easier to make this available for
    AB testing when they are all together.

  - I'm watching the status of 6.10, if for some reason it
    EOLs before we release, we'll jump to 6.11, which I have
    under test and will push as linux-yocto-dev shortly.

  - There's one known build issue with 6.10, it is zfs in
    meta-oe. The upstream hasn't updated to support 6.10 yet,
    so I'm watching and waiting on that .. but there's no
    reason to hold this request for more testing on that.

  - I've tested 6.10 for all architectures on core-image-minimal,
    core-image-sato and core-image-kernel-dev. I've also
    tested against musl and poky-altconfig (6.1 with the
    6.10 headers)

There will surely be AB issues with this, but it is now
to the point where I need additional coverage and eyes
on the changes.

Bruce

The following changes since commit fd8dc3a2f320f5b8335202ba9f366ed93bf53dd5:

  gpgme: move gpgme-tool to own sub-package (2024-07-30 12:46:22 +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 (10):
  linux-yocto/6.6: update to v6.6.36
  linux-yocto/6.6: update to v6.6.38
  linux-yocto/6.6: update to v6.6.40
  linux-yocto/6.6: update to v6.6.43
  linux-yocto: introduce 6.10 reference kernel
  linux-libc-headers: update to v6.10
  kernel-devsrc: remove 64 bit vdso cmd files
  linux-yocto/6.10: update to v6.10
  linux-yocto/6.10: update to v6.10.2
  poky/poky-tiny: bump preferred version to 6.10

 meta-poky/conf/distro/poky-tiny.conf          |    2 +-
 meta-poky/conf/distro/poky.conf               |    4 +-
 meta/conf/distro/include/tcmode-default.inc   |    2 +-
 ...ders_6.9.bb => linux-libc-headers_6.10.bb} |    2 +-
 .../linux/cve-exclusion_6.10.inc              | 6660 +++++++++++++++++
 meta/recipes-kernel/linux/kernel-devsrc.bb    |    1 +
 .../linux/linux-yocto-rt_6.10.bb              |   48 +
 .../linux/linux-yocto-rt_6.6.bb               |    6 +-
 .../linux/linux-yocto-tiny_6.10.bb            |   33 +
 .../linux/linux-yocto-tiny_6.6.bb             |    6 +-
 meta/recipes-kernel/linux/linux-yocto_6.10.bb |   76 +
 meta/recipes-kernel/linux/linux-yocto_6.6.bb  |   28 +-
 12 files changed, 6843 insertions(+), 25 deletions(-)
 rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_6.9.bb => linux-libc-headers_6.10.bb} (80%)
 create mode 100644 meta/recipes-kernel/linux/cve-exclusion_6.10.inc
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_6.10.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_6.10.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto_6.10.bb

Comments

Richard Purdie Aug. 2, 2024, 9:02 a.m. UTC | #1
Hi Bruce,

On Thu, 2024-08-01 at 11:08 -0400, bruce.ashfield@gmail.com wrote:
> Here's the next batch of kernel updates. Obviously the -stable
> updates to 6.1 are routine, but the larger changes are the
> introduction of the 6.10 kernel as a new / validated reference
> version.
> 
> Some notes:
> 
>   - I've included the poky/poky-tiny preferred version bumps
>     in this pull request for simplicity. Yes, I know they go
>     to meta-yocto, but it is easier to make this available for
>     AB testing when they are all together.
> 
>   - I'm watching the status of 6.10, if for some reason it
>     EOLs before we release, we'll jump to 6.11, which I have
>     under test and will push as linux-yocto-dev shortly.
> 
>   - There's one known build issue with 6.10, it is zfs in
>     meta-oe. The upstream hasn't updated to support 6.10 yet,
>     so I'm watching and waiting on that .. but there's no
>     reason to hold this request for more testing on that.
> 
>   - I've tested 6.10 for all architectures on core-image-minimal,
>     core-image-sato and core-image-kernel-dev. I've also
>     tested against musl and poky-altconfig (6.1 with the
>     6.10 headers)
> 
> There will surely be AB issues with this, but it is now
> to the point where I need additional coverage and eyes
> on the changes.

Thanks for this, I put it through testing after tweaking it to remove a
rouge inherit. There were some issues:

a) genericarm64 version issue:
https://autobuilder.yoctoproject.org/typhoon/#/builders/166/builds/687

Warnings since genericarm64 isn't available as 6.10. Everything else
seemed to miss the preferred_version and build 6.6

b) crypto-dev failures:
https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/9329
https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/9340
https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/9313
https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/9161/steps/11/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/5141/steps/12/logs/stdio
(the latter taking out the reproducibility build so that wasn't tested)

c) meta-virt xen issues:
https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/3455

d) meta-agl kernel config fragment warnings:
https://autobuilder.yoctoproject.org/typhoon/#/builders/120/builds/4556

e) meta-arm kernel config fragment warnings:
https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/5810

f) qemumips64 parselogs issue:
https://autobuilder.yoctoproject.org/typhoon/#/builders/74/builds/9240/steps/14/logs/stdio
"failed when register_sysctl_sz sched_fair_sysctls to kernel"
"failed when register_sysctl_sz sched_core_sysctls to kernel"
"pci 0000:00:00.0: [Firmware Bug]: BAR 5: invalid; can't size"
(and other BARs)

g) qemumips parselogs issue:
https://autobuilder.yoctoproject.org/typhoon/#/builders/60/builds/9256/steps/15/logs/stdio
Similar to qemumips64

h) qemuarmv5 config fragment warning:
https://autobuilder.yoctoproject.org/typhoon/#/builders/160/builds/989

I've copied agl/arm people.

Probably nothing too surprising. I'll drop some of the patches whilst
we resolve these but see if we can keep the headers upgrade and the
point release bumps.

I'll try and test the crypto-dev upgrade on the list as that might help
that issue.

Cheers,

Richard
Bruce Ashfield Aug. 2, 2024, 11:18 a.m. UTC | #2
On Fri, Aug 2, 2024 at 5:02 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> Hi Bruce,
>
> On Thu, 2024-08-01 at 11:08 -0400, bruce.ashfield@gmail.com wrote:
> > Here's the next batch of kernel updates. Obviously the -stable
> > updates to 6.1 are routine, but the larger changes are the
> > introduction of the 6.10 kernel as a new / validated reference
> > version.
> >
> > Some notes:
> >
> >   - I've included the poky/poky-tiny preferred version bumps
> >     in this pull request for simplicity. Yes, I know they go
> >     to meta-yocto, but it is easier to make this available for
> >     AB testing when they are all together.
> >
> >   - I'm watching the status of 6.10, if for some reason it
> >     EOLs before we release, we'll jump to 6.11, which I have
> >     under test and will push as linux-yocto-dev shortly.
> >
> >   - There's one known build issue with 6.10, it is zfs in
> >     meta-oe. The upstream hasn't updated to support 6.10 yet,
> >     so I'm watching and waiting on that .. but there's no
> >     reason to hold this request for more testing on that.
> >
> >   - I've tested 6.10 for all architectures on core-image-minimal,
> >     core-image-sato and core-image-kernel-dev. I've also
> >     tested against musl and poky-altconfig (6.1 with the
> >     6.10 headers)
> >
> > There will surely be AB issues with this, but it is now
> > to the point where I need additional coverage and eyes
> > on the changes.
>
> Thanks for this, I put it through testing after tweaking it to remove a
> rouge inherit. There were some issues:
>
> a) genericarm64 version issue:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/166/builds/687
>
> Warnings since genericarm64 isn't available as 6.10. Everything else
> seemed to miss the preferred_version and build 6.6
>
> b) crypto-dev failures:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/9329
> https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/9340
> https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/9313
> https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/9161/steps/11/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/5141/steps/12/logs/stdio
> (the latter taking out the reproducibility build so that wasn't tested)
>
> c) meta-virt xen issues:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/3455
>
> d) meta-agl kernel config fragment warnings:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/120/builds/4556
>
> e) meta-arm kernel config fragment warnings:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/5810
>
> f) qemumips64 parselogs issue:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/74/builds/9240/steps/14/logs/stdio
> "failed when register_sysctl_sz sched_fair_sysctls to kernel"
> "failed when register_sysctl_sz sched_core_sysctls to kernel"
> "pci 0000:00:00.0: [Firmware Bug]: BAR 5: invalid; can't size"
> (and other BARs)
>
> g) qemumips parselogs issue:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/60/builds/9256/steps/15/logs/stdio
> Similar to qemumips64
>
> h) qemuarmv5 config fragment warning:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/160/builds/989
>
> I've copied agl/arm people.
>
> Probably nothing too surprising. I'll drop some of the patches whilst
> we resolve these but see if we can keep the headers upgrade and the
> point release bumps.

Sounds good, and yes, this is along the lines of what I expected. With
the AB in flux, I was staying away from using those resources before
sending.

I'll come back with a v2 early next week and will rebase to see what
you grabbed before sending.

It's a holiday weekend here, so I'd expect Wednesday next week
for a v2.

My -dev bump to 6.11 also based my smoke testing, so I'll have it
ready at the same time.

Bruce

>
> I'll try and test the crypto-dev upgrade on the list as that might help
> that issue.
>
> Cheers,
>
> Richard
>
>
Bruce Ashfield Aug. 6, 2024, 3:24 a.m. UTC | #3
In message: Re: [PATCH 00/10] kernel-yocto: consolidated pull request
on 02/08/2024 Richard Purdie wrote:

> Hi Bruce,
> 
> On Thu, 2024-08-01 at 11:08 -0400, bruce.ashfield@gmail.com wrote:
> > Here's the next batch of kernel updates. Obviously the -stable
> > updates to 6.1 are routine, but the larger changes are the
> > introduction of the 6.10 kernel as a new / validated reference
> > version.
> > 
> > Some notes:
> > 
> > � - I've included the poky/poky-tiny preferred version bumps
> > ��� in this pull request for simplicity. Yes, I know they go
> > ��� to meta-yocto, but it is easier to make this available for
> > ��� AB testing when they are all together.
> > 
> > � - I'm watching the status of 6.10, if for some reason it
> > ��� EOLs before we release, we'll jump to 6.11, which I have
> > ��� under test and will push as linux-yocto-dev shortly.
> > 
> > � - There's one known build issue with 6.10, it is zfs in
> > ��� meta-oe. The upstream hasn't updated to support 6.10 yet,
> > ��� so I'm watching and waiting on that .. but there's no
> > ��� reason to hold this request for more testing on that.
> > 
> > � - I've tested 6.10 for all architectures on core-image-minimal,
> > ��� core-image-sato and core-image-kernel-dev. I've also
> > ��� tested against musl and poky-altconfig (6.1 with the
> > ��� 6.10 headers)
> > 
> > There will surely be AB issues with this, but it is now
> > to the point where I need additional coverage and eyes
> > on the changes.
> 
> Thanks for this, I put it through testing after tweaking it to remove a
> rouge inherit. There were some issues:
> 
> a) genericarm64 version issue:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/166/builds/687
> 
> Warnings since genericarm64 isn't available as 6.10. Everything else
> seemed to miss the preferred_version and build 6.6

Unlike the other hardware references, genericarm64 doesn't set
a preferred version. It isn't something that I typically test,
since it is one of the hardware platform.

Until it is tested against 6.10, I could send an update to set
it explicity to 6.6.

Would that be acceptable to everyone ?

> 
> b) crypto-dev failures:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/9329
> https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/9340
> https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/9313
> https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/9161/steps/11/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/5141/steps/12/logs/stdio
> (the latter taking out the reproducibility build so that wasn't tested)

Hopefully your patch addressed it, let me know if I need to
look into it more.

> 
> c) meta-virt xen issues:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/3455

I pushed a new .inc to meta-virt

> 
> d) meta-agl kernel config fragment warnings:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/120/builds/4556
> 
> e) meta-arm kernel config fragment warnings:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/5810

d/e I'll leave for the layer owners.

> 
> f) qemumips64 parselogs issue:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/74/builds/9240/steps/14/logs/stdio
> "failed when register_sysctl_sz sched_fair_sysctls to kernel"
> "failed when register_sysctl_sz sched_core_sysctls to kernel"
> "pci 0000:00:00.0: [Firmware Bug]: BAR 5: invalid; can't size"
> (and other BARs)

One of the format's changed and the other is harmless, I have
a patch to update and add the other to what we ignore.

> 
> g) qemumips parselogs issue:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/60/builds/9256/steps/15/logs/stdio
> Similar to qemumips64

Same fix.

> 
> h) qemuarmv5 config fragment warning:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/160/builds/989

Fixed.

I'll send v2 later in the day on Tuesday.

Bruce

> 
> I've copied agl/arm people.
> 
> Probably nothing too surprising. I'll drop some of the patches whilst
> we resolve these but see if we can keep the headers upgrade and the
> point release bumps.
> 
> I'll try and test the crypto-dev upgrade on the list as that might help
> that issue.
> 
> Cheers,
> 
> Richard
> 
>
Jon Mason Aug. 6, 2024, 3:56 a.m. UTC | #4
Sorry for the top post, but doing this from my phone.

Genericarm64 pinned to the 6.6 kernel temporarily works for me.  I can take a look at it when I get back from vacation.


Get Outlook for Android<https://aka.ms/AAb9ysg>