Hi, it looks like this change is causing mkfs.ext4 to segfault on some builders.
I'm seeing it on ubuntu-18.04 (I know it's unsupported now). It might be related to older docker or libseccomp2 there, because there is similar issue with gdk-pixbuf-native which fails when buildtools-extended is used together with this and might be related to https://github.com/moby/moby/issues/43595 because when I try very similar 18.04 ubuntu image on my gentoo host I cannot reproduce neither the gdk-pixbuf-native failure nor the mkfs.ext4 segfaults. I'm trying to get access to some of the affected boxes to find out which version docker/libseccomp2 is used there and to double check that this is root cause for these failures (now I can only confirm that it started in Nanbield when this uninative upgrade was merged and now I've reproduced the same with kirkstone-nut with the same uninative upgrade. It might be useful to delay backporting this for a bit longer (and I'll soon confirm if 3.10 was already affected or not). Regards, On Fri, Jun 2, 2023 at 4:22 AM Steve Sakoman <st...@sakoman.com> wrote: > From: Michael Halstead <mhalst...@linuxfoundation.org> > > Signed-off-by: Michael Halstead <mhalst...@linuxfoundation.org> > Signed-off-by: Richard Purdie <richard.pur...@linuxfoundation.org> > (cherry picked from commit f87becb69e02bdf055dffb633ed4f6d36b36f7a7) > Signed-off-by: Steve Sakoman <st...@sakoman.com> > --- > meta/conf/distro/include/yocto-uninative.inc | 8 ++++---- > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/meta/conf/distro/include/yocto-uninative.inc > b/meta/conf/distro/include/yocto-uninative.inc > index f3c05b7e20..ad4816a1f3 100644 > --- a/meta/conf/distro/include/yocto-uninative.inc > +++ b/meta/conf/distro/include/yocto-uninative.inc > @@ -7,9 +7,9 @@ > # > > UNINATIVE_MAXGLIBCVERSION = "2.37" > -UNINATIVE_VERSION = "3.10" > +UNINATIVE_VERSION = "4.0" > > UNINATIVE_URL ?= " > http://downloads.yoctoproject.org/releases/uninative/${UNINATIVE_VERSION}/ > " > -UNINATIVE_CHECKSUM[aarch64] ?= > "b11f7dff0ff5e3c971f22e89a105efb0f8d2006fd71d1ea3e5da771e416b0e01" > -UNINATIVE_CHECKSUM[i686] ?= > "ad7daa7fca7693ca07eea5279f830333530171d357759b380954a25254edd8dd" > -UNINATIVE_CHECKSUM[x86_64] ?= > "ce8ff7e3247da312fbf84008f415bc1b4d113ac9fe4ec91581e4a20cd8b475d3" > +UNINATIVE_CHECKSUM[aarch64] ?= > "7baa8418a302df52e00916193b0a04f318356d9d2670c9a2bce3e966efefd738" > +UNINATIVE_CHECKSUM[i686] ?= > "83114d36883d43a521e280742b9849bf85d039b2f83d8e21d480659babe75ee8" > +UNINATIVE_CHECKSUM[x86_64] ?= > "fd75b2a1a67a10f6b7d65afb7d0f3e71a63b0038e428f34dfe420bb37716558a" > -- > 2.34.1 > > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#182365): https://lists.openembedded.org/g/openembedded-core/message/182365 Mute This Topic: https://lists.openembedded.org/mt/99279066/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
