Re: [OE-core] [PATCH 1/5] linux-yocto-dev: bump to v6.11

[Quentin Schulz <quentin.schulz@cherry.de>]

Hi Bruce,

On 9/24/24 4:11 PM, Bruce Ashfield wrote:
> On Tue, Sep 24, 2024 at 9:02 AM Quentin Schulz <quentin.schulz@cherry.de>
> wrote:
> 
>> Hi Bruce,
>>
>> On 8/11/24 8:04 PM, Bruce Ashfield via lists.openembedded.org wrote:
>>> From: Bruce Ashfield <bruce.ashfield@gmail.com>
>>>
>>> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
>>> ---
>>>    meta/recipes-kernel/linux/linux-yocto-dev.bb | 4 ++--
>>>    1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb
>> b/meta/recipes-kernel/linux/linux-yocto-dev.bb
>>> index 0097fec7b2..292897ce43 100644
>>> --- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
>>> +++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
>>> @@ -14,7 +14,7 @@ require recipes-kernel/linux/linux-yocto.inc
>>>    # provide this .inc to set specific revisions
>>>    include recipes-kernel/linux/linux-yocto-dev-revisions.inc
>>>
>>> -KBRANCH = "v6.10/standard/base"
>>> +KBRANCH = "v6.11/standard/base"
>>>    KMETA = "kernel-meta"
>>>
>>>    SRC_URI = "git://
>> git.yoctoproject.org/linux-yocto-dev.git;branch=${KBRANCH};name=machine;protocol=https
>> <http://git.yoctoproject.org/linux-yocto-dev.git;branch=$%7BKBRANCH%7D;name=machine;protocol=https>
>> \
>>> @@ -28,7 +28,7 @@ SRC_URI = "git://
>> git.yoctoproject.org/linux-yocto-dev.git;branch=${KBRANCH};name
>> <http://git.yoctoproject.org/linux-yocto-dev.git;branch=$%7BKBRANCH%7D;name>
>>>    SRCREV_machine ?=
>> '${@oe.utils.conditional("PREFERRED_PROVIDER_virtual/kernel",
>> "linux-yocto-dev", "${AUTOREV}",
>> "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'
>>>    SRCREV_meta ?=
>> '${@oe.utils.conditional("PREFERRED_PROVIDER_virtual/kernel",
>> "linux-yocto-dev", "${AUTOREV}",
>> "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'
>>>
>>> -LINUX_VERSION ?= "6.10"
>>> +LINUX_VERSION ?= "6.11"
>>>    LINUX_VERSION_EXTENSION ?= "-yoctodev-${LINUX_KERNEL_TYPE}"
>>>    PV = "${LINUX_VERSION}+git"
>>>
>>
>> I haven't tried to compile linux-yocto-dev but I have my own v6.11-rc6
>> based kernel recipe.
>>
>> It failed to build on Scarthgap because I was missing coreutils-native
>> (specifically truncate binary) because CONFIG_KALLSYMS was enabled. This
>> comes from
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1472464c6248575bf2d01c7f076b94704bb32c95
>>
>> It seems there are some config fragments in linux-yocto-cache
>> (ktypes/base/base.cfg) with it, so maybe we want to always add the
>> dependency (or is there a way to add a build time dependency from an
>> .scc file?).
>>
> 
> 
> Interesting!
> 
> I build linux-yocto-dev nightly, so I can confidently say that this isn't
> being seen with the reference recipe.
> 
> I also do have KALLSYMS in the default .config, so I've worked through the
> same new commit and enabling option.
> 
> I get truncate in my kernel builds via hosttools, so the dependency
> wasn't/isn't needed.
> 

truncate isn't in HOSTTOOLS in any release yet, just master.

c.f. 
https://git.openembedded.org/openembedded-core/commit/?id=522000ce5c4f0201cbe42d7826b6a8489ed10117

This means people won't be able to build 6.11 and later with 
CONFIG_KALLSYMS enabled in Scarthgap and earlier releases...

... unless we backport this patch to still supported releases?

BTW, I could reproduce on Scarthgap by checking out poky in its 
scarthgap branch, then running `git checkout origin/master -- 
meta/recipes-kernel/linux/linux-yocto-dev.bb`, then adding 
`PREFERRED_PROVIDER_virtual/kernel="linux-yocto-dev"` to conf/local.conf 
and then running `MACHINE=qemuarm64 bitbake linux-yocto-dev` from either 
a kas-container (4.3.2) or Debian Bullseye.

> If we do add the dependency, it is best done in the kernel recipes
> themselves, as they are versioned and we'll only pull it in when needed.
> Eventually, it migrates to a common dependency as all kernels gain the
> requirement over time.
> 
> That being said, I'd rather not add coreutils as a dependency until I know
> it is really required.
> 
> If you try building linux-yocto-dev on that same build machine, can you see
> if truncate is present in devshell ? I'm not seeing an obvious path through

Sadly, kas-container doesn't allow me to run -c devshell :/ (well it 
does, but then does nothing :) ).

truncate is available within the container though.

Cheers,
Quentin