Re: [yocto-patches] [meta-rockchip][PATCH] linux-yocto-dev: fix build

[Trevor Woerner <twoerner@gmail.com>]

On Tue 2024-06-11 @ 04:29:35 PM, Quentin Schulz via lists.yoctoproject.org wrote:
> Hi Trevor,
> 
> On 6/11/24 4:06 PM, Trevor Woerner via lists.yoctoproject.org wrote:
> > The linux-yocto-dev build was failing with:
> > 	| ERROR: modpost: vmlinux: local symbol 'security_path_rmdir' was exported
> > 
> > Disabling some filesystem-related security options fixes the build.
> > 
> 
> Is this the case for every board, including non-Rockchip ones?

This builds fine with qemuarm64, for example. Comparing the .config from the
qemuarm64 build vs the rockchip build is what led me to the patch that I've
presented. The qemuarm64 build doesn't try to build the file that causes the
error since its .config doesn't ask it to. We're using the in-kernel
defconfig for the rockchip build so:
1) it's strange nobody else has seen/fixed this
2) why doesn't the qemuarm64 build use the in-kernel defconfig (or if it does,
why are these options not set in its .config)?

> Is Bruce aware of those issues? Shouldn't this rather be fixed in oe-core
> instead?

I guess I could give him a poke.

> > Signed-off-by: Trevor Woerner <twoerner@gmail.com>
> > ---
> >   recipes-kernel/linux/linux-yocto-dev.bbappend                | 1 +
> >   .../linux/linux-yocto-dev/disable-some-fs-security.cfg       | 5 +++++
> >   2 files changed, 6 insertions(+)
> >   create mode 100644 recipes-kernel/linux/linux-yocto-dev/disable-some-fs-security.cfg
> > 
> > diff --git a/recipes-kernel/linux/linux-yocto-dev.bbappend b/recipes-kernel/linux/linux-yocto-dev.bbappend
> > index b6a63d7b7b29..94bf737c63bd 100644
> > --- a/recipes-kernel/linux/linux-yocto-dev.bbappend
> > +++ b/recipes-kernel/linux/linux-yocto-dev.bbappend
> > @@ -2,4 +2,5 @@ FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"
> >   COMPATIBLE_MACHINE:orangepi-5-plus = "orangepi-5-plus"
> > +SRC_URI:append = " file://disable-some-fs-security.cfg"
> 
> If it is Rockchip-specific, I would suggest using SRC_URI:append:rockchip
> here, to make sure we do not modify other machines from other layers
> whenever meta-rockchip is included?

Oh right, thanks. I don't think of that use-case often enough.