Re: [OE-core] [PATCH v2 0/3] tunes: the great migration

[Jon Mason]

On Tue, Aug 17, 2021 at 4:44 PM Alexandre Belloni
 wrote:
>
> Hello Jon,
>
> I did run that through the autobuilders:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2457
>
> This is mostly good, the meta-arm failure is about a kernel patch not
> applying, I don't think it is related, you'd have to rebase
> meta-arm-bsp/recipes-kernel/linux/linux-yocto-5.10/n1sdp/0005-r8169-Fix-to-avoid-duplicate-sysfs-entry-creation-er.patch

Yes, this is fallout from the kernel updating behind us.  That patch
was upstreamed and is now unnecessary.  I have a patch queued to
address it.

Thanks for all the testing.  This was quite an invasive change and it needed it.

Thanks,
Jon

>
> Anuj, the remaining failure is in meta-intel:
> ERROR: ParseError at 
> /home/pokybuild/yocto-worker/meta-intel/build/meta-intel/conf/machine/include/intel-corei7-64-common.inc:6:
>  Could not include required file conf/machine/include/tune-corei7.inc
>
> Can you take care of fixing that?
>
> I you want to test, my branch is here:
>
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=abelloni/testing
>
>
>
> On 16/08/2021 18:01:41-0400, Jon Mason wrote:
> > New in v2
> > * Fix relocation oversight issue found by Alexandre Belloni
> > * More aggressive sorting of Arm, putting each tune into it's respective
> >   design versioned family
> >
> > I ran a quick and dirty CI on this via gitlab, though now including
> > machines for all present in meta-yocto-bsp.  The results can be found
> > at https://gitlab.com/jonmason00/poky/-/pipelines/353961908
> > NOTE: CI is also including patches from upcoming series to support
> > Cortex-R.  So, it's not 100% pristine.
> >
> > ---
> >
> > Move all tune files into their architecture directory.
> >
> > I'm doing this all as one series, even though they are going to
> > different repos, as an attempt to make this as atomic as possible.
> >
> >
> > Jon Mason (3):
> >   conf/machine: move tune files to architecture directories
> >   yocto-bsp: update machine confs with new tune locations
> >   docs: update docs with new tune locations
> >
> >  documentation/bsp-guide/bsp.rst   | 4 ++--
> >  documentation/dev-manual/common-tasks.rst | 2 +-
> >  documentation/ref-manual/variables.rst| 2 +-
> >  meta-yocto-bsp/conf/machine/beaglebone-yocto.conf | 2 +-
> >  meta-yocto-bsp/conf/machine/edgerouter.conf   | 2 +-
> >  meta-yocto-bsp/conf/machine/genericx86-64.conf| 2 +-
> >  meta-yocto-bsp/conf/machine/genericx86.conf   | 2 +-
> >  meta-yocto-bsp/conf/machine/include/genericx86-common.inc | 4 ++--
> >  meta/conf/machine/include/{ => arm/armv4}/tune-arm920t.inc| 0
> >  meta/conf/machine/include/{ => arm/armv4}/tune-arm9tdmi.inc   | 0
> >  meta/conf/machine/include/{ => arm/armv4}/tune-ep9312.inc | 0
> >  .../machine/include/{ => arm/armv4}/tune-strongarm1100.inc| 0
> >  meta/conf/machine/include/{ => arm/armv5}/tune-arm926ejs.inc  | 0
> >  meta/conf/machine/include/{ => arm/armv5}/tune-iwmmxt.inc | 0
> >  meta/conf/machine/include/{ => arm/armv5}/tune-xscale.inc | 0
> >  .../conf/machine/include/{ => arm/armv6}/tune-arm1136jf-s.inc | 0
> >  .../conf/machine/include/{ => arm/armv6}/tune-arm1176jz-s.inc | 0
> >  .../{tune-cortex-m0.inc => arm/armv6m/tune-cortexm0.inc}  | 0
> >  .../armv6m/tune-cortexm0plus.inc} | 0
> >  meta/conf/machine/include/{ => arm/armv6m}/tune-cortexm1.inc  | 0
> >  meta/conf/machine/include/{ => arm/armv7a}/tune-cortexa15.inc | 0
> >  meta/conf/machine/include/{ => arm/armv7a}/tune-cortexa17.inc | 0
> >  meta/conf/machine/include/{ => arm/armv7a}/tune-cortexa5.inc  | 0
> >  meta/conf/machine/include/{ => arm/armv7a}/tune-cortexa7.inc  | 0
> >  meta/conf/machine/include/{ => arm/armv7a}/tune-cortexa8.inc  | 0
> >  meta/conf/machine/include/{ => arm/armv7a}/tune-cortexa9.inc  | 0
> >  meta/conf/machine/include/{ => arm/armv7m}/tune-cortexm3.inc  | 0
> >  meta/conf/machine/include/{ => arm/armv7m}/tune-cortexm4.inc  | 0
> >  meta/conf/machine/include/{ => arm/armv7m}/tune-cortexm7.inc  | 0
> >  .../machine/include/{ => arm/armv8-2a}/tune-cortexa55.inc | 0
> >  meta/conf/machine/include/{ => arm/armv8a}/tune-cortexa32.inc | 0
> >  meta/conf/machine/include/{ => arm/armv8a}/tune-cortexa35.inc | 0
> >  meta/conf/machine/include/{ => arm/armv8a}/tune-cortexa53.inc | 0
> >  .../include/{ => arm/armv8a}/tune-cortexa57-cortexa53.inc | 0
> >  meta/conf/machine/include/{ => arm/armv8a}/tune-cortexa57.inc | 0
> >  .../include/{ => arm/armv8a}/tune-cortexa72-cortexa53.inc | 0
> >  meta/conf/machine/include/{ => arm/armv8a}/tune-cortexa72.inc | 0
> >  .../include/{ => arm/armv8a}/tune-cortexa73-cortexa53.inc | 0
> >  meta/conf/machine/include/{ => arm/armv8a}/tune-thunderx.inc  | 0
> >  meta/conf/machine/include/{ => m68k}/tune-mcf5441x.inc| 0
> >  

Re: [OE-core] [PATCH] glibc: package the stub .a libaries into glibc-dev

[Khem Raj]

hmm I am seeing pseudo build failures on master-next on all arches see
[1].  I wonder if this is related

https://errors.yoctoproject.org/Errors/Details/601473/

On Tue, Aug 17, 2021 at 4:46 PM Khem Raj  wrote:
>
> On Tue, Aug 17, 2021 at 3:29 PM Ross Burton  wrote:
> >
> > In glibc 2.34, the libraries libpthread, libdl, libutil, libanl have
> > been integrated into libc. To retain compatibility with old binaries the
> > shared libaries are still shipped but are empty, and to keep software
> > building there are empty static libraries.
> >
> > However, these static libraries get packaged into glibc-staticdev (as
> > they should be), but by this design they should be in glibc-dev.
> >
> > https://sourceware.org/pipermail/libc-alpha/2021-August/129718.html
> >
>
> this patch is ok.
>
> > Signed-off-by: Ross Burton 
> > ---
> >  meta/recipes-core/glibc/glibc-package.inc | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-core/glibc/glibc-package.inc 
> > b/meta/recipes-core/glibc/glibc-package.inc
> > index 3026aec9b6f..56fbf8b08ce 100644
> > --- a/meta/recipes-core/glibc/glibc-package.inc
> > +++ b/meta/recipes-core/glibc/glibc-package.inc
> > @@ -22,6 +22,7 @@ ARCH_DYNAMIC_LOADER = ""
> >  ARCH_DYNAMIC_LOADER:aarch64 = "ld-linux-${TARGET_ARCH}.so.1"
> >  libc_baselibs:append = " ${@oe.utils.conditional('ARCH_DYNAMIC_LOADER', 
> > '', '', '${root_prefix}/lib/${ARCH_DYNAMIC_LOADER}', d)}"
> >  INSANE_SKIP:${PN}:append:aarch64 = " libdir"
> > +INSANE_SKIP:${PN}-dev += "staticdev"
> >
> >  FILES:${PN} = "${libc_baselibs} ${libexecdir}/* ${sysconfdir}/ld.so.conf"
> >  RRECOMMENDS:${PN} = "${@bb.utils.contains('DISTRO_FEATURES', 'ldconfig', 
> > '${MLPREFIX}ldconfig', '', d)}"
> > @@ -38,7 +39,7 @@ FILES:sln = "${base_sbindir}/sln"
> >  FILES:${PN}-pic = "${libdir}/*_pic.a ${libdir}/*_pic.map 
> > ${libdir}/libc_pic/*.o"
> >  FILES:libsotruss = "${libdir}/audit/sotruss-lib.so"
> >  FILES_SOLIBSDEV = "${libdir}/lib*${SOLIBSDEV}"
> > -FILES:${PN}-dev += "${libdir}/*_nonshared.a ${base_libdir}/*_nonshared.a 
> > ${base_libdir}/*.o ${datadir}/aclocal"
> > +FILES:${PN}-dev += "${libdir}/libpthread.a ${libdir}/libdl.a 
> > ${libdir}/libutil.a ${libdir}/libanl.a ${libdir}/*_nonshared.a 
> > ${base_libdir}/*_nonshared.a ${base_libdir}/*.o ${datadir}/aclocal"
> >  RDEPENDS:${PN}-dev = "linux-libc-headers-dev"
> >  FILES:${PN}-staticdev += "${libdir}/*.a ${base_libdir}/*.a"
> >  FILES:nscd = "${sbindir}/nscd* ${sysconfdir}/init.d/nscd 
> > ${systemd_unitdir}/system/nscd* ${sysconfdir}/tmpfiles.d/nscd.conf \
> > --
> > 2.32.0
> >
> >
> > 
> >

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154905): 
https://lists.openembedded.org/g/openembedded-core/message/154905
Mute This Topic: https://lists.openembedded.org/mt/84960232/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] glibc: package the stub .a libaries into glibc-dev

[Khem Raj]

On Tue, Aug 17, 2021 at 3:29 PM Ross Burton  wrote:
>
> In glibc 2.34, the libraries libpthread, libdl, libutil, libanl have
> been integrated into libc. To retain compatibility with old binaries the
> shared libaries are still shipped but are empty, and to keep software
> building there are empty static libraries.
>
> However, these static libraries get packaged into glibc-staticdev (as
> they should be), but by this design they should be in glibc-dev.
>
> https://sourceware.org/pipermail/libc-alpha/2021-August/129718.html
>

this patch is ok.

> Signed-off-by: Ross Burton 
> ---
>  meta/recipes-core/glibc/glibc-package.inc | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/glibc/glibc-package.inc 
> b/meta/recipes-core/glibc/glibc-package.inc
> index 3026aec9b6f..56fbf8b08ce 100644
> --- a/meta/recipes-core/glibc/glibc-package.inc
> +++ b/meta/recipes-core/glibc/glibc-package.inc
> @@ -22,6 +22,7 @@ ARCH_DYNAMIC_LOADER = ""
>  ARCH_DYNAMIC_LOADER:aarch64 = "ld-linux-${TARGET_ARCH}.so.1"
>  libc_baselibs:append = " ${@oe.utils.conditional('ARCH_DYNAMIC_LOADER', '', 
> '', '${root_prefix}/lib/${ARCH_DYNAMIC_LOADER}', d)}"
>  INSANE_SKIP:${PN}:append:aarch64 = " libdir"
> +INSANE_SKIP:${PN}-dev += "staticdev"
>
>  FILES:${PN} = "${libc_baselibs} ${libexecdir}/* ${sysconfdir}/ld.so.conf"
>  RRECOMMENDS:${PN} = "${@bb.utils.contains('DISTRO_FEATURES', 'ldconfig', 
> '${MLPREFIX}ldconfig', '', d)}"
> @@ -38,7 +39,7 @@ FILES:sln = "${base_sbindir}/sln"
>  FILES:${PN}-pic = "${libdir}/*_pic.a ${libdir}/*_pic.map 
> ${libdir}/libc_pic/*.o"
>  FILES:libsotruss = "${libdir}/audit/sotruss-lib.so"
>  FILES_SOLIBSDEV = "${libdir}/lib*${SOLIBSDEV}"
> -FILES:${PN}-dev += "${libdir}/*_nonshared.a ${base_libdir}/*_nonshared.a 
> ${base_libdir}/*.o ${datadir}/aclocal"
> +FILES:${PN}-dev += "${libdir}/libpthread.a ${libdir}/libdl.a 
> ${libdir}/libutil.a ${libdir}/libanl.a ${libdir}/*_nonshared.a 
> ${base_libdir}/*_nonshared.a ${base_libdir}/*.o ${datadir}/aclocal"
>  RDEPENDS:${PN}-dev = "linux-libc-headers-dev"
>  FILES:${PN}-staticdev += "${libdir}/*.a ${base_libdir}/*.a"
>  FILES:nscd = "${sbindir}/nscd* ${sysconfdir}/init.d/nscd 
> ${systemd_unitdir}/system/nscd* ${sysconfdir}/tmpfiles.d/nscd.conf \
> --
> 2.32.0
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154904): 
https://lists.openembedded.org/g/openembedded-core/message/154904
Mute This Topic: https://lists.openembedded.org/mt/84960232/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [meta-oe][PATCH] meta-oe: libusbgx: Configure the Devices Used

[Khem Raj]

On Tue, Aug 17, 2021 at 2:47 PM Maxim Sloyko via
lists.openembedded.org 
wrote:
>
> Add ability to configure the UDC used for specific schema.
> The feature is backwards compatible, so existing users don't need to
> change anything.
>
> If one wants to specify which UDC is used for specific schema,
> for example, `eth0`, they can add this variable to the configuration
> file:
>
> UDC_FOR_SCHEMA_eth0=f800.udc
>
> If the device file exists in /sys/class/udc when the gadget is started,
> it will be used for this schema.
>
> If this configuration is not present, first available device is picked.
>

I have already picked up your prior patch and its in master now
https://github.com/openembedded/meta-openembedded/commit/3cf2475ea059184820525bb949c11c3da0e64af8

if there is delta on top of this please rebase and send

> Signed-off-by: Maksym Sloyko 
> ---
>  meta-oe/recipes-support/libusbgx/libusbgx/gadget-start | 7 ++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
>  mode change 100644 => 100755 
> meta-oe/recipes-support/libusbgx/libusbgx/gadget-start
>
> diff --git a/meta-oe/recipes-support/libusbgx/libusbgx/gadget-start 
> b/meta-oe/recipes-support/libusbgx/libusbgx/gadget-start
> old mode 100644
> new mode 100755
> index 1a106b785..9e22671a9
> --- a/meta-oe/recipes-support/libusbgx/libusbgx/gadget-start
> +++ b/meta-oe/recipes-support/libusbgx/libusbgx/gadget-start
> @@ -7,5 +7,10 @@ for i in $IMPORT_SCHEMAS; do
>  done
>
>  for i in $ENABLED_SCHEMAS; do
> -ls /sys/class/udc/ > /sys/kernel/config/usb_gadget/"$i"/UDC
> +configured_udc=$(eval 'echo ${UDC_FOR_SCHEMA_'"$i"'}')
> +if [ -n "${configured_udc}" ] && [ -e "/sys/class/udc/${configured_udc}" 
> ]; then
> +echo ${configured_udc} > /sys/kernel/config/usb_gadget/"$i"/UDC
> +else
> +ls /sys/class/udc/ > /sys/kernel/config/usb_gadget/"$i"/UDC
> +fi
>  done
> --
> 2.32.0.605.g8dce9f2422-goog
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154903): 
https://lists.openembedded.org/g/openembedded-core/message/154903
Mute This Topic: https://lists.openembedded.org/mt/84959369/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] oeqa/sdk: add relocation test for buildtools

[Ross Burton]

The buildtools-extended tarball includes GCC, which relies on being
relocated correctly to work.  Add a test case that verifies that the
loader paths have all been relocated, as otherwise there are
hard-to-debug errors at build time.

Signed-off-by: Ross Burton 
---
 meta/lib/oeqa/sdk/buildtools-cases/gcc.py | 29 +++
 1 file changed, 29 insertions(+)
 create mode 100644 meta/lib/oeqa/sdk/buildtools-cases/gcc.py

diff --git a/meta/lib/oeqa/sdk/buildtools-cases/gcc.py 
b/meta/lib/oeqa/sdk/buildtools-cases/gcc.py
new file mode 100644
index 000..36ba15b1340
--- /dev/null
+++ b/meta/lib/oeqa/sdk/buildtools-cases/gcc.py
@@ -0,0 +1,29 @@
+#
+# SPDX-License-Identifier: MIT
+#
+
+import os.path
+from oeqa.sdk.case import OESDKTestCase
+
+class GccTests(OESDKTestCase):
+def test_verify_specs(self):
+"""
+Verify that the compiler has been relocated successfully and isn't
+looking in the hard-coded prefix.
+"""
+# Canonicalise the SDK root
+sdk_base = os.path.realpath(self.tc.sdk_dir)
+# Canonicalise the location of GCC
+gcc_path = os.path.realpath(self._run("command -v gcc").strip())
+# Skip the test if the GCC didn't come from the buildtools, as it only
+# comes with buildtools-extended-tarball.
+if os.path.commonprefix((sdk_base, gcc_path)) != sdk_base:
+self.skipTest("Buildtools does not provide GCC")
+
+# This is the prefix that GCC is build with, and should be replaced at
+# installation time.
+sdkpath = self.td.get("SDKPATH")
+self.assertTrue(sdkpath)
+
+for line in self._run('gcc -dumpspecs').splitlines():
+self.assertNotIn(sdkpath, line)
-- 
2.32.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154902): 
https://lists.openembedded.org/g/openembedded-core/message/154902
Mute This Topic: https://lists.openembedded.org/mt/84960404/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] glibc: package the stub .a libaries into glibc-dev

[Ross Burton]

In glibc 2.34, the libraries libpthread, libdl, libutil, libanl have
been integrated into libc. To retain compatibility with old binaries the
shared libaries are still shipped but are empty, and to keep software
building there are empty static libraries.

However, these static libraries get packaged into glibc-staticdev (as
they should be), but by this design they should be in glibc-dev.

https://sourceware.org/pipermail/libc-alpha/2021-August/129718.html

Signed-off-by: Ross Burton 
---
 meta/recipes-core/glibc/glibc-package.inc | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-core/glibc/glibc-package.inc 
b/meta/recipes-core/glibc/glibc-package.inc
index 3026aec9b6f..56fbf8b08ce 100644
--- a/meta/recipes-core/glibc/glibc-package.inc
+++ b/meta/recipes-core/glibc/glibc-package.inc
@@ -22,6 +22,7 @@ ARCH_DYNAMIC_LOADER = ""
 ARCH_DYNAMIC_LOADER:aarch64 = "ld-linux-${TARGET_ARCH}.so.1"
 libc_baselibs:append = " ${@oe.utils.conditional('ARCH_DYNAMIC_LOADER', '', 
'', '${root_prefix}/lib/${ARCH_DYNAMIC_LOADER}', d)}"
 INSANE_SKIP:${PN}:append:aarch64 = " libdir"
+INSANE_SKIP:${PN}-dev += "staticdev"
 
 FILES:${PN} = "${libc_baselibs} ${libexecdir}/* ${sysconfdir}/ld.so.conf"
 RRECOMMENDS:${PN} = "${@bb.utils.contains('DISTRO_FEATURES', 'ldconfig', 
'${MLPREFIX}ldconfig', '', d)}"
@@ -38,7 +39,7 @@ FILES:sln = "${base_sbindir}/sln"
 FILES:${PN}-pic = "${libdir}/*_pic.a ${libdir}/*_pic.map 
${libdir}/libc_pic/*.o"
 FILES:libsotruss = "${libdir}/audit/sotruss-lib.so"
 FILES_SOLIBSDEV = "${libdir}/lib*${SOLIBSDEV}"
-FILES:${PN}-dev += "${libdir}/*_nonshared.a ${base_libdir}/*_nonshared.a 
${base_libdir}/*.o ${datadir}/aclocal"
+FILES:${PN}-dev += "${libdir}/libpthread.a ${libdir}/libdl.a 
${libdir}/libutil.a ${libdir}/libanl.a ${libdir}/*_nonshared.a 
${base_libdir}/*_nonshared.a ${base_libdir}/*.o ${datadir}/aclocal"
 RDEPENDS:${PN}-dev = "linux-libc-headers-dev"
 FILES:${PN}-staticdev += "${libdir}/*.a ${base_libdir}/*.a"
 FILES:nscd = "${sbindir}/nscd* ${sysconfdir}/init.d/nscd 
${systemd_unitdir}/system/nscd* ${sysconfdir}/tmpfiles.d/nscd.conf \
-- 
2.32.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154901): 
https://lists.openembedded.org/g/openembedded-core/message/154901
Mute This Topic: https://lists.openembedded.org/mt/84960232/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] oeqa/sdk: add HTTPS test for buildtools

[Ross Burton]

Verify that HTTPS connections work in both wget and Python, as this
depends on variables correctly pointing to the certificate chain.

Signed-off-by: Ross Burton 
---
 meta/lib/oeqa/sdk/buildtools-cases/https.py | 20 
 1 file changed, 20 insertions(+)
 create mode 100644 meta/lib/oeqa/sdk/buildtools-cases/https.py

diff --git a/meta/lib/oeqa/sdk/buildtools-cases/https.py 
b/meta/lib/oeqa/sdk/buildtools-cases/https.py
new file mode 100644
index 000..61020abdb3f
--- /dev/null
+++ b/meta/lib/oeqa/sdk/buildtools-cases/https.py
@@ -0,0 +1,20 @@
+#
+# SPDX-License-Identifier: MIT
+#
+
+from oeqa.sdk.case import OESDKTestCase
+from oeqa.utils.subprocesstweak import errors_have_output
+errors_have_output()
+
+class HTTPTests(OESDKTestCase):
+"""
+Verify that HTTPS certificates are working correctly, as this depends on
+environment variables being set correctly.
+"""
+
+def test_wget(self):
+self._run('env -i wget --debug https://www.example.com')
+
+def test_python(self):
+# urlopen() returns a file-like object on success and throws an 
exception otherwise
+self._run('python3 -c \'import urllib.request; 
urllib.request.urlopen("https://www.example.com/;)\'')
-- 
2.32.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154900): 
https://lists.openembedded.org/g/openembedded-core/message/154900
Mute This Topic: https://lists.openembedded.org/mt/84959867/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [gatesgarth][PATCH] glib-2.0: backport 2.65.0 commit to fix intermittent race condition

[Gabriel Valcazar]

glib versions between 2.63.3 and 2.64.6 are susceptible to a race condition
that has a low chance of happening, but can cause segmentation faults. For
example, when using NetworkManager 1.22.0 or newer, a segmentation fault can
happen even when running a simple command like 'nmcli'.

Backport a commit from glib 2.65.0 that fixes this issue to avoid unexpected
behaviour.

Signed-off-by: Gabriel Valcazar 
---
 ...-minor-race-between-GCancellable-and.patch | 217 ++
 meta/recipes-core/glib-2.0/glib-2.0_2.64.5.bb |   1 +
 2 files changed, 218 insertions(+)
 create mode 100644 
meta/recipes-core/glib-2.0/glib-2.0/0001-gcancellable-Fix-minor-race-between-GCancellable-and.patch

diff --git 
a/meta/recipes-core/glib-2.0/glib-2.0/0001-gcancellable-Fix-minor-race-between-GCancellable-and.patch
 
b/meta/recipes-core/glib-2.0/glib-2.0/0001-gcancellable-Fix-minor-race-between-GCancellable-and.patch
new file mode 100644
index 00..44c824eaa8
--- /dev/null
+++ 
b/meta/recipes-core/glib-2.0/glib-2.0/0001-gcancellable-Fix-minor-race-between-GCancellable-and.patch
@@ -0,0 +1,217 @@
+From d7e27bdce2f2f34efd860875e5c01425891aef56 Mon Sep 17 00:00:00 2001
+From: Philip Withnall 
+Date: Fri, 21 Feb 2020 14:44:44 +
+Subject: [PATCH] gcancellable: Fix minor race between GCancellable and
+ GCancellableSource
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+There’s a minor race condition between cancellation of a `GCancellable`,
+and disposal/finalisation of a `GCancellableSource` in another thread.
+
+Thread A   Thread B
+ g_cancellable_cancel(C)
+ →cancellable_source_cancelled(C, S)
+   g_source_unref(S)
+   cancellable_source_dispose(S)
+ →→g_source_ref(S)
+ →→# S is invalid at this point; crash
+
+Thankfully, the `GCancellable` sets `cancelled_running` while it’s
+emitting the `cancelled` signal, so if `cancellable_source_dispose()` is
+called while that’s high, we know that the thread which is doing the
+cancellation has already started (or is committed to starting) calling
+`cancellable_source_cancelled()`.
+
+Fix the race by resurrecting the `GCancellableSource` in
+`cancellable_source_dispose()`, and signalling this using
+`GCancellableSource.resurrected_during_cancellation`. Check for that
+flag in `cancellable_source_cancelled()` and ignore cancellation if it’s
+set.
+
+The modifications to `resurrected_during_cancellation` and the
+cancellable source’s refcount have to be done with `cancellable_mutex`
+held so that they are seen atomically by each thread. This should not
+affect performance too much, as it only happens during cancellation or
+disposal of a `GCancellableSource`.
+
+Signed-off-by: Philip Withnall 
+
+Fixes: #1841
+---
+ gio/gcancellable.c  | 43 +++
+ gio/tests/cancellable.c | 77 +
+ 2 files changed, 120 insertions(+)
+
+diff --git a/gio/gcancellable.c b/gio/gcancellable.c
+index d9e58b8e8..e687cca23 100644
+--- a/gio/gcancellable.c
 b/gio/gcancellable.c
+@@ -643,6 +643,8 @@ typedef struct {
+ 
+   GCancellable *cancellable;
+   gulongcancelled_handler;
++  /* Protected by cancellable_mutex: */
++  gboolean  resurrected_during_cancellation;
+ } GCancellableSource;
+ 
+ /*
+@@ -661,8 +663,24 @@ cancellable_source_cancelled (GCancellable *cancellable,
+ gpointer  user_data)
+ {
+   GSource *source = user_data;
++  GCancellableSource *cancellable_source = (GCancellableSource *) source;
++
++  g_mutex_lock (_mutex);
++
++  /* Drop the reference added in cancellable_source_dispose(); see the 
comment there.
++   * The reference must be dropped after unlocking @cancellable_mutex since
++   * it could be the final reference, and the dispose function takes
++   * @cancellable_mutex. */
++  if (cancellable_source->resurrected_during_cancellation)
++{
++  cancellable_source->resurrected_during_cancellation = FALSE;
++  g_mutex_unlock (_mutex);
++  g_source_unref (source);
++  return;
++}
+ 
+   g_source_ref (source);
++  g_mutex_unlock (_mutex);
+   g_source_set_ready_time (source, 0);
+   g_source_unref (source);
+ }
+@@ -684,12 +702,37 @@ cancellable_source_dispose (GSource *source)
+ {
+   GCancellableSource *cancellable_source = (GCancellableSource *)source;
+ 
++  g_mutex_lock (_mutex);
++
+   if (cancellable_source->cancellable)
+ {
++  if (cancellable_source->cancellable->priv->cancelled_running)
++{
++  /* There can be a race here: if thread A has called
++   * g_cancellable_cancel() and has got as far as committing to call
++   * cancellable_source_cancelled(), then thread B drops the final
++   * ref on the GCancellableSource before g_source_ref() is called in
++   * cancellable_source_cancelled(), then cancellable_source_dispose()
++   * 

[OE-core] [meta-oe][PATCH] meta-oe: libusbgx: Configure the Devices Used

[Maxim Sloyko via lists.openembedded.org]

Add ability to configure the UDC used for specific schema.
The feature is backwards compatible, so existing users don't need to
change anything.

If one wants to specify which UDC is used for specific schema,
for example, `eth0`, they can add this variable to the configuration
file:

UDC_FOR_SCHEMA_eth0=f800.udc

If the device file exists in /sys/class/udc when the gadget is started,
it will be used for this schema.

If this configuration is not present, first available device is picked.

Signed-off-by: Maksym Sloyko 
---
 meta-oe/recipes-support/libusbgx/libusbgx/gadget-start | 7 ++-
 1 file changed, 6 insertions(+), 1 deletion(-)
 mode change 100644 => 100755 
meta-oe/recipes-support/libusbgx/libusbgx/gadget-start

diff --git a/meta-oe/recipes-support/libusbgx/libusbgx/gadget-start 
b/meta-oe/recipes-support/libusbgx/libusbgx/gadget-start
old mode 100644
new mode 100755
index 1a106b785..9e22671a9
--- a/meta-oe/recipes-support/libusbgx/libusbgx/gadget-start
+++ b/meta-oe/recipes-support/libusbgx/libusbgx/gadget-start
@@ -7,5 +7,10 @@ for i in $IMPORT_SCHEMAS; do
 done
 
 for i in $ENABLED_SCHEMAS; do
-ls /sys/class/udc/ > /sys/kernel/config/usb_gadget/"$i"/UDC
+configured_udc=$(eval 'echo ${UDC_FOR_SCHEMA_'"$i"'}')
+if [ -n "${configured_udc}" ] && [ -e "/sys/class/udc/${configured_udc}" 
]; then
+echo ${configured_udc} > /sys/kernel/config/usb_gadget/"$i"/UDC
+else
+ls /sys/class/udc/ > /sys/kernel/config/usb_gadget/"$i"/UDC
+fi
 done
-- 
2.32.0.605.g8dce9f2422-goog


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154898): 
https://lists.openembedded.org/g/openembedded-core/message/154898
Mute This Topic: https://lists.openembedded.org/mt/84959369/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v2 0/3] tunes: the great migration

[Alexandre Belloni]

Hello Jon,

I did run that through the autobuilders:

https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2457

This is mostly good, the meta-arm failure is about a kernel patch not
applying, I don't think it is related, you'd have to rebase
meta-arm-bsp/recipes-kernel/linux/linux-yocto-5.10/n1sdp/0005-r8169-Fix-to-avoid-duplicate-sysfs-entry-creation-er.patch

Anuj, the remaining failure is in meta-intel:
ERROR: ParseError at 
/home/pokybuild/yocto-worker/meta-intel/build/meta-intel/conf/machine/include/intel-corei7-64-common.inc:6:
 Could not include required file conf/machine/include/tune-corei7.inc

Can you take care of fixing that?

I you want to test, my branch is here:

http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=abelloni/testing



On 16/08/2021 18:01:41-0400, Jon Mason wrote:
> New in v2
> * Fix relocation oversight issue found by Alexandre Belloni
> * More aggressive sorting of Arm, putting each tune into it's respective
>   design versioned family
> 
> I ran a quick and dirty CI on this via gitlab, though now including
> machines for all present in meta-yocto-bsp.  The results can be found
> at https://gitlab.com/jonmason00/poky/-/pipelines/353961908
> NOTE: CI is also including patches from upcoming series to support
> Cortex-R.  So, it's not 100% pristine. 
> 
> ---
> 
> Move all tune files into their architecture directory.
> 
> I'm doing this all as one series, even though they are going to
> different repos, as an attempt to make this as atomic as possible.
> 
> 
> Jon Mason (3):
>   conf/machine: move tune files to architecture directories
>   yocto-bsp: update machine confs with new tune locations
>   docs: update docs with new tune locations
> 
>  documentation/bsp-guide/bsp.rst   | 4 ++--
>  documentation/dev-manual/common-tasks.rst | 2 +-
>  documentation/ref-manual/variables.rst| 2 +-
>  meta-yocto-bsp/conf/machine/beaglebone-yocto.conf | 2 +-
>  meta-yocto-bsp/conf/machine/edgerouter.conf   | 2 +-
>  meta-yocto-bsp/conf/machine/genericx86-64.conf| 2 +-
>  meta-yocto-bsp/conf/machine/genericx86.conf   | 2 +-
>  meta-yocto-bsp/conf/machine/include/genericx86-common.inc | 4 ++--
>  meta/conf/machine/include/{ => arm/armv4}/tune-arm920t.inc| 0
>  meta/conf/machine/include/{ => arm/armv4}/tune-arm9tdmi.inc   | 0
>  meta/conf/machine/include/{ => arm/armv4}/tune-ep9312.inc | 0
>  .../machine/include/{ => arm/armv4}/tune-strongarm1100.inc| 0
>  meta/conf/machine/include/{ => arm/armv5}/tune-arm926ejs.inc  | 0
>  meta/conf/machine/include/{ => arm/armv5}/tune-iwmmxt.inc | 0
>  meta/conf/machine/include/{ => arm/armv5}/tune-xscale.inc | 0
>  .../conf/machine/include/{ => arm/armv6}/tune-arm1136jf-s.inc | 0
>  .../conf/machine/include/{ => arm/armv6}/tune-arm1176jz-s.inc | 0
>  .../{tune-cortex-m0.inc => arm/armv6m/tune-cortexm0.inc}  | 0
>  .../armv6m/tune-cortexm0plus.inc} | 0
>  meta/conf/machine/include/{ => arm/armv6m}/tune-cortexm1.inc  | 0
>  meta/conf/machine/include/{ => arm/armv7a}/tune-cortexa15.inc | 0
>  meta/conf/machine/include/{ => arm/armv7a}/tune-cortexa17.inc | 0
>  meta/conf/machine/include/{ => arm/armv7a}/tune-cortexa5.inc  | 0
>  meta/conf/machine/include/{ => arm/armv7a}/tune-cortexa7.inc  | 0
>  meta/conf/machine/include/{ => arm/armv7a}/tune-cortexa8.inc  | 0
>  meta/conf/machine/include/{ => arm/armv7a}/tune-cortexa9.inc  | 0
>  meta/conf/machine/include/{ => arm/armv7m}/tune-cortexm3.inc  | 0
>  meta/conf/machine/include/{ => arm/armv7m}/tune-cortexm4.inc  | 0
>  meta/conf/machine/include/{ => arm/armv7m}/tune-cortexm7.inc  | 0
>  .../machine/include/{ => arm/armv8-2a}/tune-cortexa55.inc | 0
>  meta/conf/machine/include/{ => arm/armv8a}/tune-cortexa32.inc | 0
>  meta/conf/machine/include/{ => arm/armv8a}/tune-cortexa35.inc | 0
>  meta/conf/machine/include/{ => arm/armv8a}/tune-cortexa53.inc | 0
>  .../include/{ => arm/armv8a}/tune-cortexa57-cortexa53.inc | 0
>  meta/conf/machine/include/{ => arm/armv8a}/tune-cortexa57.inc | 0
>  .../include/{ => arm/armv8a}/tune-cortexa72-cortexa53.inc | 0
>  meta/conf/machine/include/{ => arm/armv8a}/tune-cortexa72.inc | 0
>  .../include/{ => arm/armv8a}/tune-cortexa73-cortexa53.inc | 0
>  meta/conf/machine/include/{ => arm/armv8a}/tune-thunderx.inc  | 0
>  meta/conf/machine/include/{ => m68k}/tune-mcf5441x.inc| 0
>  .../conf/machine/include/{ => microblaze}/tune-microblaze.inc | 0
>  meta/conf/machine/include/{ => mips}/qemuboot-mips.inc| 0
>  meta/conf/machine/include/mips/tune-mips-24k.inc  | 2 +-
>  meta/conf/machine/include/mips/tune-mips-74k.inc  | 2 +-
>  meta/conf/machine/include/{ => mips}/tune-mips32.inc  | 0
>  meta/conf/machine/include/{ => mips}/tune-mips32r2.inc| 2 +-
>  meta/conf/machine/include/{ => mips}/tune-mips32r6.inc| 0

Re: [OE-core][PATCH v2 2/2] oeqa: wic: Add tests for --no-fstab-update

[Daniel Gomez]

Hi,

On Tue, 17 Aug 2021 at 15:34, Alexandre Belloni
 wrote:
>
> Hi,
>
> On 16/08/2021 10:05:08+0200, Daniel Gomez wrote:
> > Hi Alexandre,
> >
> >
> > On Fri, 13 Aug 2021 at 07:41, Daniel Gomez via lists.openembedded.org
> >  wrote:
> > >
> > > Hi Alexandre,
> > >
> > > On Thu, 12 Aug 2021 at 18:34, Alexandre Belloni
> > >  wrote:
> > > >
> > > > Hello,
> > > >
> > > > On 10/08/2021 22:11:01+0200, Daniel Gomez wrote:
> > > > > Add tests for the --no-fstab-update wic part command.
> > > > >
> > > > > Signed-off-by: Daniel Gomez 
> > > > > ---
> > > > >  meta/lib/oeqa/selftest/cases/wic.py | 56 
> > > > > +
> > > > >  1 file changed, 56 insertions(+)
> > > > >
> > > > > diff --git a/meta/lib/oeqa/selftest/cases/wic.py 
> > > > > b/meta/lib/oeqa/selftest/cases/wic.py
> > > > > index 2efbe514c1..a58360851a 100644
> > > > > --- a/meta/lib/oeqa/selftest/cases/wic.py
> > > > > +++ b/meta/lib/oeqa/selftest/cases/wic.py
> > > > > @@ -11,6 +11,7 @@
> > > > >  import os
> > > > >  import sys
> > > > >  import unittest
> > > > > +import hashlib
> > > > >
> > > > >  from glob import glob
> > > > >  from shutil import rmtree, copy
> > > > > @@ -686,6 +687,61 @@ part /etc --source rootfs --fstype=ext4 
> > > > > --change-directory=etc
> > > > >% (wks_file, self.resultdir), 
> > > > > ignore_status=True).status)
> > > > >  os.remove(wks_file)
> > > > >
> > > > > +def test_no_fstab_update(self):
> > > > > +"""Test --no-fstab-update wks option."""
> > > > > +
> > > > > +oldpath = os.environ['PATH']
> > > > > +os.environ['PATH'] = get_bb_var("PATH", "wic-tools")
> > > > > +
> > > > > +# Get stock fstab from base-files recipe
> > > > > +bitbake('base-files')
> > > > > +bf_fstab = os.path.join(get_bb_var('WORKDIR', 
> > > > > 'base-files'),'image/etc/fstab')
> > > > > +bf_fstab_md5sum = runCmd('md5sum %s 2>/dev/null' % 
> > > > > bf_fstab).output.split(" ")[0]
> > > > > +
> > > >
> > > > This failed on the autobuilders:
> > > >
> > > >   File 
> > > > "/home/pokybuild/yocto-worker/oe-selftest-debian/build/meta/lib/oeqa/selftest/cases/wic.py",
> > > >  line 699, in test_no_fstab_update
> > > > bf_fstab_md5sum = runCmd('md5sum %s 2>/dev/null' % 
> > > > bf_fstab).output.split(" ")[0]
> > > >   File 
> > > > "/home/pokybuild/yocto-worker/oe-selftest-debian/build/meta/lib/oeqa/utils/commands.py",
> > > >  line 207, in runCmd
> > > > raise AssertionError("Command '%s' returned non-zero exit status 
> > > > %d:\n%s" % (command, result.status, exc_output))
> > > > AssertionError: Command 'md5sum 
> > > > /home/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-15202/tmp/work/qemux86_64-poky-linux/base-files/3.0.14-r89/image/etc/fstab
> > > >  2>/dev/null' returned non-zero exit status 1:
> > > >
> > > > Full log here:
> > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/2374/steps/14/logs/stdio
> > >
> > > Thanks for letting me know. I'll take a look.
> >
> > I can't replicate the problem in my setup ('master' branch for bitbake
> > and openembedded core; 'qemux86-64' machine) . Could it be possible to
> > get the environment variables for the build?
> >
> > The problem comes when executing the first md5sum command:
> >
> > 1. bitbake 'base-files' recipe.
> > 2. Get the 'WORKDIR' for 'base-files' recipe.
> > 3. Do 'md5sum' for the 'WORKDIR' + 'image/etc/fstab' file.
> >
> > md5sum 
> > /home/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-15202/tmp/work/qemux86_64-poky-linux/base-files/3.0.14-r89/image/etc/fstab
> >
> > If the file does not exist, md5sum will return the same '1' status
> > (assuming that's the error). Could this be bause the '${WORKDIR} +
> > image' for the 'base-files' recipe is located under another directory?
> > Could we get access to that directory to know if the file was present
> > there?
> >
>
> I did run the build again and:
>
> debian10-ty-1:~$ md5sum 
> /home/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-32220/tmp/work/qemux86_64-poky-linux/base-files/3.0.14-r89/image/etc/fstab
> md5sum: 
> /home/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-32220/tmp/work/qemux86_64-poky-linux/base-files/3.0.14-r89/image/etc/fstab:
>  No such file or directory
>
> debian10-ty-1:~$ ls 
> /home/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-32220/tmp/work/qemux86_64-poky-linux/base-files/3.0.14-r89/
> deploy-rpms   license-destdir  source-date-epoch  
>   sstate-install-package_qa sstate-install-packagedata   
> sstate-install-populate_sysroot  temp
> deploy-source-date-epoch  pkgdata-pdata-input  
> sstate-install-deploy_source_date_epoch  sstate-install-package_write_rpm  
> sstate-install-populate_lic  sysroot-destdir
>
> I guess the issue is that we reuse the sstate cache and so the file is
> not present at all.

Thanks for the hint. I've just sent a v3 patch where I 

[OE-core][PATCH v3 1/2] wic: Add --no-fstab-update part option

[Daniel Gomez]

When embedding a rootfs image (e.g. 'rootfs-dir') as a partition we
might want to keep the stock fstab for that image. In such a case, use
this option to not update the fstab and use the stock one instead.

This option allows you to specify which partitions get the fstab
updated and which get the stock fstab.

The option matches the argument you can pass to wic itself where the
same action is performed but for all the partitions.

Example:
part /export --source rootfs --rootfs-dir=hockeycam-image
--fstype=ext4 --label export --align 1024 --no-fstab-update

part / --source rootfs --fstype=ext4 --label rootfs --align 1024

Signed-off-by: Daniel Gomez 
---
 scripts/lib/wic/help.py  | 3 +++
 scripts/lib/wic/ksparser.py  | 1 +
 scripts/lib/wic/partition.py | 5 +++--
 scripts/lib/wic/plugins/source/rootfs.py | 2 +-
 4 files changed, 8 insertions(+), 3 deletions(-)

diff --git a/scripts/lib/wic/help.py b/scripts/lib/wic/help.py
index 41451d1cb0..991907d3f5 100644
--- a/scripts/lib/wic/help.py
+++ b/scripts/lib/wic/help.py
@@ -991,6 +991,9 @@ DESCRIPTION
  multiple partitions and we want to keep the right
  permissions and usernames in all the partitions.

+ --no-fstab-update: This option is specific to wic. It does not update 
the
+'/etc/fstab' stock file for the given partition.
+
  --extra-space: This option is specific to wic. It adds extra
 space after the space filled by the content
 of the partition. The final size can go
diff --git a/scripts/lib/wic/ksparser.py b/scripts/lib/wic/ksparser.py
index 7a4cc83af5..0df9eb0d05 100644
--- a/scripts/lib/wic/ksparser.py
+++ b/scripts/lib/wic/ksparser.py
@@ -185,6 +185,7 @@ class KickStart():
 part.add_argument('--use-uuid', action='store_true')
 part.add_argument('--uuid')
 part.add_argument('--fsuuid')
+part.add_argument('--no-fstab-update', action='store_true')

 bootloader = subparsers.add_parser('bootloader')
 bootloader.add_argument('--append')
diff --git a/scripts/lib/wic/partition.py b/scripts/lib/wic/partition.py
index e0b2c5bdf2..ab304f1b2a 100644
--- a/scripts/lib/wic/partition.py
+++ b/scripts/lib/wic/partition.py
@@ -54,6 +54,7 @@ class Partition():
 self.uuid = args.uuid
 self.fsuuid = args.fsuuid
 self.type = args.type
+self.no_fstab_update = args.no_fstab_update
 self.updated_fstab_path = None
 self.has_fstab = False
 self.update_fstab_in_rootfs = False
@@ -286,7 +287,7 @@ class Partition():
 (self.fstype, extraopts, rootfs, label_str, self.fsuuid, 
rootfs_dir)
 exec_native_cmd(mkfs_cmd, native_sysroot, pseudo=pseudo)

-if self.updated_fstab_path and self.has_fstab:
+if self.updated_fstab_path and self.has_fstab and not 
self.no_fstab_update:
 debugfs_script_path = os.path.join(cr_workdir, "debugfs_script")
 with open(debugfs_script_path, "w") as f:
 f.write("cd etc\n")
@@ -350,7 +351,7 @@ class Partition():
 mcopy_cmd = "mcopy -i %s -s %s/* ::/" % (rootfs, rootfs_dir)
 exec_native_cmd(mcopy_cmd, native_sysroot)

-if self.updated_fstab_path and self.has_fstab:
+if self.updated_fstab_path and self.has_fstab and not 
self.no_fstab_update:
 mcopy_cmd = "mcopy -i %s %s ::/etc/fstab" % (rootfs, 
self.updated_fstab_path)
 exec_native_cmd(mcopy_cmd, native_sysroot)

diff --git a/scripts/lib/wic/plugins/source/rootfs.py 
b/scripts/lib/wic/plugins/source/rootfs.py
index 96d940a91d..2e34e715ca 100644
--- a/scripts/lib/wic/plugins/source/rootfs.py
+++ b/scripts/lib/wic/plugins/source/rootfs.py
@@ -218,7 +218,7 @@ class RootfsPlugin(SourcePlugin):
 # Update part.has_fstab here as fstab may have been added or
 # removed by the above modifications.
 part.has_fstab = os.path.exists(os.path.join(new_rootfs, 
"etc/fstab"))
-if part.update_fstab_in_rootfs and part.has_fstab:
+if part.update_fstab_in_rootfs and part.has_fstab and not 
part.no_fstab_update:
 fstab_path = os.path.join(new_rootfs, "etc/fstab")
 # Assume that fstab should always be owned by root with fixed 
permissions
 install_cmd = "install -m 0644 %s %s" % 
(part.updated_fstab_path, fstab_path)
--
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154894): 
https://lists.openembedded.org/g/openembedded-core/message/154894
Mute This Topic: https://lists.openembedded.org/mt/84957310/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][PATCH v3 2/2] oeqa: wic: Add tests for --no-fstab-update

[Daniel Gomez]

Add tests for the --no-fstab-update wic part command.

Signed-off-by: Daniel Gomez 
---
 meta/lib/oeqa/selftest/cases/wic.py | 58 +
 1 file changed, 58 insertions(+)

diff --git a/meta/lib/oeqa/selftest/cases/wic.py 
b/meta/lib/oeqa/selftest/cases/wic.py
index 2efbe514c1..3b4143414f 100644
--- a/meta/lib/oeqa/selftest/cases/wic.py
+++ b/meta/lib/oeqa/selftest/cases/wic.py
@@ -11,6 +11,7 @@
 import os
 import sys
 import unittest
+import hashlib
 
 from glob import glob
 from shutil import rmtree, copy
@@ -686,6 +687,63 @@ part /etc --source rootfs --fstype=ext4 
--change-directory=etc
   % (wks_file, self.resultdir), 
ignore_status=True).status)
 os.remove(wks_file)
 
+def test_no_fstab_update(self):
+"""Test --no-fstab-update wks option."""
+
+oldpath = os.environ['PATH']
+os.environ['PATH'] = get_bb_var("PATH", "wic-tools")
+
+# Get stock fstab from base-files recipe
+self.assertEqual(0, bitbake('base-files -c do_install').status)
+bf_fstab = os.path.join(get_bb_var('D', 'base-files'), 'etc/fstab')
+self.assertEqual(True, os.path.exists(bf_fstab))
+bf_fstab_md5sum = runCmd('md5sum %s 2>/dev/null' % 
bf_fstab).output.split(" ")[0]
+
+try:
+no_fstab_update_path = os.path.join(self.resultdir, 
'test-no-fstab-update')
+os.makedirs(no_fstab_update_path)
+wks_file = os.path.join(no_fstab_update_path, 'temp.wks')
+with open(wks_file, 'w') as wks:
+wks.writelines(['part / --source rootfs --fstype=ext4 --label 
rootfs\n',
+'part /mnt/p2 --source rootfs 
--rootfs-dir=core-image-minimal ',
+'--fstype=ext4 --label p2 
--no-fstab-update\n'])
+runCmd("wic create %s -e core-image-minimal -o %s" \
+   % (wks_file, self.resultdir))
+
+part_fstab_md5sum = []
+for i in range(1, 3):
+part = glob(os.path.join(self.resultdir, 'temp-*.direct.p') + 
str(i))[0]
+part_fstab = runCmd("debugfs -R 'cat etc/fstab' %s 
2>/dev/null" % (part))
+part_fstab_md5sum.append(hashlib.md5((part_fstab.output + 
"\n\n").encode('utf-8')).hexdigest())
+
+# '/etc/fstab' in partition 2 should contain the same stock fstab 
file
+# as the one installed by the base-file recipe.
+self.assertEqual(bf_fstab_md5sum, part_fstab_md5sum[1])
+
+# '/etc/fstab' in partition 1 should contain an updated fstab file.
+self.assertNotEqual(bf_fstab_md5sum, part_fstab_md5sum[0])
+
+finally:
+os.environ['PATH'] = oldpath
+
+def test_no_fstab_update_errors(self):
+"""Test --no-fstab-update wks option error handling."""
+wks_file = 'temp.wks'
+
+# Absolute argument.
+with open(wks_file, 'w') as wks:
+wks.write("part / --source rootfs --fstype=ext4 --no-fstab-update 
/etc")
+self.assertNotEqual(0, runCmd("wic create %s -e core-image-minimal -o 
%s" \
+  % (wks_file, self.resultdir), 
ignore_status=True).status)
+os.remove(wks_file)
+
+# Argument pointing to parent directory.
+with open(wks_file, 'w') as wks:
+wks.write("part / --source rootfs --fstype=ext4 --no-fstab-update 
././..")
+self.assertNotEqual(0, runCmd("wic create %s -e core-image-minimal -o 
%s" \
+  % (wks_file, self.resultdir), 
ignore_status=True).status)
+os.remove(wks_file)
+
 class Wic2(WicTestCase):
 
 def test_bmap_short(self):
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154895): 
https://lists.openembedded.org/g/openembedded-core/message/154895
Mute This Topic: https://lists.openembedded.org/mt/84957311/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] grep: upgrade 3.6 -> 3.7

[Denys Dmytriyenko]

GNU grep 3.7 has been released with a fix for a bug causing
"extreme performance degradation" in certain types of search.

https://www.theregister.com/2021/08/16/gnu_grep_37/

Signed-off-by: Denys Dmytriyenko 
---
 meta/recipes-extended/grep/{grep_3.6.bb => grep_3.7.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-extended/grep/{grep_3.6.bb => grep_3.7.bb} (93%)

diff --git a/meta/recipes-extended/grep/grep_3.6.bb 
b/meta/recipes-extended/grep/grep_3.7.bb
similarity index 93%
rename from meta/recipes-extended/grep/grep_3.6.bb
rename to meta/recipes-extended/grep/grep_3.7.bb
index 750575e..b0b89de 100644
--- a/meta/recipes-extended/grep/grep_3.6.bb
+++ b/meta/recipes-extended/grep/grep_3.7.bb
@@ -8,7 +8,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=1ebbd3e34237af26da5dc08a4e440464"
 
 SRC_URI = "${GNU_MIRROR}/grep/grep-${PV}.tar.xz"
 
-SRC_URI[sha256sum] = 
"667e15e8afe189e93f9f21a7cd3a7b3f776202f417330b248c2ad4f997d9373e"
+SRC_URI[sha256sum] = 
"5c10da312460aec721984d5d83246d24520ec438dd48d7ab5a05dbc0d6d6823c"
 
 inherit autotools gettext texinfo pkgconfig
 
-- 
2.7.4


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154893): 
https://lists.openembedded.org/g/openembedded-core/message/154893
Mute This Topic: https://lists.openembedded.org/mt/84953590/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 2/2] binutils: Apply upstream patch to fix 'too many open files' on qtwebengine

[Khem Raj]

On 8/17/21 7:32 AM, Andreas Müller wrote:

Since upgrade of binutils to 2.37 builds of qtwebengine failed to link even
with ulimits -n 100 (!!).
Fix that by applying a patch from stable 'binutils-2_37-branch'.




lgtm


Signed-off-by: Andreas Müller 
---
  .../binutils/binutils-2.37.inc|   1 +
  ...le-descriptor-if-there-is-no-archive.patch | 234 ++
  2 files changed, 235 insertions(+)
  create mode 100644 
meta/recipes-devtools/binutils/binutils/0017-bfd-Close-the-file-descriptor-if-there-is-no-archive.patch

diff --git a/meta/recipes-devtools/binutils/binutils-2.37.inc 
b/meta/recipes-devtools/binutils/binutils-2.37.inc
index 4218c0a616..6093558e4b 100644
--- a/meta/recipes-devtools/binutils/binutils-2.37.inc
+++ b/meta/recipes-devtools/binutils/binutils-2.37.inc
@@ -35,5 +35,6 @@ SRC_URI = "\
   file://0014-Fix-rpath-in-libtool-when-sysroot-is-enabled.patch \
   file://0015-sync-with-OE-libtool-changes.patch \
   file://0016-Check-for-clang-before-checking-gcc-version.patch \
+ file://0017-bfd-Close-the-file-descriptor-if-there-is-no-archive.patch \
  "
  S  = "${WORKDIR}/git"
diff --git 
a/meta/recipes-devtools/binutils/binutils/0017-bfd-Close-the-file-descriptor-if-there-is-no-archive.patch
 
b/meta/recipes-devtools/binutils/binutils/0017-bfd-Close-the-file-descriptor-if-there-is-no-archive.patch
new file mode 100644
index 00..9becee39a2
--- /dev/null
+++ 
b/meta/recipes-devtools/binutils/binutils/0017-bfd-Close-the-file-descriptor-if-there-is-no-archive.patch
@@ -0,0 +1,234 @@
+From 1c611b40e6bfc8029bff7696814330b5bc0ee5c0 Mon Sep 17 00:00:00 2001
+From: "H.J. Lu" 
+Date: Mon, 26 Jul 2021 05:59:55 -0700
+Subject: [PATCH] bfd: Close the file descriptor if there is no archive fd
+
+Close the file descriptor if there is no archive plugin file descriptor
+to avoid running out of file descriptors on thin archives with many
+archive members.
+
+bfd/
+
+   PR ld/28138
+   * plugin.c (bfd_plugin_close_file_descriptor): Close the file
+   descriptor there is no archive plugin file descriptor.
+
+ld/
+
+   PR ld/28138
+   * testsuite/ld-plugin/lto.exp: Run tmpdir/pr28138 only for
+   native build.
+
+   PR ld/28138
+   * testsuite/ld-plugin/lto.exp: Run ld/28138 tests.
+   * testsuite/ld-plugin/pr28138.c: New file.
+   * testsuite/ld-plugin/pr28138-1.c: Likewise.
+   * testsuite/ld-plugin/pr28138-2.c: Likewise.
+   * testsuite/ld-plugin/pr28138-3.c: Likewise.
+   * testsuite/ld-plugin/pr28138-4.c: Likewise.
+   * testsuite/ld-plugin/pr28138-5.c: Likewise.
+   * testsuite/ld-plugin/pr28138-6.c: Likewise.
+   * testsuite/ld-plugin/pr28138-7.c: Likewise.
+
+(cherry picked from commit 5a98fb7513b559e20dfebdbaa2a471afda3b4742)
+(cherry picked from commit 7dc37e1e1209c80e0bab784df6b6bac335e836f2)
+
+Upstream-Status: 
Accepted[https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=1c611b40e6bfc8029bff7696814330b5bc0ee5c0]
+---
+ bfd/plugin.c   |  8 +++
+ ld/testsuite/ld-plugin/lto.exp | 34 ++
+ ld/testsuite/ld-plugin/pr28138-1.c |  6 ++
+ ld/testsuite/ld-plugin/pr28138-2.c |  6 ++
+ ld/testsuite/ld-plugin/pr28138-3.c |  6 ++
+ ld/testsuite/ld-plugin/pr28138-4.c |  6 ++
+ ld/testsuite/ld-plugin/pr28138-5.c |  6 ++
+ ld/testsuite/ld-plugin/pr28138-6.c |  6 ++
+ ld/testsuite/ld-plugin/pr28138-7.c |  6 ++
+ ld/testsuite/ld-plugin/pr28138.c   | 20 ++
+ 10 files changed, 104 insertions(+)
+ create mode 100644 ld/testsuite/ld-plugin/pr28138-1.c
+ create mode 100644 ld/testsuite/ld-plugin/pr28138-2.c
+ create mode 100644 ld/testsuite/ld-plugin/pr28138-3.c
+ create mode 100644 ld/testsuite/ld-plugin/pr28138-4.c
+ create mode 100644 ld/testsuite/ld-plugin/pr28138-5.c
+ create mode 100644 ld/testsuite/ld-plugin/pr28138-6.c
+ create mode 100644 ld/testsuite/ld-plugin/pr28138-7.c
+ create mode 100644 ld/testsuite/ld-plugin/pr28138.c
+
+diff --git a/bfd/plugin.c b/bfd/plugin.c
+index 6cfa2b66470..3bab8febe88 100644
+--- a/bfd/plugin.c
 b/bfd/plugin.c
+@@ -291,6 +291,14 @@ bfd_plugin_close_file_descriptor (bfd *abfd, int fd)
+&& !bfd_is_thin_archive (abfd->my_archive))
+   abfd = abfd->my_archive;
+
++  /* Close the file descriptor if there is no archive plugin file
++   descriptor.  */
++  if (abfd->archive_plugin_fd == -1)
++  {
++close (fd);
++return;
++  }
++
+   abfd->archive_plugin_fd_open_count--;
+   /* Dup the archive plugin file descriptor for later use, which
+will be closed by _bfd_archive_close_and_cleanup.  */
+diff --git a/ld/testsuite/ld-plugin/lto.exp b/ld/testsuite/ld-plugin/lto.exp
+index def69e43ab3..999d911ce6a 100644
+--- a/ld/testsuite/ld-plugin/lto.exp
 b/ld/testsuite/ld-plugin/lto.exp
+@@ -687,6 +687,40 @@ if { [is_elf_format] && [check_lto_shared_available] } {
+ }
+ }
+
++run_cc_link_tests [list \

Re: [oe-core][PATCH 1/1] blktrace: change shebangs

[Joe Slater]

When I previously checked upstream, they explicitly left the "python" when they 
converted the scripts to work with python3 because the scripts work with 2 or 3.

Joe

> -Original Message-
> From: Richard Purdie 
> Sent: Monday, August 16, 2021 2:59 PM
> To: Alexander Kanavin ; Slater, Joseph
> 
> Cc: OE-core ; MacLeod, Randy
> 
> Subject: Re: [oe-core][PATCH 1/1] blktrace: change shebangs
> 
> On Mon, 2021-08-16 at 20:40 +0200, Alexander Kanavin wrote:
> > On Mon, 16 Aug 2021 at 20:20, Joe Slater  wrote:
> > > +blktrace can use either python2 or python3, but we really want
> > > +python3, so modify the shebangs.
> > > +
> > > +Upstream-Status: pending
> > > +
> > > +Signed-off-by: Joe Slater  > >
> >
> >
> > Please submit upstream first. Signed-off-by is incorrectly written,
> > needs to be added by git preferably. 'Pending' needs to be capitalized
> > (but please submit upstream first).
> 
> I very much doubt upstream will want to change "python" -> "python3" as it is 
> a
> distro thing. It is frustrating it isn't configurable. I think in most other 
> cases we
> sed this into scripts but that has pros and cons too rather than a patch we 
> have
> to carry...
> 
> Cheers,
> 
> Richard


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154891): 
https://lists.openembedded.org/g/openembedded-core/message/154891
Mute This Topic: https://lists.openembedded.org/mt/84930362/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 4/4] kernel-devsrc: fix 5.14+ objtool compilation

[Bruce Ashfield]

From: Bruce Ashfield 

In v5.14+, x86 requires not just elfutils, but the elf headers
on the target to build objtool (required for 'scripts parepare'),
so we tweak our RDEPENDS to ensure that the right headers are
on the target.

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/kernel-devsrc.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/linux/kernel-devsrc.bb 
b/meta/recipes-kernel/linux/kernel-devsrc.bb
index 23de1a4917..d39573965f 100644
--- a/meta/recipes-kernel/linux/kernel-devsrc.bb
+++ b/meta/recipes-kernel/linux/kernel-devsrc.bb
@@ -322,7 +322,7 @@ RDEPENDS:${PN} = "bc python3 flex bison ${TCLIBC}-utils"
 # 4.15+ needs these next two RDEPENDS
 RDEPENDS:${PN} += "openssl-dev util-linux"
 # and x86 needs a bit more for 4.15+
-RDEPENDS:${PN} += "${@bb.utils.contains('ARCH', 'x86', 'elfutils', '', d)}"
+RDEPENDS:${PN} += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-dev', '', d)}"
 # 5.8+ needs gcc-plugins libmpc-dev
 RDEPENDS:${PN} += "gcc-plugins libmpc-dev"
 # 5.13+ needs awk for arm64
-- 
2.19.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154890): 
https://lists.openembedded.org/g/openembedded-core/message/154890
Mute This Topic: https://lists.openembedded.org/mt/84950305/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 3/4] kernel-devsrc: 5.14+ updates

[Bruce Ashfield]

From: Bruce Ashfield 

commit 6218d0f6b8dec [x86/syscalls: Switch to generic syscalltbl.sh]
means that x86 no longer has a syscall script to copy, which causes
a build error.

We already copy the generic syscall script (in scripts), so we just
catch errors for the copies to support older and 5.14+ kernels in
the same devsrc recipe.

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/kernel-devsrc.bb | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta/recipes-kernel/linux/kernel-devsrc.bb 
b/meta/recipes-kernel/linux/kernel-devsrc.bb
index 3b5fdda773..23de1a4917 100644
--- a/meta/recipes-kernel/linux/kernel-devsrc.bb
+++ b/meta/recipes-kernel/linux/kernel-devsrc.bb
@@ -220,10 +220,10 @@ do_install() {
 
if [ "${ARCH}" = "x86" ]; then
# files for 'make prepare' to succeed with kernel-devel
-   cp -a --parents $(find arch/x86 -type f -name "syscall_32.tbl") 
$kerneldir/build/
-   cp -a --parents $(find arch/x86 -type f -name "syscalltbl.sh") 
$kerneldir/build/
-   cp -a --parents $(find arch/x86 -type f -name "syscallhdr.sh") 
$kerneldir/build/
-   cp -a --parents $(find arch/x86 -type f -name "syscall_64.tbl") 
$kerneldir/build/
+   cp -a --parents $(find arch/x86 -type f -name "syscall_32.tbl") 
$kerneldir/build/ 2>/dev/null || :
+   cp -a --parents $(find arch/x86 -type f -name "syscalltbl.sh") 
$kerneldir/build/ 2>/dev/null || :
+   cp -a --parents $(find arch/x86 -type f -name "syscallhdr.sh") 
$kerneldir/build/ 2>/dev/null || :
+   cp -a --parents $(find arch/x86 -type f -name "syscall_64.tbl") 
$kerneldir/build/ 2>/dev/null || :
cp -a --parents arch/x86/tools/relocs_32.c $kerneldir/build/
cp -a --parents arch/x86/tools/relocs_64.c $kerneldir/build/
cp -a --parents arch/x86/tools/relocs.c $kerneldir/build/
-- 
2.19.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154889): 
https://lists.openembedded.org/g/openembedded-core/message/154889
Mute This Topic: https://lists.openembedded.org/mt/84950304/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 2/4] lttng-modules: update to 2.13.0

[Bruce Ashfield]

From: Bruce Ashfield 

Updating to 2.13.0, so we can pick up the latest -stable and
support for 5.14+ kernels.

We refresh one patch for new context, and update the LICENSE
checksum due to commit 2df37e95fa4303 [Cleanup: Move headers from
toplevel to include/lttng/]. which impacted the LICENSE file (but
licensing is the same).

MODULES_MODULE_SYMVERS_LOCATION must also be specified in this
release, as the lttng build has moved the module target to a
'src' subdirectory.

Signed-off-by: Bruce Ashfield 
---
 ...fail-if-CONFIG_TRACEPOINTS-is-not-en.patch | 32 ++-
 ...ules_2.12.6.bb => lttng-modules_2.13.0.bb} |  6 ++--
 2 files changed, 14 insertions(+), 24 deletions(-)
 rename meta/recipes-kernel/lttng/{lttng-modules_2.12.6.bb => 
lttng-modules_2.13.0.bb} (88%)

diff --git 
a/meta/recipes-kernel/lttng/lttng-modules/Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch
 
b/meta/recipes-kernel/lttng/lttng-modules/Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch
index e411242272..a852834344 100644
--- 
a/meta/recipes-kernel/lttng/lttng-modules/Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch
+++ 
b/meta/recipes-kernel/lttng/lttng-modules/Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch
@@ -13,37 +13,25 @@ available, allowing it to be kept being pulled by default.
 Upstream-Status: Inappropriate [embedded specific]
 
 Signed-off-by: Otavio Salvador 
+[bva: modified for lttng-modules 2.13+ context]
+Signed-off-by: Bruce Ashfield 
 ---
  Makefile | 9 +
  1 file changed, 5 insertions(+), 4 deletions(-)
 
-diff --git a/Makefile b/Makefile
-index 8602649..75550cc 100644
 a/Makefile
-+++ b/Makefile
-@@ -8,10 +8,7 @@ ifneq ($(KERNELRELEASE),)
-   # and defines the modules to be built.
+Index: lttng-modules-2.13.0/Makefile
+===
+--- lttng-modules-2.13.0.orig/Makefile
 lttng-modules-2.13.0/Makefile
+@@ -7,6 +7,11 @@
  
-   ifdef CONFIG_LOCALVERSION   # Check if dot-config is included.
--ifeq ($(CONFIG_TRACEPOINTS),)
--  $(error The option CONFIG_TRACEPOINTS needs to be enabled in your 
kernel configuration)
--endif # CONFIG_TRACEPOINTS
--  endif # ifdef CONFIG_LOCALVERSION
-+ifneq ($(CONFIG_TRACEPOINTS),)
- 
-   TOP_LTTNG_MODULES_DIR := $(shell dirname $(lastword $(MAKEFILE_LIST)))
- 
-@@ -94,6 +91,10 @@ ifneq ($(KERNELRELEASE),)
-   obj-$(CONFIG_LTTNG) += lib/
-   obj-$(CONFIG_LTTNG) += tests/
+ obj-$(CONFIG_LTTNG) += src/
  
-+else
++  ifdef CONFIG_LOCALVERSION   # Check if dot-config is included.
++ifneq ($(CONFIG_TRACEPOINTS),)
 +  $(warning The option CONFIG_TRACEPOINTS needs to be enabled in your 
kernel configuration)
 +endif # CONFIG_TRACEPOINTS
 +  endif # ifdef CONFIG_LOCALVERSION
  else # KERNELRELEASE
  
  # This part of the Makefile is used when the 'make' command is runned in the
--- 
-2.1.4
-
diff --git a/meta/recipes-kernel/lttng/lttng-modules_2.12.6.bb 
b/meta/recipes-kernel/lttng/lttng-modules_2.13.0.bb
similarity index 88%
rename from meta/recipes-kernel/lttng/lttng-modules_2.12.6.bb
rename to meta/recipes-kernel/lttng/lttng-modules_2.13.0.bb
index c46faaee58..b95d7ecaaf 100644
--- a/meta/recipes-kernel/lttng/lttng-modules_2.12.6.bb
+++ b/meta/recipes-kernel/lttng/lttng-modules_2.13.0.bb
@@ -3,7 +3,7 @@ SUMMARY = "Linux Trace Toolkit KERNEL MODULE"
 DESCRIPTION = "The lttng-modules 2.0 package contains the kernel tracer 
modules"
 HOMEPAGE = "https://lttng.org/;
 LICENSE = "LGPLv2.1 & GPLv2 & MIT"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=3f882d431dc0f32f1f44c0707aa41128"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=0464cff101a009c403cd2ed65d01d4c4"
 
 inherit module
 
@@ -13,12 +13,14 @@ SRC_URI = 
"https://lttng.org/files/${BPN}/${BPN}-${PV}.tar.bz2 \
file://Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch \
"
 
-SRC_URI[sha256sum] = 
"95ac2a2cf92d85d23ffbdaca6a1ec0d7c167211d1e0fb850ab90004a3f475eaa"
+SRC_URI[sha256sum] = 
"5ebf2b3cd128b3a1c8afaea1e98d5a6f7f0676fd524fcf72361c34d9dc603356"
 
 export INSTALL_MOD_DIR="kernel/lttng-modules"
 
 EXTRA_OEMAKE += "KERNELDIR='${STAGING_KERNEL_DIR}'"
 
+MODULES_MODULE_SYMVERS_LOCATION = "src"
+
 do_install:append() {
# Delete empty directories to avoid QA failures if no modules were built
find ${D}/${nonarch_base_libdir} -depth -type d -empty -exec rmdir {} \;
-- 
2.19.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154888): 
https://lists.openembedded.org/g/openembedded-core/message/154888
Mute This Topic: https://lists.openembedded.org/mt/84950303/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 0/4] linux-yocto-dev: dev and supporting recipes updates

[Bruce Ashfield]

From: Bruce Ashfield 

Richard,

Continuing on the kenrel update path, I've built, booted and run
core-image-kernel-dev on all the supported architectures for v5.14-rcX.

I've pushed the kernel changes, and here are the supporting updaes.
lttng-modules is of course involved, and on that front rather than
backporting patches ot the 2.12.x series, I've moved it to 2.13 (the
latest release), since that will give us better support and more
forward compatibility.

Cheers,

Bruce

The following changes since commit bc65a37ef50faba339fb54d6a89ef9da0298bbbe:

  package: Fix overrides converion issue with PKGSIZE (2021-08-17 09:53:04 
+0100)

are available in the Git repository at:

  git://git.yoctoproject.org/poky-contrib zedd/kernel-dev
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-dev

Bruce Ashfield (4):
  linux-yocto-dev: bump to v5.14+
  lttng-modules: update to 2.13.0
  kernel-devsrc: 5.14+ updates
  kernel-devsrc: fix 5.14+ objtool compilation

 meta/recipes-kernel/linux/kernel-devsrc.bb| 10 +++---
 meta/recipes-kernel/linux/linux-yocto-dev.bb  |  2 +-
 ...fail-if-CONFIG_TRACEPOINTS-is-not-en.patch | 32 ++-
 ...ules_2.12.6.bb => lttng-modules_2.13.0.bb} |  6 ++--
 4 files changed, 20 insertions(+), 30 deletions(-)
 rename meta/recipes-kernel/lttng/{lttng-modules_2.12.6.bb => 
lttng-modules_2.13.0.bb} (88%)

-- 
2.19.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154886): 
https://lists.openembedded.org/g/openembedded-core/message/154886
Mute This Topic: https://lists.openembedded.org/mt/84950300/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 1/4] linux-yocto-dev: bump to v5.14+

[Bruce Ashfield]

From: Bruce Ashfield 

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb 
b/meta/recipes-kernel/linux/linux-yocto-dev.bb
index 28a255a0c0..0911787009 100644
--- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
@@ -30,7 +30,7 @@ SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-dev.git;branch=${KBRANCH};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 ?= "5.13+"
+LINUX_VERSION ?= "5.14+"
 LINUX_VERSION_EXTENSION ?= "-yoctodev-${LINUX_KERNEL_TYPE}"
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
-- 
2.19.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154887): 
https://lists.openembedded.org/g/openembedded-core/message/154887
Mute This Topic: https://lists.openembedded.org/mt/84950301/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] glibc: Fix CVE-2021-33574

[Vinay Kumar]

Hi Ernst,

Thanks, for the update of CVE-2021-38604.
Will send a path to the hardknott branch as well as master branch.

Regards,
Vinay

On Tue, Aug 17, 2021 at 12:10 PM Ernst Sjöstrand  wrote:
>
> There is now an additional fix on top of this:
>
> https://it.slashdot.org/story/21/08/16/2131221/linux-glibc-security-fix-created-a-nastier-linux-bug
>
> https://access.redhat.com/security/cve/cve-2021-38604
>
> //E
>
> Den mån 2 aug. 2021 kl 06:14 skrev Vinay Kumar :
>>
>> Hi Anuj,
>>
>> >> It seems wrong to me because the patch header/description is not
>> >> correct here. It's no longer a backport of just
>> >> 42d359350510506b87101cf77202fefcbfc790cb.
>>
>> Yes, I merged 2 commits first
>> (42d359350510506b87101cf77202fefcbfc790cb and
>> 217b6dc298156bdb0d6aea9ea93e7e394a5ff091)
>> and then backported as a single patch, and I used only the patch
>> header of 42d359350510506b87101cf77202fefcbfc790cb.
>>
>> >> I also just noticed that there's already a fix for this CVE in my
>> >> branch. So I think I will take that:
>>
>> Ok, thanks. Will go with this once it gets merged to the "hardknott" branch.
>>
>> Regards,
>> Vinay
>>
>> On Mon, Aug 2, 2021 at 8:09 AM Mittal, Anuj  wrote:
>> >
>> > On Sat, 2021-07-31 at 21:57 +0530, Vinay Kumar wrote:
>> > > Hi Anuj,
>> > >
>> > > The patch is conjugate of both commits.
>> > > https://sourceware.org/git/?p=glibc.git;a=commit;h=42d359350510506b87101cf77202fefcbfc790cb
>> > >
>> > > https://sourceware.org/git/?p=glibc.git;a=commit;h=217b6dc298156bdb0d6aea9ea93e7e394a5ff091
>> > >
>> > > Also, the patch is committed to master branch
>> > > http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=55681d09d7f519a1c7f17d17b18ec59bccdc91ca
>> > >
>> > > Due you want me to resubmit for "hardknott" branch by splitting in to
>> > > 2 patches ?
>> >
>> > It seems wrong to me because the patch header/description is not
>> > correct here. It's no longer a backport of just
>> > 42d359350510506b87101cf77202fefcbfc790cb.
>> >
>> > I also just noticed that there's already a fix for this CVE in my
>> > branch. So I think I will take that:
>> >
>> > https://git.openembedded.org/openembedded-core-contrib/commit/?h=anujm/hardknott=ede353df06a07d35dc66d024e2c7bd1b250d9761
>> >
>> > Thanks,
>> >
>> > Anuj
>> >
>> > >
>> > > Regards,
>> > > Vinay
>> > >
>> > > On Sat, Jul 31, 2021 at 11:52 AM Mittal, Anuj 
>> > > wrote:
>> > > >
>> > > > On Tue, 2021-07-27 at 11:38 -0700, Vinay Kumar wrote:
>> > > > > Source: https://sourceware.org/git/glibc.git
>> > > > > Tracking -- https://sourceware.org/bugzilla/show_bug.cgi?id=27896
>> > > > >
>> > > > > Backported upstream commit 42d359350510506b87101cf77202fefcbfc790cb
>> > > > > to
>> > > > > glibc-2.33 source with dependent commit id
>> > > > > 217b6dc298156bdb0d6aea9ea93e7e394a5ff091.
>> > > > >
>> > > > > Upstream-Status: Backport
>> > > > > [
>> > > > > https://sourceware.org/git/?p=glibc.git;a=commit;h=42d359350510506b87101cf77202fefcbfc790cb
>> > > > > ]
>> > > >
>> > > > It looks like you'd need to backport this one too:
>> > > >
>> > > > https://sourceware.org/git/?p=glibc.git;a=commit;h=217b6dc298156bdb0d6aea9ea93e7e394a5ff091
>> > > >
>> > > > ?
>> > > >
>> > > > Thanks,
>> > > >
>> > > > Anuj
>> > > >
>> > > > >
>> > > > > Signed-off-by: Vinay Kumar 
>> > > > > ---
>> > > > >  .../glibc/glibc/CVE-2021-33574.patch  | 61
>> > > > > +++
>> > > > >  meta/recipes-core/glibc/glibc_2.33.bb |  1 +
>> > > > >  2 files changed, 62 insertions(+)
>> > > > >  create mode 100644 meta/recipes-core/glibc/glibc/CVE-2021-
>> > > > > 33574.patch
>> > > > >
>> > > > > diff --git a/meta/recipes-core/glibc/glibc/CVE-2021-33574.patch
>> > > > > b/meta/recipes-core/glibc/glibc/CVE-2021-33574.patch
>> > > > > new file mode 100644
>> > > > > index 00..fd73b23c88
>> > > > > --- /dev/null
>> > > > > +++ b/meta/recipes-core/glibc/glibc/CVE-2021-33574.patch
>> > > > > @@ -0,0 +1,61 @@
>> > > > > +From 42d359350510506b87101cf77202fefcbfc790cb Mon Sep 17 00:00:00
>> > > > > 2001
>> > > > > +From: Andreas Schwab 
>> > > > > +Date: Thu, 27 May 2021 12:49:47 +0200
>> > > > > +Subject: [PATCH] Use __pthread_attr_copy in mq_notify (bug 27896)
>> > > > > +
>> > > > > +Make a deep copy of the pthread attribute object to remove a
>> > > > > potential
>> > > > > +use-after-free issue.
>> > > > > +
>> > > > > +Upstream-Status: Backport
>> > > > > [
>> > > > > https://sourceware.org/git/?p=glibc.git;a=commit;h=42d359350510506b87101cf77202fefcbfc790cb
>> > > > > ]
>> > > > > +CVE: CVE-2021-33574
>> > > > > +Signed-off-by: Vinay Kumar 
>> > > > > +---
>> > > > > +diff --git a/sysdeps/unix/sysv/linux/mq_notify.c
>> > > > > b/sysdeps/unix/sysv/linux/mq_notify.c
>> > > > > +index cc575a0cdd8..6f46d29d1dc 100644
>> > > > > +--- a/sysdeps/unix/sysv/linux/mq_notify.c
>> > > > >  b/sysdeps/unix/sysv/linux/mq_notify.c
>> > > > > +@@ -133,8 +133,11 @@ helper_thread (void *arg)
>> > > > > +   (void) __pthread_barrier_wait (_barrier);
>> > > 

Re: [OE-core] [poky][dunfell][PATCH] python3: Remove unused python3 recipe

[Steve Sakoman]

On Tue, Aug 17, 2021 at 5:09 AM Khem Raj  wrote:
>
> On Tue, Aug 17, 2021 at 8:00 AM Martin Jansa  wrote:
> >
> > On Tue, Aug 17, 2021 at 4:52 PM Steve Sakoman  wrote:
> >>
> >> On Mon, Aug 9, 2021 at 9:08 PM Purushottam choudhary
> >>  wrote:
> >> >
> >> > Currently in dunfell branch python3 version is 3.8.11.
> >> > so, python3_3.8.10.bb is not needed.
> >> > Hence, removed.
> >>
> >> I don't feel good about removing a recipe from a stable release.
> >> There may be people who are using 3.8.10 for whatever reason and
> >> removing the recipe would break their builds.
> >
> >
> > IMHO removing 3.8.10 is correct in this case, normally the upgrade to 
> > 3.8.11 from:
> > https://git.openembedded.org/openembedded-core/commit/?h=dunfell=1ba51ee2d52ee92bbdede9f2cd2f9ed9ff04ddb6
> > would remove the older version like the upgrade to 3.8.10 did couple days 
> > before:
> > https://git.openembedded.org/openembedded-core/commit/?h=dunfell=471d19fa70c4c2b43a039909c9538e2223996335
> >
> > 3.8.10 recipe existed in dunfell only for about 2,5 weeks (and probably 
> > only by accident it wasn't removed with 3.8.11 upgrade), if someone started 
> > to depend on this exact version for whatever reason, then something is 
> > wrong with him or her :).
> >
>
> right. 3.8.11 is a bugfix release so keeping 3.8.10 around will also
> mean CVEs we will carry with 3.8.10

OK, say goodbye to 3.8.10 :-)

Steve

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154884): 
https://lists.openembedded.org/g/openembedded-core/message/154884
Mute This Topic: https://lists.openembedded.org/mt/84788234/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [poky][dunfell][PATCH] python3: Remove unused python3 recipe

[Khem Raj]

On Tue, Aug 17, 2021 at 8:00 AM Martin Jansa  wrote:
>
> On Tue, Aug 17, 2021 at 4:52 PM Steve Sakoman  wrote:
>>
>> On Mon, Aug 9, 2021 at 9:08 PM Purushottam choudhary
>>  wrote:
>> >
>> > Currently in dunfell branch python3 version is 3.8.11.
>> > so, python3_3.8.10.bb is not needed.
>> > Hence, removed.
>>
>> I don't feel good about removing a recipe from a stable release.
>> There may be people who are using 3.8.10 for whatever reason and
>> removing the recipe would break their builds.
>
>
> IMHO removing 3.8.10 is correct in this case, normally the upgrade to 3.8.11 
> from:
> https://git.openembedded.org/openembedded-core/commit/?h=dunfell=1ba51ee2d52ee92bbdede9f2cd2f9ed9ff04ddb6
> would remove the older version like the upgrade to 3.8.10 did couple days 
> before:
> https://git.openembedded.org/openembedded-core/commit/?h=dunfell=471d19fa70c4c2b43a039909c9538e2223996335
>
> 3.8.10 recipe existed in dunfell only for about 2,5 weeks (and probably only 
> by accident it wasn't removed with 3.8.11 upgrade), if someone started to 
> depend on this exact version for whatever reason, then something is wrong 
> with him or her :).
>

right. 3.8.11 is a bugfix release so keeping 3.8.10 around will also
mean CVEs we will carry with 3.8.10
> Regards,
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154883): 
https://lists.openembedded.org/g/openembedded-core/message/154883
Mute This Topic: https://lists.openembedded.org/mt/84788234/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [poky][dunfell][PATCH] python3: Remove unused python3 recipe

[Martin Jansa]

On Tue, Aug 17, 2021 at 4:52 PM Steve Sakoman  wrote:

> On Mon, Aug 9, 2021 at 9:08 PM Purushottam choudhary
>  wrote:
> >
> > Currently in dunfell branch python3 version is 3.8.11.
> > so, python3_3.8.10.bb is not needed.
> > Hence, removed.
>
> I don't feel good about removing a recipe from a stable release.
> There may be people who are using 3.8.10 for whatever reason and
> removing the recipe would break their builds.
>

IMHO removing 3.8.10 is correct in this case, normally the upgrade to
3.8.11 from:
https://git.openembedded.org/openembedded-core/commit/?h=dunfell=1ba51ee2d52ee92bbdede9f2cd2f9ed9ff04ddb6
would remove the older version like the upgrade to 3.8.10 did couple days
before:
https://git.openembedded.org/openembedded-core/commit/?h=dunfell=471d19fa70c4c2b43a039909c9538e2223996335

3.8.10 recipe existed in dunfell only for about 2,5 weeks (and probably
only by accident it wasn't removed with 3.8.11 upgrade), if someone started
to depend on this exact version for whatever reason, then something is
wrong with him or her :).

Regards,

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154882): 
https://lists.openembedded.org/g/openembedded-core/message/154882
Mute This Topic: https://lists.openembedded.org/mt/84788234/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [v4] [RFC] Merge meta-rust to oe-core

[Randy MacLeod]

On 2021-08-13 11:22 a.m., Vinay Kumar wrote:

Hi Randy,


Vinay or I will look into glibc/qemuppc64
if no one else is working on that.


The failure is due to the below error in libstd-rs package build.
"error: unrecognized arch "powerpc64le" in target specification"

The reason for this is "arch": "powerpc64le" from the below target
specific file.

cat 
$b2/tmp/work/ppc64p9le-poky-linux/libstd-rs/1.54.0-r0/recipe-sysroot-native/usr/lib/rustlib/powerpc64le-poky-linux.json
{
 "llvm-target": "powerpc64le-unknown-linux-gnu",
 "data-layout": "e-m:e-i64:64-n32:64-v256:256:256-v512:512:512",
 "max-atomic-width": 64,
 "target-pointer-width": "64",
 "target-c-int-width": "64",
 "target-endian": "little",
 "arch": "powerpc64le",
 "os": "linux",
 "env": "gnu",
 "vendor": "unknown",
 "target-family": "unix",
 "linker": "powerpc64le-poky-linux-gcc",
 "ar": "powerpc64le-poky-linux-ar",
 "cpu": "generic",
 "dynamic-linking": true,
 "executables": true,
 "linker-is-gnu": true,
 "linker-flavor": "gcc",
 "has-rpath": true,
 "has-elf-tls": true,
 "position-independent-executables": true,
 "panic-strategy": "unwind"
}

So the "arch" should be "powerpc64" in case of "powerpc64le" fixes the
librstd-rs build failure.

With the above fix,

$cat  rust-hello-world-buildall.log
BUILDALL-QEMU LOG FOR rust-hello-world
START TIME: 2021-08-13_03:11:23
HOSTNAME: ala-lpggp3
HOST OS: Ubuntu 18.04.3 LTS
HOST KERNEL: 5.4.0-80-generic
===
BUILD RESULTS:
[glibc]
PASS: qemuriscv32
PASS: qemuarmv5
PASS: qemumips
PASS: qemux86-64
PASS: qemuarm64
PASS: qemumips64
PASS: qemuarm
PASS: qemuppc
PASS: qemuriscv64
PASS: qemuppc64
PASS: qemux86
[musl]
FAIL: qemuriscv32
FAIL: qemuarmv5
FAIL: qemumips
FAIL: qemux86-64
FAIL: qemuarm64
FAIL: qemumips64
FAIL: qemuarm
FAIL: qemuppc
FAIL: qemuriscv64
FAIL: qemuppc64
FAIL: qemux86
===
PASSED: 11
FAILED: 11

Regards,
Vinay


Thanks Vinay, applied.

I'll push a new branch to poky-contrib later today.

../Randy


On Fri, Aug 13, 2021 at 8:50 PM Vinay Kumar  wrote:


rust-common.inc: Fix build failure with qemuppc64.

The glibc build of "rust-hello-world" throws error in libstd-rs package.
error: unrecognized arch "powerpc64le" in target specification

The same got fixed by changing the arch to "powerpc64".

Signed-off-by: Vinay Kumar 
---
  meta/recipes-devtools/rust/rust-common.inc | 2 ++
  1 file changed, 2 insertions(+)

diff --git a/meta/recipes-devtools/rust/rust-common.inc 
b/meta/recipes-devtools/rust/rust-common.inc
index 350517c723..f574152815 100644
--- a/meta/recipes-devtools/rust/rust-common.inc
+++ b/meta/recipes-devtools/rust/rust-common.inc
@@ -248,6 +248,8 @@ def arch_to_rust_target_arch(arch):
  return "mips64"
  elif arch == "armv7":
  return "arm"
+elif arch == "powerpc64le":
+return "powerpc64"
  else:
  return arch

--
2.31.1




--
# Randy MacLeod
# Wind River Linux

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154881): 
https://lists.openembedded.org/g/openembedded-core/message/154881
Mute This Topic: https://lists.openembedded.org/mt/84865833/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [poky][dunfell][PATCH] python3: Remove unused python3 recipe

[Steve Sakoman]

On Mon, Aug 9, 2021 at 9:08 PM Purushottam choudhary
 wrote:
>
> Currently in dunfell branch python3 version is 3.8.11.
> so, python3_3.8.10.bb is not needed.
> Hence, removed.

I don't feel good about removing a recipe from a stable release.
There may be people who are using 3.8.10 for whatever reason and
removing the recipe would break their builds.

Steve

> ---
>  meta/recipes-devtools/python/python3_3.8.10.bb | 363 
> -
>  1 file changed, 363 deletions(-)
>  delete mode 100644 meta/recipes-devtools/python/python3_3.8.10.bb
>
> diff --git a/meta/recipes-devtools/python/python3_3.8.10.bb 
> b/meta/recipes-devtools/python/python3_3.8.10.bb
> deleted file mode 100644
> index 7295c63..000
> --- a/meta/recipes-devtools/python/python3_3.8.10.bb
> +++ /dev/null
> @@ -1,363 +0,0 @@
> -SUMMARY = "The Python Programming Language"
> -HOMEPAGE = "http://www.python.org;
> -DESCRIPTION = "Python is a programming language that lets you work more 
> quickly and integrate your systems more effectively."
> -LICENSE = "PSF-2.0 & BSD-0-Clause"
> -SECTION = "devel/python"
> -
> -LIC_FILES_CHKSUM = "file://LICENSE;md5=c22d2438294c784731bf9dd224a467b7"
> -
> -SRC_URI = "http://www.python.org/ftp/python/${PV}/Python-${PV}.tar.xz \
> -   file://run-ptest \
> -   file://create_manifest3.py \
> -   file://get_module_deps3.py \
> -   file://python3-manifest.json \
> -   file://check_build_completeness.py \
> -   file://cgi_py.patch \
> -   
> file://0001-Do-not-add-usr-lib-termcap-to-linker-flags-to-avoid-.patch \
> -   ${@bb.utils.contains('PACKAGECONFIG', 'tk', '', 
> 'file://avoid_warning_about_tkinter.patch', d)} \
> -   
> file://0001-Do-not-use-the-shell-version-of-python-config-that-w.patch \
> -   file://python-config.patch \
> -   
> file://0001-Makefile.pre-use-qemu-wrapper-when-gathering-profile.patch \
> -   
> file://0001-Do-not-hardcode-lib-as-location-for-site-packages-an.patch \
> -   
> file://0001-python3-use-cc_basename-to-replace-CC-for-checking-c.patch \
> -   
> file://0001-Lib-sysconfig.py-fix-another-place-where-lib-is-hard.patch \
> -   
> file://0001-Makefile-fix-Issue36464-parallel-build-race-problem.patch \
> -   
> file://0001-bpo-36852-proper-detection-of-mips-architecture-for-.patch \
> -   file://crosspythonpath.patch \
> -   file://reformat_sysconfig.py \
> -   file://0001-Use-FLAG_REF-always-for-interned-strings.patch \
> -   file://0001-test_locale.py-correct-the-test-output-format.patch \
> -   
> file://0017-setup.py-do-not-report-missing-dependencies-for-disa.patch \
> -   
> file://0001-setup.py-pass-missing-libraries-to-Extension-for-mul.patch \
> -   file://0001-Makefile-do-not-compile-.pyc-in-parallel.patch \
> -   file://0001-configure.ac-fix-LIBPL.patch \
> -   file://0001-python3-Do-not-hardcode-lib-for-distutils.patch \
> -   
> file://0020-configure.ac-setup.py-do-not-add-a-curses-include-pa.patch \
> -   file://0001-test_ctypes.test_find-skip-without-tools-sdk.patch \
> -   "
> -
> -SRC_URI_append_class-native = " \
> -   
> file://0001-distutils-sysconfig-append-STAGING_LIBDIR-python-sys.patch \
> -   file://12-distutils-prefix-is-inside-staging-area.patch \
> -   file://0001-Don-t-search-system-for-headers-libraries.patch \
> -   "
> -
> -SRC_URI[md5sum] = "d9eee4b2013830a2025e4dcaa7b3"
> -SRC_URI[sha256sum] = 
> "6af24a66093dd840bcccf371d4044a3027e655cf24591ce26e48022bc79219d9"
> -
> -# exclude pre-releases for both python 2.x and 3.x
> -UPSTREAM_CHECK_REGEX = "[Pp]ython-(?P\d+(\.\d+)+).tar"
> -
> -CVE_PRODUCT = "python"
> -
> -# Upstream consider this expected behaviour
> -CVE_CHECK_WHITELIST += "CVE-2007-4559"
> -# This is not exploitable when glibc has CVE-2016-10739 fixed.
> -CVE_CHECK_WHITELIST += "CVE-2019-18348"
> -
> -# This is windows only issue.
> -CVE_CHECK_WHITELIST += "CVE-2020-15523"
> -
> -PYTHON_MAJMIN = "3.8"
> -
> -S = "${WORKDIR}/Python-${PV}"
> -
> -BBCLASSEXTEND = "native nativesdk"
> -
> -inherit autotools pkgconfig qemu ptest multilib_header update-alternatives
> -
> -MULTILIB_SUFFIX = "${@d.getVar('base_libdir',1).split('/')[-1]}"
> -
> -ALTERNATIVE_${PN}-dev = "python3-config"
> -ALTERNATIVE_LINK_NAME[python3-config] = 
> "${bindir}/python${PYTHON_MAJMIN}-config"
> -ALTERNATIVE_TARGET[python3-config] = 
> "${bindir}/python${PYTHON_MAJMIN}-config-${MULTILIB_SUFFIX}"
> -
> -
> -DEPENDS = "bzip2-replacement-native libffi bzip2 openssl sqlite3 zlib 
> virtual/libintl xz virtual/crypt util-linux libtirpc libnsl2 autoconf-archive"
> -DEPENDS_append_class-target = " python3-native"
> -DEPENDS_append_class-nativesdk = " python3-native"
> -
> -EXTRA_OECONF = " --without-ensurepip --enable-shared"
> -EXTRA_OECONF_append_class-native = " --bindir=${bindir}/${PN}"
> -
> -export 
> 

Re: [OE-core] [poky][dunfell][PATCH] lighttpd: Add patch for reuse large memory chunks

[Steve Sakoman]

On Thu, Aug 12, 2021 at 9:56 PM Purushottam choudhary
 wrote:
>
> Added 0001-core-reuse-large-mem-chunks-fix-mem-usage-fixes-3033.patch
> to fix large memory usage for large file downloads
> from dynamic backends reuse or release large memory chunks.
>
> This issue is caused by a bug in the lighttpd 1.4.55 version and
> has been fixed in lighttpd 1.4.58. Hence, it is not needed for
> master and hardknott branch because lighttpd has 1.4.59 version.
>
> Link: 
> https://redmine.lighttpd.net/projects/lighttpd/repository/14/revisions/7ba521ffb4959f6f74a609d5d4acafc29a038337
>
> Signed-off-by: Purushottam Choudhary 

This patch still does not apply:

Applying: lighttpd: Add patch for reuse large memory chunks
Using index info to reconstruct a base tree...
error: patch failed:
meta/recipes-extended/lighttpd/lighttpd/0001-Use-pkg-config-for-pcre-dependency-instead-of-config.patch:6
error: 
meta/recipes-extended/lighttpd/lighttpd/0001-Use-pkg-config-for-pcre-dependency-instead-of-config.patch:
patch does not apply
error: Did you hand edit your patch?
It does not apply to blobs recorded in its index.
Patch failed at 0001 lighttpd: Add patch for reuse large memory chunks

I'm not sure why you are making what appear to be cosmetic changes to
an existing patch file, but that seems to be what is causing the
error.

Steve

> ---
>  ...fig-for-pcre-dependency-instead-of-config.patch |  10 +-
>  ...large-mem-chunks-fix-mem-usage-fixes-3033.patch | 224 
> +
>  meta/recipes-extended/lighttpd/lighttpd_1.4.55.bb  |   1 +
>  3 files changed, 229 insertions(+), 6 deletions(-)
>  create mode 100644 
> meta/recipes-extended/lighttpd/lighttpd/0001-core-reuse-large-mem-chunks-fix-mem-usage-fixes-3033.patch
>
> diff --git 
> a/meta/recipes-extended/lighttpd/lighttpd/0001-Use-pkg-config-for-pcre-dependency-instead-of-config.patch
>  
> b/meta/recipes-extended/lighttpd/lighttpd/0001-Use-pkg-config-for-pcre-dependency-instead-of-config.patch
> index f17bdce..0b27bcc 100644
> --- 
> a/meta/recipes-extended/lighttpd/lighttpd/0001-Use-pkg-config-for-pcre-dependency-instead-of-config.patch
> +++ 
> b/meta/recipes-extended/lighttpd/lighttpd/0001-Use-pkg-config-for-pcre-dependency-instead-of-config.patch
> @@ -1,4 +1,4 @@
> -From 22afc5d9aaa215c3c87ba21c77d47da44ab3b113 Mon Sep 17 00:00:00 2001
> +From 43e22184eede7ee1b29baf3479ce99e953498570 Mon Sep 17 00:00:00 2001
>  From: Alexander Kanavin 
>  Date: Fri, 26 Aug 2016 18:20:32 +0300
>  Subject: [PATCH] Use pkg-config for pcre dependency instead of -config 
> script.
> @@ -6,15 +6,16 @@ Subject: [PATCH] Use pkg-config for pcre dependency instead 
> of -config script.
>  RP 2014/5/22
>  Upstream-Status: Pending
>  Signed-off-by: Alexander Kanavin 
> +
>  ---
>   configure.ac | 16 
>   1 file changed, 12 insertions(+), 4 deletions(-)
>
>  diff --git a/configure.ac b/configure.ac
> -index 5383cec..c29a902 100644
> +index dbddfb9..62cf17f 100644
>  --- a/configure.ac
>  +++ b/configure.ac
> -@@ -651,10 +651,18 @@ AC_ARG_WITH([pcre],
> +@@ -748,10 +748,18 @@ AC_ARG_WITH([pcre],
>   )
>   AC_MSG_RESULT([$WITH_PCRE])
>
> @@ -37,6 +38,3 @@ index 5383cec..c29a902 100644
> else
>   AC_PATH_PROG([PCRECONFIG], [pcre-config])
>   if test -n "$PCRECONFIG"; then
> ---
> -2.15.0
> -
> diff --git 
> a/meta/recipes-extended/lighttpd/lighttpd/0001-core-reuse-large-mem-chunks-fix-mem-usage-fixes-3033.patch
>  
> b/meta/recipes-extended/lighttpd/lighttpd/0001-core-reuse-large-mem-chunks-fix-mem-usage-fixes-3033.patch
> new file mode 100644
> index 000..777ee40
> --- /dev/null
> +++ 
> b/meta/recipes-extended/lighttpd/lighttpd/0001-core-reuse-large-mem-chunks-fix-mem-usage-fixes-3033.patch
> @@ -0,0 +1,224 @@
> +From 8caa841f2e039ab93a8b63b6dadd1ad1b240384a Mon Sep 17 00:00:00 2001
> +From: Glenn Strauss 
> +Date: Wed, 23 Dec 2020 23:14:47 -0500
> +Subject: [PATCH] reuse large mem chunks (fix mem usage) (fixes #3033)
> +
> +(cherry picked from commit 7ba521ffb4959f6f74a609d5d4acafc29a038337)
> +
> +(thx flynn)
> +
> +fix large memory usage for large file downloads from dynamic backends
> +
> +reuse or release large memory chunks
> +
> +x-ref:
> +  "Memory Growth with PUT and full buffered streams"
> +  https://redmine.lighttpd.net/issues/3033
> +
> +Upstream-Status: Backport
> +Comment: No hunk refreshed
> +https://redmine.lighttpd.net/projects/lighttpd/repository/14/revisions/7ba521ffb4959f6f74a609d5d4acafc29a038337
> +Signed-off-by: Purushottam Choudhary 
> +
> +---
> + src/chunk.c| 99 
> --
> + src/chunk.h|  2 +
> + src/http-header-glue.c |  2 +-
> + 3 files changed, 82 insertions(+), 21 deletions(-)
> +
> +diff --git a/src/chunk.c b/src/chunk.c
> +index 09dd3f1..ffb3795 100644
> +--- a/src/chunk.c
>  b/src/chunk.c
> +@@ -28,16 +28,20 @@
> + static size_t chunk_buf_sz = 4096;
> + static chunk *chunks, *chunks_oversized;
> + static chunk *chunk_buffers;
> ++static int 

[OE-core] Yocto Project Status WW33`21

[Stephen Jolley]

Current Dev Position: YP 3.4 M3

Next Deadline: 23rd Aug. 2021 YP 3.4 M3 build (Feature Freeze)

 

Next Team Meetings:

*   Bug Triage meeting Thursday Aug. 19th at 7:30am PDT (

https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*   Monthly Project Meeting Tuesday Sept. 7th at 8am PDT (

https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
 )
*   Weekly Engineering Sync Tuesday Aug. 17th at 8am PDT (

https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
 )
*   Twitch -  See https://www.twitch.tv/theyoctojester

 

Key Status/Updates:

*   YP 3.1.10 was released
*   Next week is feature freeze for YP 3.4
*   Known pending work for YP 3.4 includes rust support in core and the
prserv changes.
*   OE-Core has moved to the new override syntax and is now only
compatible with the honister release series. Other layers will need to
migrate to the new syntax to work with it. There is documentation about
handling migration to the new syntax in the migration section of the manual:

 

http://docs.yoctoproject.org/migration-guides/migration-3.4.html#override-sy
ntax-changes

*   There continue to be small bug fixes from the override syntax change
but most of the core layers tested on the autobuilder now seem to be working
ok.
*   We merged the upgrade to glibc to 2.34. Unfortunately this version
makes some changes which have broken uninative and pseudo. Fixes for those
issues are being investigated. 
*   Kernel changes to drop 5.4 and switch to 5.10 and 5.13 are pending,
mainly on other layers being ready for the change to the default versions.
*   There also appear to be issues in the buildtools tarball on aarch64,
probably from the gcc 11 upgrade.
*   There is a plan to migrate the tune files into architecture specific
directories. This patch will likely merge in the next few days and will need
BSP layers to be updated as the tune files will no longer be found.
*   The bitbake fetcher no longer ignores SSL certificates by default
(this wasn't a huge problem as we separately checksum input files).
*   LTO linker flags handling changes were merged now the
reproducibility issues it introduced were fixed meaning LTO builds should be
more reproducible.
*   Overlayfs class changes were merged.
*   Intermittent issues are ongoing and help is very much welcome on
these issues. You can see the list of failures we're continuing to see by
searching for the "AB-INT" tag in bugzilla:

https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

 

Ways to contribute:

*   There are bugs identified as possible for newcomers to the project:

https://wiki.yoctoproject.org/wiki/Newcomers
*   There are bugs that are currently unassigned for YP 3.4. See:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.4_Unassigned_Enhan
cements.2FBugs
*   We'd welcome new maintainers for recipes in OE-Core. Please see the
list at:

http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/main
tainers.inc and discuss with the existing maintainer, or ask on the OE-Core
mailing list. We will likely move a chunk of these to "Unassigned" soon to
help facilitate this.

 

YP 3.4 Milestone Dates:

*   YP 3.4 M3 build date 2021/08/23 (Feature Freeze)
*   YP 3.4 M3 Release date 2021/09/03
*   YP 3.4 M4 build date 2021/10/04
*   YP 3.4 M4 Release date 2021/10/29

 

Planned upcoming dot releases:

*   YP 3.1.10  is released
*   YP 3.1.10 release date 2021/08/06
*   YP 3.1.11 build date 2021/09/13
*   YP 3.1.11 release date 2021/9/24

 

Tracking Metrics:

*   WDD 2583 (last week 2577) (

https://wiki.yoctoproject.org/charts/combo.html)
*   OE-Core/Poky Patch Metrics

*   Total patches found: 1293 (last week 1292)
*   Patches in the Pending State: 485 (38%) [last week 485 (38%)]

 

The Yocto Project's technical governance is through its Technical Steering
Committee, more information is available at:

 
https://wiki.yoctoproject.org/wiki/TSC

 

The Status reports are now stored on the wiki at:

https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[If anyone has suggestions for other information 

[OE-core] [PATCH 2/2] binutils: Apply upstream patch to fix 'too many open files' on qtwebengine

[Andreas Müller]

Since upgrade of binutils to 2.37 builds of qtwebengine failed to link even
with ulimits -n 100 (!!).
Fix that by applying a patch from stable 'binutils-2_37-branch'.

Signed-off-by: Andreas Müller 
---
 .../binutils/binutils-2.37.inc|   1 +
 ...le-descriptor-if-there-is-no-archive.patch | 234 ++
 2 files changed, 235 insertions(+)
 create mode 100644 
meta/recipes-devtools/binutils/binutils/0017-bfd-Close-the-file-descriptor-if-there-is-no-archive.patch

diff --git a/meta/recipes-devtools/binutils/binutils-2.37.inc 
b/meta/recipes-devtools/binutils/binutils-2.37.inc
index 4218c0a616..6093558e4b 100644
--- a/meta/recipes-devtools/binutils/binutils-2.37.inc
+++ b/meta/recipes-devtools/binutils/binutils-2.37.inc
@@ -35,5 +35,6 @@ SRC_URI = "\
  file://0014-Fix-rpath-in-libtool-when-sysroot-is-enabled.patch \
  file://0015-sync-with-OE-libtool-changes.patch \
  file://0016-Check-for-clang-before-checking-gcc-version.patch \
+ file://0017-bfd-Close-the-file-descriptor-if-there-is-no-archive.patch \
 "
 S  = "${WORKDIR}/git"
diff --git 
a/meta/recipes-devtools/binutils/binutils/0017-bfd-Close-the-file-descriptor-if-there-is-no-archive.patch
 
b/meta/recipes-devtools/binutils/binutils/0017-bfd-Close-the-file-descriptor-if-there-is-no-archive.patch
new file mode 100644
index 00..9becee39a2
--- /dev/null
+++ 
b/meta/recipes-devtools/binutils/binutils/0017-bfd-Close-the-file-descriptor-if-there-is-no-archive.patch
@@ -0,0 +1,234 @@
+From 1c611b40e6bfc8029bff7696814330b5bc0ee5c0 Mon Sep 17 00:00:00 2001
+From: "H.J. Lu" 
+Date: Mon, 26 Jul 2021 05:59:55 -0700
+Subject: [PATCH] bfd: Close the file descriptor if there is no archive fd
+
+Close the file descriptor if there is no archive plugin file descriptor
+to avoid running out of file descriptors on thin archives with many
+archive members.
+
+bfd/
+
+   PR ld/28138
+   * plugin.c (bfd_plugin_close_file_descriptor): Close the file
+   descriptor there is no archive plugin file descriptor.
+
+ld/
+
+   PR ld/28138
+   * testsuite/ld-plugin/lto.exp: Run tmpdir/pr28138 only for
+   native build.
+
+   PR ld/28138
+   * testsuite/ld-plugin/lto.exp: Run ld/28138 tests.
+   * testsuite/ld-plugin/pr28138.c: New file.
+   * testsuite/ld-plugin/pr28138-1.c: Likewise.
+   * testsuite/ld-plugin/pr28138-2.c: Likewise.
+   * testsuite/ld-plugin/pr28138-3.c: Likewise.
+   * testsuite/ld-plugin/pr28138-4.c: Likewise.
+   * testsuite/ld-plugin/pr28138-5.c: Likewise.
+   * testsuite/ld-plugin/pr28138-6.c: Likewise.
+   * testsuite/ld-plugin/pr28138-7.c: Likewise.
+
+(cherry picked from commit 5a98fb7513b559e20dfebdbaa2a471afda3b4742)
+(cherry picked from commit 7dc37e1e1209c80e0bab784df6b6bac335e836f2)
+
+Upstream-Status: 
Accepted[https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=1c611b40e6bfc8029bff7696814330b5bc0ee5c0]
+---
+ bfd/plugin.c   |  8 +++
+ ld/testsuite/ld-plugin/lto.exp | 34 ++
+ ld/testsuite/ld-plugin/pr28138-1.c |  6 ++
+ ld/testsuite/ld-plugin/pr28138-2.c |  6 ++
+ ld/testsuite/ld-plugin/pr28138-3.c |  6 ++
+ ld/testsuite/ld-plugin/pr28138-4.c |  6 ++
+ ld/testsuite/ld-plugin/pr28138-5.c |  6 ++
+ ld/testsuite/ld-plugin/pr28138-6.c |  6 ++
+ ld/testsuite/ld-plugin/pr28138-7.c |  6 ++
+ ld/testsuite/ld-plugin/pr28138.c   | 20 ++
+ 10 files changed, 104 insertions(+)
+ create mode 100644 ld/testsuite/ld-plugin/pr28138-1.c
+ create mode 100644 ld/testsuite/ld-plugin/pr28138-2.c
+ create mode 100644 ld/testsuite/ld-plugin/pr28138-3.c
+ create mode 100644 ld/testsuite/ld-plugin/pr28138-4.c
+ create mode 100644 ld/testsuite/ld-plugin/pr28138-5.c
+ create mode 100644 ld/testsuite/ld-plugin/pr28138-6.c
+ create mode 100644 ld/testsuite/ld-plugin/pr28138-7.c
+ create mode 100644 ld/testsuite/ld-plugin/pr28138.c
+
+diff --git a/bfd/plugin.c b/bfd/plugin.c
+index 6cfa2b66470..3bab8febe88 100644
+--- a/bfd/plugin.c
 b/bfd/plugin.c
+@@ -291,6 +291,14 @@ bfd_plugin_close_file_descriptor (bfd *abfd, int fd)
+&& !bfd_is_thin_archive (abfd->my_archive))
+   abfd = abfd->my_archive;
+ 
++  /* Close the file descriptor if there is no archive plugin file
++   descriptor.  */
++  if (abfd->archive_plugin_fd == -1)
++  {
++close (fd);
++return;
++  }
++
+   abfd->archive_plugin_fd_open_count--;
+   /* Dup the archive plugin file descriptor for later use, which
+will be closed by _bfd_archive_close_and_cleanup.  */
+diff --git a/ld/testsuite/ld-plugin/lto.exp b/ld/testsuite/ld-plugin/lto.exp
+index def69e43ab3..999d911ce6a 100644
+--- a/ld/testsuite/ld-plugin/lto.exp
 b/ld/testsuite/ld-plugin/lto.exp
+@@ -687,6 +687,40 @@ if { [is_elf_format] && [check_lto_shared_available] } {
+ }
+ }
+ 
++run_cc_link_tests [list \
++[list \
++  "Build pr28138.a" \
++  "-T" "" \
++   

[OE-core] [PATCH 1/2] mesa: upgrade 21.1.5 -> 21.1.7

[Andreas Müller]

Joshua's vc4/v3d/dma-patch was applied in 21.1.7

Release notes 21.1.7:

Bug fixes
Miscompilation of a switch case
[radeonsi][regression] CPU is being used ~10 times more than usual after 
c5478f9067f.
dEQP-VK.wsi.android.swapchain.create#image_swapchain_create_info crash on 
Android R
The image is distorted while use iGPU(Intel GPU) rendering and output via 
dGPU (AMD GPU)
lima: regression in plbu scissors cmd
Incorrect rendering
Changes
pan/bi: Restrict swizzles on same cycle temporaries
nir/lower_mediump_io: Don’t remap base unless needed
nir/lower_mediump: Fix metadata in all passes
util/fossilize_db: Update parsed_offset correctly.
util/fossilize_db: Reset file position to parsed_offset on cache_offset 
read failure.
util/fossilize_db: Flush files after header write.
util/fossilize_db: Be conservative about header length check for locking.
util/fossilize_db: Only allocate entries after full read.
util/fossilize_db: Use uint64_t for file size.
util/fossilize_db: Unlock the cache file if the entry already exists.
util/fossilize_db: Add extra flock mutex.
radv: Allocate space for inline push constants.
vulkan/wsi/x11: do not inherit last_present_mode
ir3: Preserve gl_ViewportIndex in the binning shader
teximage: return correct desktop GL error for compressedteximage
intel/fs: restrict max push length on older GPUs to a smaller amount
virgl: disable anisotropic filtering.
freedreno/ir3: Add build id to the disassembler test
.pick_status.json: Update to 7055282231cdad23e7b23fb49a2f953a99797f8a
.pick_status.json: Update to 2f06642b06c94f07f4bfe3df32b25659428c9144
.pick_status.json: Mark 6ccf11ac2b951963407601b5b1109b45a972e48e as 
denominated
.pick_status.json: Update to 2f06642b06c94f07f4bfe3df32b25659428c9144
.pick_status.json: Update to 353e6323936b812884fa677c25bdba91554881b7
.pick_status.json: Update to 4128acdee32eadfef1fb8c3c3ce2e512a267cdf4
pick-ui: drop assert that optional argument is passed
pick-ui: show nomination type in the UI
pick-ui: show commit date
lima: avoid crash with negative viewport values
zink: make codegen compatible with python 3.5
mesa/main: Check for fbo attachments when importing EGL images to textures
v3d, vc4: Fix dmabuf import for non-scanout buffers
gallium/hud: initialize query
nv30: fix emulated vertex index buffers
gallium: Reset {d,r}Priv in dri_unbind_context
loader/dri3: create linear buffer with scanout support
anv: fix submission batching with perf queries
anv: don’t try to access Android swapchains
renderonly: don’t complain when GPU import fails
etnaviv: always try to create KMS side handles for imported resources
glsl: evaluate switch expression once
zink: use array size in spirv bo length calculations
etnaviv: fix gbm_bo_get_handle_for_plane for multiplanar images
clover/spirv: Properly size 3-component vector args
clover/nir: Set constant buffer pointer size to host
gallium/va: don’t use key=NULL in hash tables
amd/registers: fix fields conflict detection
radeonsi: don’t create an infinite number of variants
nir/algebraic: fix imod by negative power-of-two
radv: fix selecting the first active CU when profiling with SQTT
etnaviv: fix renderonly check in etna_resource_alloc
etnaviv: fail in get_handle(TYPE_KMS) without a scanout resource
freedreno: fail in get_handle(TYPE_KMS) without a scanout resource
panfrost: fail in get_handle(TYPE_KMS) without a scanout resource
lima: fail in get_handle(TYPE_KMS) without a scanout resource
nine: Fix assert in tx_src_param
intel/compiler: make sure swizzle is applied to if condition
glsl: Add operator for .length() method on implicitly-sized arrays
glsl: Properly handle .length() of an unsized array
gallium/vl: don’t leak fd in vl_dri3_screen_create

Release notes 21.1.6:

Bug fixes
[RADV] FSR in Resident Evil: Village looks very pixelated on Polaris
Crash in update_buffers after closing KDE “splash screen” downloader
Crash in update_buffers after closing KDE “splash screen” downloader
radeonsi: persistent, read-only buffer maps are slow to read
substance painter flickering with jagged texture and masks shown black
radv: FP16 mode in FidelityFX FSR doesn’t look right
[RADV] Blocky corruption in Scarlet Nexus and vkd3d-proton 2.4
Radeon RX580 and 5700 XT: Reloading ARB assembly shaders causes very 
glitchy rendering

Changes
targets/graw-xlib: Add missing dep_x11
egl/surfaceless: try kms_swrast before swrast
meson: allow egl_native_platform to be specified
freedreno/computerator: Fix local_size typo
aco/optimizer: ensure to not erase high bits when propagating packed 
constants
egl/wayland: Error on invalid native window
egl/wayland: Allow EGLSurface to outlive wl_egl_window
softpipe/aniso: move DDQ 

Re: [OE-core][PATCH v2 2/2] oeqa: wic: Add tests for --no-fstab-update

[Alexandre Belloni]

Hi,

On 16/08/2021 10:05:08+0200, Daniel Gomez wrote:
> Hi Alexandre,
> 
> 
> On Fri, 13 Aug 2021 at 07:41, Daniel Gomez via lists.openembedded.org
>  wrote:
> >
> > Hi Alexandre,
> >
> > On Thu, 12 Aug 2021 at 18:34, Alexandre Belloni
> >  wrote:
> > >
> > > Hello,
> > >
> > > On 10/08/2021 22:11:01+0200, Daniel Gomez wrote:
> > > > Add tests for the --no-fstab-update wic part command.
> > > >
> > > > Signed-off-by: Daniel Gomez 
> > > > ---
> > > >  meta/lib/oeqa/selftest/cases/wic.py | 56 +
> > > >  1 file changed, 56 insertions(+)
> > > >
> > > > diff --git a/meta/lib/oeqa/selftest/cases/wic.py 
> > > > b/meta/lib/oeqa/selftest/cases/wic.py
> > > > index 2efbe514c1..a58360851a 100644
> > > > --- a/meta/lib/oeqa/selftest/cases/wic.py
> > > > +++ b/meta/lib/oeqa/selftest/cases/wic.py
> > > > @@ -11,6 +11,7 @@
> > > >  import os
> > > >  import sys
> > > >  import unittest
> > > > +import hashlib
> > > >
> > > >  from glob import glob
> > > >  from shutil import rmtree, copy
> > > > @@ -686,6 +687,61 @@ part /etc --source rootfs --fstype=ext4 
> > > > --change-directory=etc
> > > >% (wks_file, self.resultdir), 
> > > > ignore_status=True).status)
> > > >  os.remove(wks_file)
> > > >
> > > > +def test_no_fstab_update(self):
> > > > +"""Test --no-fstab-update wks option."""
> > > > +
> > > > +oldpath = os.environ['PATH']
> > > > +os.environ['PATH'] = get_bb_var("PATH", "wic-tools")
> > > > +
> > > > +# Get stock fstab from base-files recipe
> > > > +bitbake('base-files')
> > > > +bf_fstab = os.path.join(get_bb_var('WORKDIR', 
> > > > 'base-files'),'image/etc/fstab')
> > > > +bf_fstab_md5sum = runCmd('md5sum %s 2>/dev/null' % 
> > > > bf_fstab).output.split(" ")[0]
> > > > +
> > >
> > > This failed on the autobuilders:
> > >
> > >   File 
> > > "/home/pokybuild/yocto-worker/oe-selftest-debian/build/meta/lib/oeqa/selftest/cases/wic.py",
> > >  line 699, in test_no_fstab_update
> > > bf_fstab_md5sum = runCmd('md5sum %s 2>/dev/null' % 
> > > bf_fstab).output.split(" ")[0]
> > >   File 
> > > "/home/pokybuild/yocto-worker/oe-selftest-debian/build/meta/lib/oeqa/utils/commands.py",
> > >  line 207, in runCmd
> > > raise AssertionError("Command '%s' returned non-zero exit status 
> > > %d:\n%s" % (command, result.status, exc_output))
> > > AssertionError: Command 'md5sum 
> > > /home/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-15202/tmp/work/qemux86_64-poky-linux/base-files/3.0.14-r89/image/etc/fstab
> > >  2>/dev/null' returned non-zero exit status 1:
> > >
> > > Full log here:
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/2374/steps/14/logs/stdio
> >
> > Thanks for letting me know. I'll take a look.
> 
> I can't replicate the problem in my setup ('master' branch for bitbake
> and openembedded core; 'qemux86-64' machine) . Could it be possible to
> get the environment variables for the build?
> 
> The problem comes when executing the first md5sum command:
> 
> 1. bitbake 'base-files' recipe.
> 2. Get the 'WORKDIR' for 'base-files' recipe.
> 3. Do 'md5sum' for the 'WORKDIR' + 'image/etc/fstab' file.
> 
> md5sum 
> /home/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-15202/tmp/work/qemux86_64-poky-linux/base-files/3.0.14-r89/image/etc/fstab
> 
> If the file does not exist, md5sum will return the same '1' status
> (assuming that's the error). Could this be bause the '${WORKDIR} +
> image' for the 'base-files' recipe is located under another directory?
> Could we get access to that directory to know if the file was present
> there?
> 

I did run the build again and:

debian10-ty-1:~$ md5sum 
/home/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-32220/tmp/work/qemux86_64-poky-linux/base-files/3.0.14-r89/image/etc/fstab
md5sum: 
/home/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-32220/tmp/work/qemux86_64-poky-linux/base-files/3.0.14-r89/image/etc/fstab:
 No such file or directory

debian10-ty-1:~$ ls 
/home/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-32220/tmp/work/qemux86_64-poky-linux/base-files/3.0.14-r89/
deploy-rpms   license-destdir  source-date-epoch
sstate-install-package_qa sstate-install-packagedata   
sstate-install-populate_sysroot  temp
deploy-source-date-epoch  pkgdata-pdata-input  
sstate-install-deploy_source_date_epoch  sstate-install-package_write_rpm  
sstate-install-populate_lic  sysroot-destdir

I guess the issue is that we reuse the sstate cache and so the file is
not present at all.

> If that's the case, I could replace the command to be executed with
> one of the following environment variables:
> D="/workdir/openembedded-core/build/tmp-glibc/work/qemux86_64-oe-linux/base-files/3.0.14-r89/image"
> PKGD="/workdir/openembedded-core/build/tmp-glibc/work/qemux86_64-oe-linux/base-files/3.0.14-r89/package"
> 

Re: [OE-core] [PATCH V2] shadow: add /etc/default/useradd

[Alexander Kanavin]

Thanks, this should work fine :)

Alex

On Tue, 17 Aug 2021 at 10:17, Yi Zhao  wrote:

> The shadow 4.9 stops shiping /etc/default/useradd[1] and uses built-in
> settings by default. Some settings are not consistent with previous
> shadow 4.8.1 in oe-core. e.g. The default shell is /bin/bash rather than
> /bin/sh. Per shadow 4.8.1 settings, add /etc/default/useradd back to
> update useradd settings.
>
> [1]
> https://github.com/shadow-maint/shadow/commit/bbf4b79bc49fd1826eb41f6629669ef0b647267b
>
> Signed-off-by: Yi Zhao 
> ---
>  meta/recipes-extended/shadow/files/useradd | 8 
>  meta/recipes-extended/shadow/shadow.inc| 3 +++
>  2 files changed, 11 insertions(+)
>  create mode 100644 meta/recipes-extended/shadow/files/useradd
>
> diff --git a/meta/recipes-extended/shadow/files/useradd
> b/meta/recipes-extended/shadow/files/useradd
> new file mode 100644
> index 00..782aeef418
> --- /dev/null
> +++ b/meta/recipes-extended/shadow/files/useradd
> @@ -0,0 +1,8 @@
> +# useradd defaults file
> +GROUP=100
> +HOME=/home
> +INACTIVE=-1
> +EXPIRE=
> +SHELL=/bin/sh
> +SKEL=/etc/skel
> +CREATE_MAIL_SPOOL=no
> diff --git a/meta/recipes-extended/shadow/shadow.inc
> b/meta/recipes-extended/shadow/shadow.inc
> index 97ffae978a..44b9898897 100644
> --- a/meta/recipes-extended/shadow/shadow.inc
> +++ b/meta/recipes-extended/shadow/shadow.inc
> @@ -16,6 +16,7 @@ SRC_URI = "
> https://github.com/shadow-maint/shadow/releases/download/v${PV}/${BP}
> file://shadow-relaxed-usernames.patch \
>
> file://0001-Fix-out-of-tree-builds-with-respect-to-libsubid-incl.patch \
> file://0001-libsubid-link-to-PAM-libraries.patch \
> +   file://useradd \
> "
>
>  SRC_URI:append:class-target = " \
> @@ -115,6 +116,8 @@ do_install() {
> # Use proper encryption for passwords
> sed -i 's/^#ENCRYPT_METHOD.*$/ENCRYPT_METHOD SHA512/'
> ${D}${sysconfdir}/login.defs
>
> +   install -d ${D}${sysconfdir}/default
> +   install -m 0644 ${WORKDIR}/useradd ${D}${sysconfdir}/default
>  }
>
>  do_install:append() {
> --
> 2.25.1
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154874): 
https://lists.openembedded.org/g/openembedded-core/message/154874
Mute This Topic: https://lists.openembedded.org/mt/84943382/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH V2] shadow: add /etc/default/useradd

[Yi Zhao]

The shadow 4.9 stops shiping /etc/default/useradd[1] and uses built-in
settings by default. Some settings are not consistent with previous
shadow 4.8.1 in oe-core. e.g. The default shell is /bin/bash rather than
/bin/sh. Per shadow 4.8.1 settings, add /etc/default/useradd back to
update useradd settings.

[1] 
https://github.com/shadow-maint/shadow/commit/bbf4b79bc49fd1826eb41f6629669ef0b647267b

Signed-off-by: Yi Zhao 
---
 meta/recipes-extended/shadow/files/useradd | 8 
 meta/recipes-extended/shadow/shadow.inc| 3 +++
 2 files changed, 11 insertions(+)
 create mode 100644 meta/recipes-extended/shadow/files/useradd

diff --git a/meta/recipes-extended/shadow/files/useradd 
b/meta/recipes-extended/shadow/files/useradd
new file mode 100644
index 00..782aeef418
--- /dev/null
+++ b/meta/recipes-extended/shadow/files/useradd
@@ -0,0 +1,8 @@
+# useradd defaults file
+GROUP=100
+HOME=/home
+INACTIVE=-1
+EXPIRE=
+SHELL=/bin/sh
+SKEL=/etc/skel
+CREATE_MAIL_SPOOL=no
diff --git a/meta/recipes-extended/shadow/shadow.inc 
b/meta/recipes-extended/shadow/shadow.inc
index 97ffae978a..44b9898897 100644
--- a/meta/recipes-extended/shadow/shadow.inc
+++ b/meta/recipes-extended/shadow/shadow.inc
@@ -16,6 +16,7 @@ SRC_URI = 
"https://github.com/shadow-maint/shadow/releases/download/v${PV}/${BP}
file://shadow-relaxed-usernames.patch \

file://0001-Fix-out-of-tree-builds-with-respect-to-libsubid-incl.patch \
file://0001-libsubid-link-to-PAM-libraries.patch \
+   file://useradd \
"
 
 SRC_URI:append:class-target = " \
@@ -115,6 +116,8 @@ do_install() {
# Use proper encryption for passwords
sed -i 's/^#ENCRYPT_METHOD.*$/ENCRYPT_METHOD SHA512/' 
${D}${sysconfdir}/login.defs
 
+   install -d ${D}${sysconfdir}/default
+   install -m 0644 ${WORKDIR}/useradd ${D}${sysconfdir}/default
 }
 
 do_install:append() {
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154873): 
https://lists.openembedded.org/g/openembedded-core/message/154873
Mute This Topic: https://lists.openembedded.org/mt/84943382/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [poky][dunfell][PATCH] lighttpd: Add patch for reuse large memory chunks

[purushottamc]

Hi Steve,

could you please check again?

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154872): 
https://lists.openembedded.org/g/openembedded-core/message/154872
Mute This Topic: https://lists.openembedded.org/mt/84836400/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [poky][dunfell][PATCH] python3: Remove unused python3 recipe

[purushottamc]

Hi,

Please provide an update on this change.

Could you please confirm if changes are OK and can be merged?

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154871): 
https://lists.openembedded.org/g/openembedded-core/message/154871
Mute This Topic: https://lists.openembedded.org/mt/84788234/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] shadow: update default settings for useradd

[Yi Zhao]

On 8/17/21 2:59 PM, Alexander Kanavin wrote:
If the issue is that /etc/default/useradd was deleted, shouldn't we 
address this by reinstating that file? Patching the source code does 
not seem like a better solution, and introduces surprising behaviour 
for those expecting upstream defaults rather than Yocto's.


Thanks. That's reasonable. I will send V2.


//Yi




Alex

On Tue, 17 Aug 2021 at 05:11, Yi Zhao > wrote:


The shadow 4.9 stops shiping /etc/default/useradd[1] and uses built-in
settings by default. Some settings are not consistent with previous
shadow 4.8.1 in oe-core. Per shadow 4.8.1 settings, change the default
shell to /bin/sh and stop creating mail spool.

[1]

https://github.com/shadow-maint/shadow/commit/bbf4b79bc49fd1826eb41f6629669ef0b647267b



Signed-off-by: Yi Zhao mailto:yi.z...@windriver.com>>
---
 ...0001-useradd-update-default-settings.patch | 38
+++
 meta/recipes-extended/shadow/shadow.inc       |  1 +
 2 files changed, 39 insertions(+)
 create mode 100644

meta/recipes-extended/shadow/files/0001-useradd-update-default-settings.patch

diff --git

a/meta/recipes-extended/shadow/files/0001-useradd-update-default-settings.patch

b/meta/recipes-extended/shadow/files/0001-useradd-update-default-settings.patch
new file mode 100644
index 00..1e6702019b
--- /dev/null
+++

b/meta/recipes-extended/shadow/files/0001-useradd-update-default-settings.patch
@@ -0,0 +1,38 @@
+From 46106ec16409ea99f73a8a8823e50ac54db8e122 Mon Sep 17 00:00:00
2001
+From: Yi Zhao mailto:yi.z...@windriver.com>>
+Date: Tue, 17 Aug 2021 10:11:27 +0800
+Subject: [PATCH] useradd: update default settings
+
+The shadow 4.9 stops shiping /etc/default/useradd[1] and uses
built-in
+settings by default. Some settings are not consistent with previous
+shadow 4.8.1 in oe-core. Per shadow 4.8.1 settings, change the
default
+shell to /bin/sh and stop creating mail spool.
+
+[1]

https://github.com/shadow-maint/shadow/commit/bbf4b79bc49fd1826eb41f6629669ef0b647267b


+
+Upstream-Status: Inappropriate [embedded specific]
+
+Signed-off-by: Yi Zhao mailto:yi.z...@windriver.com>>
+---
+ src/useradd.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/src/useradd.c b/src/useradd.c
+index 0d3f390d..715351b4 100644
+--- a/src/useradd.c
 b/src/useradd.c
+@@ -104,9 +104,9 @@ FILE *shadow_logfd = NULL;
+ static gid_t def_group = 1000;
+ static const char *def_gname = "other";
+ static const char *def_home = "/home";
+-static const char *def_shell = "/bin/bash";
++static const char *def_shell = "/bin/sh";
+ static const char *def_template = SKEL_DIR;
+-static const char *def_create_mail_spool = "yes";
++static const char *def_create_mail_spool = "no";
+
+ static long def_inactive = -1;
+ static const char *def_expire = "";
+--
+2.25.1
+
diff --git a/meta/recipes-extended/shadow/shadow.inc
b/meta/recipes-extended/shadow/shadow.inc
index 97ffae978a..e2a7a5bac6 100644
--- a/meta/recipes-extended/shadow/shadow.inc
+++ b/meta/recipes-extended/shadow/shadow.inc
@@ -16,6 +16,7 @@ SRC_URI =
"https://github.com/shadow-maint/shadow/releases/download/v${PV}/${BP}


            file://shadow-relaxed-usernames.patch \
file://0001-Fix-out-of-tree-builds-with-respect-to-libsubid-incl.patch
\
            file://0001-libsubid-link-to-PAM-libraries.patch \
+           file://0001-useradd-update-default-settings.patch \
            "

 SRC_URI:append:class-target = " \
-- 
2.25.1






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154870): 
https://lists.openembedded.org/g/openembedded-core/message/154870
Mute This Topic: https://lists.openembedded.org/mt/84940316/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] AUH mails not delivered to oe-core list

[Alexander Kanavin]

Hello Michael,

the problem (AUH mails not making it to the mailing lists) still goes on.
Has there been any progress with the ticket? Should we think of possible
workarounds?

Alex

On Mon, 2 Aug 2021 at 14:42, Alexander Kanavin 
wrote:

> Hello Michael,
>
> unfortunately the problem persists - no AUH emails in the latest round
> either.
>
> Alex
>
> On Mon, 26 Jul 2021 at 23:36, Michael Halstead <
> mhalst...@linuxfoundation.org> wrote:
>
>> That server is having trouble delivering email to Groups.io. I have a
>> support request open with Groups.io about it.
>>
>> On Sun, Jul 25, 2021 at 7:13 AM Alexander Kanavin 
>> wrote:
>>
>>> The latest round of upgrade helper emails didn't make it to oe-core list
>>> (but I did get ones that were also CCd to me directly) - can you please
>>> check?
>>>
>>> Here's the log:
>>>
>>> https://autobuilder.yoctoproject.org/typhoon/#/builders/112/builds/37/steps/11/logs/stdio
>>>
>>> Alex
>>>
>>> On Sun, 25 Jul 2021 at 14:28,  wrote:
>>>
 Hello,

 this email is a notification from the Auto Upgrade Helper
 that the automatic attempt to upgrade the recipe *meson* to *0.59.0*
 has Failed (devtool error).

 Detailed error information:

 Running 'devtool upgrade' for recipe meson failed.
 NOTE: Starting bitbake server...
 NOTE: Reconnecting to bitbake server...
 NOTE: Retrying server connection (#1)...
 Loading cache...done.
 Loaded 1459 entries from dependency cache.
 INFO: Extracting current version source...
 Removing 1 recipes from the x86_64 sysroot...done.
 NOTE: Resolving any missing task queue dependencies

 Build Configuration:
 BB_VERSION   = "1.51.0"
 BUILD_SYS= "x86_64-linux"
 NATIVELSBSTRING  = "universal"
 TARGET_SYS   = "x86_64-poky-linux"
 MACHINE  = "qemux86-64"
 DISTRO   = "poky"
 DISTRO_VERSION   =
 "3.3+snapshot-0421d4df954a35ad0176a12db1060e52115b14b1"
 TUNE_FEATURES= "m64 core2"
 TARGET_FPU   = ""
 meta
 meta-poky
 meta-yocto-bsp   =
 "tmp-auh-upgrades:0421d4df954a35ad0176a12db1060e52115b14b1"
 workspace= "master:982f98f721af11b5698be8fe959058823d1de0d3"

 Initialising tasks...done.
 Sstate summary: Wanted 0 Local 0 Network 0 Missed 0 Current 20 (0%
 match, 100% complete)
 NOTE: Executing Tasks
 NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be
 rerun and all succeeded.
 NOTE: Writing buildhistory
 NOTE: Writing buildhistory took: 1 seconds
 INFO: Extracting upgraded version source...
 INFO: Fetching
 https://github.com/mesonbuild/meson/releases/download/0.59.0/meson-0.59.0.tar.gz.
 ..
 Loading cache...done.
 Loaded 1459 entries from dependency cache.
 Parsing recipes...done.
 Parsing of 822 .bb files complete (820 cached, 2 parsed). 1460 targets,
 35 skipped, 0 masked, 0 errors.
 NOTE: Resolving any missing task queue dependencies

 Build Configuration:
 BB_VERSION   = "1.51.0"
 BUILD_SYS= "x86_64-linux"
 NATIVELSBSTRING  = "universal"
 TARGET_SYS   = "x86_64-poky-linux"
 MACHINE  = "qemux86-64"
 DISTRO   = "poky"
 DISTRO_VERSION   =
 "3.3+snapshot-0421d4df954a35ad0176a12db1060e52115b14b1"
 TUNE_FEATURES= "m64 core2"
 TARGET_FPU   = ""
 meta
 meta-poky
 meta-yocto-bsp   =
 "tmp-auh-upgrades:0421d4df954a35ad0176a12db1060e52115b14b1"
 workspace= "master:982f98f721af11b5698be8fe959058823d1de0d3"

 Initialising tasks...done.
 Sstate summary: Wanted 0 Local 0 Network 0 Missed 0 Current 0 (0%
 match, 0% complete)
 NOTE: No setscene tasks
 NOTE: Executing Tasks
 NOTE: Tasks Summary: Attempted 2 tasks of which 0 didn't need to be
 rerun and all succeeded.
 NOTE: Writing buildhistory
 NOTE: Writing buildhistory took: 1 seconds
 DEBUG 5 [Errno 25] Inappropriate ioctl for device
 Adding changed files:   0% |   | ETA:
 --:--:--
 Adding changed files:   0% |   | ETA:
 --:--:--
 Adding changed files:  15% |#   | ETA:
 0:00:00
 Adding changed files:  30% |##  | ETA:
 0:00:00
 Adding changed files:  45% || ETA:
 0:00:00
 Adding changed files:  60% |#   | ETA:
 0:00:00
 Adding changed files:  75% |### | ETA:
 0:00:00
 Adding changed files:  90% || ETA:
 0:00:00
 Adding changed files: 100% || Time:
 0:00:00
 INFO: Rebasing devtool onto c5d7d02bfafd0664a2d3e9c304d3aedf2b771bda
 

Re: [OE-core] [PATCH] shadow: update default settings for useradd

[Alexander Kanavin]

If the issue is that /etc/default/useradd was deleted, shouldn't we address
this by reinstating that file? Patching the source code does not seem like
a better solution, and introduces surprising behaviour for those expecting
upstream defaults rather than Yocto's.

Alex

On Tue, 17 Aug 2021 at 05:11, Yi Zhao  wrote:

> The shadow 4.9 stops shiping /etc/default/useradd[1] and uses built-in
> settings by default. Some settings are not consistent with previous
> shadow 4.8.1 in oe-core. Per shadow 4.8.1 settings, change the default
> shell to /bin/sh and stop creating mail spool.
>
> [1]
> https://github.com/shadow-maint/shadow/commit/bbf4b79bc49fd1826eb41f6629669ef0b647267b
>
> Signed-off-by: Yi Zhao 
> ---
>  ...0001-useradd-update-default-settings.patch | 38 +++
>  meta/recipes-extended/shadow/shadow.inc   |  1 +
>  2 files changed, 39 insertions(+)
>  create mode 100644
> meta/recipes-extended/shadow/files/0001-useradd-update-default-settings.patch
>
> diff --git
> a/meta/recipes-extended/shadow/files/0001-useradd-update-default-settings.patch
> b/meta/recipes-extended/shadow/files/0001-useradd-update-default-settings.patch
> new file mode 100644
> index 00..1e6702019b
> --- /dev/null
> +++
> b/meta/recipes-extended/shadow/files/0001-useradd-update-default-settings.patch
> @@ -0,0 +1,38 @@
> +From 46106ec16409ea99f73a8a8823e50ac54db8e122 Mon Sep 17 00:00:00 2001
> +From: Yi Zhao 
> +Date: Tue, 17 Aug 2021 10:11:27 +0800
> +Subject: [PATCH] useradd: update default settings
> +
> +The shadow 4.9 stops shiping /etc/default/useradd[1] and uses built-in
> +settings by default. Some settings are not consistent with previous
> +shadow 4.8.1 in oe-core. Per shadow 4.8.1 settings, change the default
> +shell to /bin/sh and stop creating mail spool.
> +
> +[1]
> https://github.com/shadow-maint/shadow/commit/bbf4b79bc49fd1826eb41f6629669ef0b647267b
> +
> +Upstream-Status: Inappropriate [embedded specific]
> +
> +Signed-off-by: Yi Zhao 
> +---
> + src/useradd.c | 4 ++--
> + 1 file changed, 2 insertions(+), 2 deletions(-)
> +
> +diff --git a/src/useradd.c b/src/useradd.c
> +index 0d3f390d..715351b4 100644
> +--- a/src/useradd.c
>  b/src/useradd.c
> +@@ -104,9 +104,9 @@ FILE *shadow_logfd = NULL;
> + static gid_t def_group = 1000;
> + static const char *def_gname = "other";
> + static const char *def_home = "/home";
> +-static const char *def_shell = "/bin/bash";
> ++static const char *def_shell = "/bin/sh";
> + static const char *def_template = SKEL_DIR;
> +-static const char *def_create_mail_spool = "yes";
> ++static const char *def_create_mail_spool = "no";
> +
> + static long def_inactive = -1;
> + static const char *def_expire = "";
> +--
> +2.25.1
> +
> diff --git a/meta/recipes-extended/shadow/shadow.inc
> b/meta/recipes-extended/shadow/shadow.inc
> index 97ffae978a..e2a7a5bac6 100644
> --- a/meta/recipes-extended/shadow/shadow.inc
> +++ b/meta/recipes-extended/shadow/shadow.inc
> @@ -16,6 +16,7 @@ SRC_URI = "
> https://github.com/shadow-maint/shadow/releases/download/v${PV}/${BP}
> file://shadow-relaxed-usernames.patch \
>
> file://0001-Fix-out-of-tree-builds-with-respect-to-libsubid-incl.patch \
> file://0001-libsubid-link-to-PAM-libraries.patch \
> +   file://0001-useradd-update-default-settings.patch \
> "
>
>  SRC_URI:append:class-target = " \
> --
> 2.25.1
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154868): 
https://lists.openembedded.org/g/openembedded-core/message/154868
Mute This Topic: https://lists.openembedded.org/mt/84940316/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] glibc: Fix CVE-2021-33574

[Ernst Sjöstrand]

There is now an additional fix on top of this:

https://it.slashdot.org/story/21/08/16/2131221/linux-glibc-security-fix-created-a-nastier-linux-bug

https://access.redhat.com/security/cve/cve-2021-38604

//E

Den mån 2 aug. 2021 kl 06:14 skrev Vinay Kumar :

> Hi Anuj,
>
> >> It seems wrong to me because the patch header/description is not
> >> correct here. It's no longer a backport of just
> >> 42d359350510506b87101cf77202fefcbfc790cb.
>
> Yes, I merged 2 commits first
> (42d359350510506b87101cf77202fefcbfc790cb and
> 217b6dc298156bdb0d6aea9ea93e7e394a5ff091)
> and then backported as a single patch, and I used only the patch
> header of 42d359350510506b87101cf77202fefcbfc790cb.
>
> >> I also just noticed that there's already a fix for this CVE in my
> >> branch. So I think I will take that:
>
> Ok, thanks. Will go with this once it gets merged to the "hardknott"
> branch.
>
> Regards,
> Vinay
>
> On Mon, Aug 2, 2021 at 8:09 AM Mittal, Anuj  wrote:
> >
> > On Sat, 2021-07-31 at 21:57 +0530, Vinay Kumar wrote:
> > > Hi Anuj,
> > >
> > > The patch is conjugate of both commits.
> > >
> https://sourceware.org/git/?p=glibc.git;a=commit;h=42d359350510506b87101cf77202fefcbfc790cb
> > >
> > >
> https://sourceware.org/git/?p=glibc.git;a=commit;h=217b6dc298156bdb0d6aea9ea93e7e394a5ff091
> > >
> > > Also, the patch is committed to master branch
> > >
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=55681d09d7f519a1c7f17d17b18ec59bccdc91ca
> > >
> > > Due you want me to resubmit for "hardknott" branch by splitting in to
> > > 2 patches ?
> >
> > It seems wrong to me because the patch header/description is not
> > correct here. It's no longer a backport of just
> > 42d359350510506b87101cf77202fefcbfc790cb.
> >
> > I also just noticed that there's already a fix for this CVE in my
> > branch. So I think I will take that:
> >
> >
> https://git.openembedded.org/openembedded-core-contrib/commit/?h=anujm/hardknott=ede353df06a07d35dc66d024e2c7bd1b250d9761
> >
> > Thanks,
> >
> > Anuj
> >
> > >
> > > Regards,
> > > Vinay
> > >
> > > On Sat, Jul 31, 2021 at 11:52 AM Mittal, Anuj 
> > > wrote:
> > > >
> > > > On Tue, 2021-07-27 at 11:38 -0700, Vinay Kumar wrote:
> > > > > Source: https://sourceware.org/git/glibc.git
> > > > > Tracking -- https://sourceware.org/bugzilla/show_bug.cgi?id=27896
> > > > >
> > > > > Backported upstream commit 42d359350510506b87101cf77202fefcbfc790cb
> > > > > to
> > > > > glibc-2.33 source with dependent commit id
> > > > > 217b6dc298156bdb0d6aea9ea93e7e394a5ff091.
> > > > >
> > > > > Upstream-Status: Backport
> > > > > [
> > > > >
> https://sourceware.org/git/?p=glibc.git;a=commit;h=42d359350510506b87101cf77202fefcbfc790cb
> > > > > ]
> > > >
> > > > It looks like you'd need to backport this one too:
> > > >
> > > >
> https://sourceware.org/git/?p=glibc.git;a=commit;h=217b6dc298156bdb0d6aea9ea93e7e394a5ff091
> > > >
> > > > ?
> > > >
> > > > Thanks,
> > > >
> > > > Anuj
> > > >
> > > > >
> > > > > Signed-off-by: Vinay Kumar 
> > > > > ---
> > > > >  .../glibc/glibc/CVE-2021-33574.patch  | 61
> > > > > +++
> > > > >  meta/recipes-core/glibc/glibc_2.33.bb |  1 +
> > > > >  2 files changed, 62 insertions(+)
> > > > >  create mode 100644 meta/recipes-core/glibc/glibc/CVE-2021-
> > > > > 33574.patch
> > > > >
> > > > > diff --git a/meta/recipes-core/glibc/glibc/CVE-2021-33574.patch
> > > > > b/meta/recipes-core/glibc/glibc/CVE-2021-33574.patch
> > > > > new file mode 100644
> > > > > index 00..fd73b23c88
> > > > > --- /dev/null
> > > > > +++ b/meta/recipes-core/glibc/glibc/CVE-2021-33574.patch
> > > > > @@ -0,0 +1,61 @@
> > > > > +From 42d359350510506b87101cf77202fefcbfc790cb Mon Sep 17 00:00:00
> > > > > 2001
> > > > > +From: Andreas Schwab 
> > > > > +Date: Thu, 27 May 2021 12:49:47 +0200
> > > > > +Subject: [PATCH] Use __pthread_attr_copy in mq_notify (bug 27896)
> > > > > +
> > > > > +Make a deep copy of the pthread attribute object to remove a
> > > > > potential
> > > > > +use-after-free issue.
> > > > > +
> > > > > +Upstream-Status: Backport
> > > > > [
> > > > >
> https://sourceware.org/git/?p=glibc.git;a=commit;h=42d359350510506b87101cf77202fefcbfc790cb
> > > > > ]
> > > > > +CVE: CVE-2021-33574
> > > > > +Signed-off-by: Vinay Kumar 
> > > > > +---
> > > > > +diff --git a/sysdeps/unix/sysv/linux/mq_notify.c
> > > > > b/sysdeps/unix/sysv/linux/mq_notify.c
> > > > > +index cc575a0cdd8..6f46d29d1dc 100644
> > > > > +--- a/sysdeps/unix/sysv/linux/mq_notify.c
> > > > >  b/sysdeps/unix/sysv/linux/mq_notify.c
> > > > > +@@ -133,8 +133,11 @@ helper_thread (void *arg)
> > > > > +   (void) __pthread_barrier_wait (_barrier);
> > > > > +   }
> > > > > +   else if (data.raw[NOTIFY_COOKIE_LEN - 1] == NOTIFY_REMOVED)
> > > > > +-  /* The only state we keep is the copy of the thread
> > > > > attributes.  */
> > > > > +-  free (data.attr);
> > > > > ++  {
> > > > > ++/* The only state we keep is the copy of the thread
>