[OE-core][PATCH v2] bluez5: add dbus to RDEPENDS

2022-10-17 Thread Bartosz Golaszewski 
From: Bartosz Golaszewski 

Unless we're using systemd, dbus is not pulled into the system
automatically. Bluez5 will not work without dbus so add it to RDEPENDS
explicitly.

Signed-off-by: Bartosz Golaszewski 
---
v1 -> v2:
- don't overwrite RDEPENDS, use '+='

 meta/recipes-connectivity/bluez5/bluez5.inc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-connectivity/bluez5/bluez5.inc 
b/meta/recipes-connectivity/bluez5/bluez5.inc
index 79d4645ca8..f07e318897 100644
--- a/meta/recipes-connectivity/bluez5/bluez5.inc
+++ b/meta/recipes-connectivity/bluez5/bluez5.inc
@@ -7,6 +7,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=12f884d2ae1ff87c09e5b7ccc2c4ca7e \
 file://COPYING.LIB;md5=fb504b67c50331fc78734fed90fb0e09 \
 
file://src/main.c;beginline=1;endline=24;md5=0ad83ca0dc37ab08af448777c581e7ac"
 DEPENDS = "dbus glib-2.0"
+RDEPENDS:${PN} += "dbus"
 PROVIDES += "bluez-hcidump"
 RPROVIDES:${PN} += "bluez-hcidump"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171902): 
https://lists.openembedded.org/g/openembedded-core/message/171902
Mute This Topic: https://lists.openembedded.org/mt/94379685/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] grub: Allow build on armv7ve/a with softfp

2022-10-17 Thread Yu, Mingli 

It fails on qemuarm during do_configure.

| checking for compile options to get strict alignment... 
-mno-unaligned-access

| checking if compiler generates unaligned accesses... no
| checking if C symbols get an underscore after compilation... no
| checking whether target compiler is working... no
| configure: error: cannot compile for the target

Thanks,

On 9/15/22 20:59, Andrei Gherzan wrote:

[Please note: This e-mail is from an EXTERNAL e-mail address]

From: Andrei Gherzan 

Grub tries to force the compilation in softfp mode for some known target
CPU. That is because it doesn't use floats or doubles and there are
known limitations of using a configuration with hardfp. There are though
target CPUs that grub won't know how to configure failing with something
similar to:

| checking for options to get soft-float... no
| configure: error: could not force soft-float

This change relaxes a bit the COMPATIBLE_HOST restriction to only apply
for hardfp configuration even for arm7ve/a.

Signed-off-by: Andrei Gherzan 
---
  meta/recipes-bsp/grub/grub2.inc | 10 +++---
  1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-bsp/grub/grub2.inc b/meta/recipes-bsp/grub/grub2.inc
index 47ea561002..e257c31235 100644
--- a/meta/recipes-bsp/grub/grub2.inc
+++ b/meta/recipes-bsp/grub/grub2.inc
@@ -43,9 +43,13 @@ CVE_CHECK_IGNORE += "CVE-2021-46705"

  DEPENDS = "flex-native bison-native gettext-native"

-COMPATIBLE_HOST = 
'(x86_64.*|i.86.*|arm.*|aarch64.*|riscv.*)-(linux.*|freebsd.*)'
-COMPATIBLE_HOST:armv7a = 'null'
-COMPATIBLE_HOST:armv7ve = 'null'
+GRUB_COMPATIBLE_HOST = 
'(x86_64.*|i.86.*|arm.*|aarch64.*|riscv.*)-(linux.*|freebsd.*)'
+COMPATIBLE_HOST = "${GRUB_COMPATIBLE_HOST}"
+# Grub doesn't support hard float toolchain and won't be able to forcefully
+# disable it on some of the target CPUs. See 'configure.ac' for
+# supported/unsupported CPUs in hardfp.
+COMPATIBLE_HOST:armv7a = "${@'null' if d.getVar('TUNE_CCARGS_MFLOAT') == 'hardfp' 
else d.getVar('GRUB_COMPATIBLE_HOST')}"
+COMPATIBLE_HOST:armv7ve = "${@'null' if d.getVar('TUNE_CCARGS_MFLOAT') == 'hardfp' 
else d.getVar('GRUB_COMPATIBLE_HOST')}"

  # configure.ac has code to set this automagically from the target tuple
  # but the OE freeform one (core2-foo-bar-linux) don't work with that.
--
2.25.1






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

[OE-core][kirkstone][PATCH] lttng-modules: Fix crash on powerpc64

2022-10-17 Thread He Zhe 
Backport a patch to fix the following on powerpc64 ABIv2.

root@qemuppc64:~# lttng create trace_session --live -U net://127.0.0.1
Spawning a session daemon
lttng_kretprobes: loading out-of-tree module taints kernel.
BUG: Unable to handle kernel data access on read at 0xfff8
Faulting instruction address: 0xc01f6fd0
Oops: Kernel access of bad area, sig: 11 [#1]


Signed-off-by: He Zhe 
---
 ...4-fix-kernel-crash-caused-by-do_get_.patch | 94 +++
 .../lttng/lttng-modules_2.13.4.bb |  1 +
 2 files changed, 95 insertions(+)
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0001-wrapper-powerpc64-fix-kernel-crash-caused-by-do_get_.patch

diff --git 
a/meta/recipes-kernel/lttng/lttng-modules/0001-wrapper-powerpc64-fix-kernel-crash-caused-by-do_get_.patch
 
b/meta/recipes-kernel/lttng/lttng-modules/0001-wrapper-powerpc64-fix-kernel-crash-caused-by-do_get_.patch
new file mode 100644
index 00..b3b191c7ac
--- /dev/null
+++ 
b/meta/recipes-kernel/lttng/lttng-modules/0001-wrapper-powerpc64-fix-kernel-crash-caused-by-do_get_.patch
@@ -0,0 +1,94 @@
+From 480cce4315ce5bf59a509e8a53a52545f393de68 Mon Sep 17 00:00:00 2001
+From: He Zhe 
+Date: Tue, 27 Sep 2022 15:59:42 +0800
+Subject: [PATCH] wrapper: powerpc64: fix kernel crash caused by
+ do_get_kallsyms
+
+Kernel crashes on powerpc64 ABIv2 as follow when lttng_tracer initializes,
+since do_get_kallsyms in lttng_wrapper fails to return a proper address of
+kallsyms_lookup_name.
+
+root@qemuppc64:~# lttng create trace_session --live -U net://127.0.0.1
+Spawning a session daemon
+lttng_kretprobes: loading out-of-tree module taints kernel.
+BUG: Unable to handle kernel data access on read at 0xfff8
+Faulting instruction address: 0xc01f6fd0
+Oops: Kernel access of bad area, sig: 11 [#1]
+
+NIP [c01f6fd0] module_kallsyms_lookup_name+0xf0/0x180
+LR [c01f6f28] module_kallsyms_lookup_name+0x48/0x180
+Call Trace:
+module_kallsyms_lookup_name+0x34/0x180 (unreliable)
+kallsyms_lookup_name+0x258/0x2b0
+wrapper_kallsyms_lookup_name+0x4c/0xd0 [lttng_wrapper]
+wrapper_get_pfnblock_flags_mask_init+0x28/0x60 [lttng_wrapper]
+lttng_events_init+0x40/0x344 [lttng_tracer]
+do_one_initcall+0x78/0x340
+do_init_module+0x6c/0x2f0
+__do_sys_finit_module+0xd0/0x120
+system_call_exception+0x194/0x2f0
+system_call_vectored_common+0xe8/0x278
+
+
+do_get_kallsyms makes use of kprobe_register and in turn kprobe_lookup_name
+to get the address of the kernel function kallsyms_lookup_name. In case of
+PPC64_ELF_ABI_v2, when kprobes are placed at function entry,
+kprobe_lookup_name adjusts the global entry point of the function returned
+by kallsyms_lookup_name to the local entry point(at some fixed offset of
+global one). This adjustment is all for kprobes to be able to work properly.
+Global and local entry point are defined in powerpc64 ABIv2.
+
+When the local entry point is given, some instructions at the beginning of
+the function are skipped and thus causes the above kernel crash. We just
+want to make a simple function call which needs global entry point.
+
+This patch adds 4 bytes which is the length of one instruction to
+kallsyms_lookup_name so that it will not trigger the global to local
+adjustment, and then substracts 4 bytes from the returned address. See the
+following kernel change for more details.
+
+https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=290e3070762ac80e5fc4087d8c4de7e3f1d90aca
+
+Upstream-Status: Backport
+
+Signed-off-by: He Zhe 
+Signed-off-by: Mathieu Desnoyers 
+Change-Id: I34e68e886b97e3976d0b5e25be295a8bb866c1a4
+---
+ src/wrapper/kallsyms.c | 16 
+ 1 file changed, 16 insertions(+)
+
+diff --git a/src/wrapper/kallsyms.c b/src/wrapper/kallsyms.c
+index d2848764..93017adc 100644
+--- a/src/wrapper/kallsyms.c
 b/src/wrapper/kallsyms.c
+@@ -39,10 +39,26 @@ unsigned long do_get_kallsyms(void)
+   memset(&probe, 0, sizeof(probe));
+   probe.pre_handler = dummy_kprobe_handler;
+   probe.symbol_name = "kallsyms_lookup_name";
++#ifdef PPC64_ELF_ABI_v2
++  /*
++   * With powerpc64 ABIv2, we need the global entry point of
++   * kallsyms_lookup_name to call it later, while kprobe_register would
++   * automatically adjust the global entry point to the local entry point,
++   * when a kprobe was registered at a function entry. So we add 4 bytes
++   * which is the length of one instruction to kallsyms_lookup_name to
++   * avoid the adjustment.
++   */
++  probe.offset = 4;
++#endif
+   ret = register_kprobe(&probe);
+   if (ret)
+   return 0;
++#ifdef PPC64_ELF_ABI_v2
++  /* Substract 4 bytes to get what we originally want */
++  addr = (unsigned long)(((char *)probe.addr) - 4);
++#else
+   addr = (unsigned long)probe.addr;
++#endif
+ #ifdef CONFIG_ARM
+ #ifdef CONFIG_THUMB2_KERNEL
+   if (addr)
+-- 
+2.17.1
+
diff --git a/meta/recipes-kernel/lttng/lt

[OE-core] [PATCH] btrfs-tools: upgrade 5.19.1 -> 6.0

2022-10-17 Thread wangmy 
Changelog:
==
  * fi usage: in tabular output, print total size and slack size
   * mkfs:
  * option -O now accepts values from -R to unify the interface (-R will
continue to work)
  * zone reset and discard is done in parallel on all devices
  * removed option --leafsize, deprecated long time ago
   * corrupt-block: recalculate checksum when changing generation
   * fixes:
  * convert: fix reserved range detection and overlaps
  * mkfs: fix creating files with reserved inode numbers with --rootdir
  * receive: escape filenames in command attributes
  * fix extent buffer leaks after transaction abort
   * experimental:
  * mkfs: support for block-group-tree (kernel 6.1)
  * fsverity in send (protocol v3, WIP)
  * btrfstune -b converts to block-group-tree
   * other:
  * cleanups, refactoring
  * new and updated tests
  * update documentation

Signed-off-by: Wang Mingyu 
---
 .../btrfs-tools/{btrfs-tools_5.19.1.bb => btrfs-tools_6.0.bb}   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/btrfs-tools/{btrfs-tools_5.19.1.bb => 
btrfs-tools_6.0.bb} (98%)

diff --git a/meta/recipes-devtools/btrfs-tools/btrfs-tools_5.19.1.bb 
b/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.0.bb
similarity index 98%
rename from meta/recipes-devtools/btrfs-tools/btrfs-tools_5.19.1.bb
rename to meta/recipes-devtools/btrfs-tools/btrfs-tools_6.0.bb
index db8026e0f0..887a530a52 100644
--- a/meta/recipes-devtools/btrfs-tools/btrfs-tools_5.19.1.bb
+++ b/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.0.bb
@@ -18,7 +18,7 @@ DEPENDS = "util-linux zlib"
 SRC_URI = 
"git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git;branch=master
 \

file://0001-Add-a-possibility-to-specify-where-python-modules-ar.patch \
"
-SRCREV = "e1d9dab326e043696e6648aba4ccf90874d1d3d1"
+SRCREV = "3db756352685f38c1de0aa886d380c733e0f53e7"
 S = "${WORKDIR}/git"
 
 PACKAGECONFIG ??= " \
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171905): 
https://lists.openembedded.org/g/openembedded-core/message/171905
Mute This Topic: https://lists.openembedded.org/mt/94381986/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] vulkan-loader: Move libvulkan.so to main package

2022-10-17 Thread Ross Burton 
On 16 Oct 2022, at 22:43, Tom Hochstein via lists.openembedded.org 
 wrote:
> 
> Since libvulkan.so is commonly loaded dynamically, put it in the main
> package.

Can you give an example?

Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171906): 
https://lists.openembedded.org/g/openembedded-core/message/171906
Mute This Topic: https://lists.openembedded.org/mt/94372555/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] vulkan-samples: enable network during do_unpack

2022-10-17 Thread Martin Jansa 
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14938

On Thu, Aug 18, 2022 at 10:00 PM Alexander Kanavin 
wrote:

> The ticket is RESOLVED/FIXED, which is surely not the case here?
>
> Alex
>
> On Thu, 18 Aug 2022 at 21:45, Martin Jansa  wrote:
> >
> > There is ticket about this already, see
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=14283
> >
> > On Thu, Aug 18, 2022 at 9:02 AM Julien STEPHAN 
> wrote:
> >>
> >>
> >>
> >> Le mer. 17 août 2022 à 22:33, Alexander Kanavin 
> a écrit :
> >>>
> >>> I reproduced. This happens if all three are true:
> >>> - recipe is using gitsm://
> >>> - one of the submodules contains lfs objects
> >>> - git-lfs is installed on the host (that's why it's not seen on the AB)
> >>>
> >> Nice! I figured out the first two points, but not the last one.
> >>
> >>>
> >>> There's logic in plain git:// fetcher to deal with lfs, but not in
> >>> gitsm://. So that logic needs to be added there as well. A workaround
> >>> like you suggested is not the right fix.
> >>>
> >>> Can you look into it please? Or at least a ticket would be good to
> have.
> >>>
> >> Sure, I will try to look at it
> >> Julien
> >>>
> >>> Alex
> >>>
> >>> On Wed, 17 Aug 2022 at 21:42, Alexander Kanavin via
> >>> lists.openembedded.org 
> >>> wrote:
> >>> >
> >>> > Just to be sure, can you repeat this on a pristine poky master
> >>> > checkout with no cache and no downloads? 'bitbake -c unpack
> >>> > vulkan-samples' should do.
> >>> >
> >>> > Also what does git --version say? I wonder if there's something in
> too
> >>> > old or too new versions of it.
> >>> >
> >>> > Alex
> >>> >
> >>> > On Wed, 17 Aug 2022 at 21:22, Julien Stephan 
> wrote:
> >>> > >
> >>> > > Hi Alexander,
> >>> > >
> >>> > > I observe this by just trying to build the vulkan-samples recipe:
> DISTRO=poky bitbake vulkan-samples.
> >>> > >
> >>> > > Here is the log output (sorry it is a bit verbose):
> >>> > > ERROR: vulkan-samples-git-r0 do_unpack: Bitbake Fetcher Error:
> FetchError('Fetch command export PSEUDO_DISABLED=1; export
> SSH_AUTH_SOCK="/home/jstephan/.ssh/ssh_auth_sock"; export
> PATH="/home/jstephan/kirkstone/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/jstephan/kirkstone/src/poky/scripts:/home/jstephan/kirkstone/build/tmp/work/cortexa53-poky-linux/vulkan-samples/git-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux:/home/jstephan/kirkstone/build/tmp/work/cortexa53-poky-linux/vulkan-samples/git-r0/recipe-sysroot/usr/bin/crossscripts:/home/jstephan/kirkstone/build/tmp/work/cortexa53-poky-linux/vulkan-samples/git-r0/recipe-sysroot-native/usr/sbin:/home/jstephan/kirkstone/build/tmp/work/cortexa53-poky-linux/vulkan-samples/git-r0/recipe-sysroot-native/usr/bin:/home/jstephan/kirkstone/build/tmp/work/cortexa53-poky-linux/vulkan-samples/git-r0/recipe-sysroot-native/sbin:/home/jstephan/kirkstone/build/tmp/work/cortexa53-poky-linux/vulkan-samples/git-r0/recipe-sysroot-native/bin:/home/jstephan/kirkstone/src/poky/bitbake/bin:/home/jstephan/kirkstone/build/tmp/hosttools";
> export HOME="/home/jstephan"; git -c core.fsyncobjectfiles=0 -c
> gc.autoDetach=false -c core.pager=cat submodule update --recursive
> --no-fetch failed with exit code 1, output:\nSubmodule path \'assets\':
> checked out \'8a6b7f952d7786a305f89d375a55598e995ee972\'\nSubmodule path
> \'third_party/CTPL\': checked out
> \'437e135dbd94eb65b45533d9ce8ee28b5bd37b6d\'\nSubmodule path
> \'third_party/astc\': checked out
> \'4861c3db1ca50eb5f5767d95d1cd1bacb98ac8a5\'\nSubmodule path
> \'third_party/cli11\': checked out
> \'4af78beef777e313814b4daff70e2da9171a385a\'\nSubmodule path
> \'third_party/glfw\': checked out
> \'6876cf8d7e0e70dc3e4d7b0224d08312c9f78099\'\nSubmodule path
> \'third_party/glm\': checked out
> \'fce2abd01ce21063bd25ba67c9318be83bf48813\'\nSubmodule path
> \'third_party/glslang\': checked out
> \'6baa85f6ceec5fddd2e13b43dd1edc944dd930af\'\nSubmodule path
> \'third_party/hwcpipe\': checked out
> \'5a0c3d0b527bea96154998f29177f3b449cebd3a\'\nSubmodule path
> \'third_party/imgui\': checked out
> \'c23a19c26fa9cc778f755e76799f0cafdcb5a13b\'\nSubmodule path
> \'third_party/opencl\': checked out
> \'1aa1139b58a515877a923cce6b254e09d1b2fb2c\'\nSubmodule path
> \'third_party/spdlog\': checked out
> \'7bf8f148795d2571b4ae4aa9c6d2a8111fbb7077\'\nSubmodule path
> \'third_party/spirv-cross\': checked out
> \'84f56d0b43e5a6874de45e11be2bff9dc336fd7e\'\nSubmodule path
> \'third_party/stb\': checked out
> \'2c2908f50515dcd939f24be261c3ccbcd277bb49\'\nSubmodule path
> \'third_party/tinygltf\': checked out
> \'c0d0251e2c7f2273a894aa1b125af9313a88eae4\'\nSubmodule path
> \'third_party/vma\': checked out
> \'f9921aefddee2437cc2e3303d3175bd8ef23e22c\'\nSubmodule path
> \'third_party/volk\': checked out
> \'b18f3192886981f28d17f8f41c26c5a53ac3b977\'\nSubmodule path
> \'third_party/vulkan\': checked out
> \'76f00ef6cbb1886eb1162d1fa39bee8b51e22ee8\'\n\nDownloading
> other_lib/ios/Debug-iphoneos/libSDL2.a (8.2 MB)\nError downloading object:
> other_lib/ios/Deb

Re: [OE-core] [PATCH] vulkan-loader: Move libvulkan.so to main package

2022-10-17 Thread Martin Jansa 
On Mon, Oct 17, 2022 at 2:10 PM Ross Burton  wrote:

> On 16 Oct 2022, at 22:43, Tom Hochstein via lists.openembedded.org
>  wrote:
> >
> > Since libvulkan.so is commonly loaded dynamically, put it in the main
> > package.
>
> Can you give an example?
>

I'm wondering the same, because e.g.  tensorflow-lite. arm-compute-library
were also trying to dlopen libOpenCL.so and we've patched them to
dlopen libOpenCL.so.1 instead, so why should libvulkan.so be different.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171908): 
https://lists.openembedded.org/g/openembedded-core/message/171908
Mute This Topic: https://lists.openembedded.org/mt/94372555/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/3] zlib: do out-of-tree builds

2022-10-17 Thread Ross Burton 
zlib supports out-of-tree builds, so do them.

Signed-off-by: Ross Burton 
---
 meta/recipes-core/zlib/zlib_1.2.12.bb | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-core/zlib/zlib_1.2.12.bb 
b/meta/recipes-core/zlib/zlib_1.2.12.bb
index 2491cb941f5..9ec78b95be0 100644
--- a/meta/recipes-core/zlib/zlib_1.2.12.bb
+++ b/meta/recipes-core/zlib/zlib_1.2.12.bb
@@ -30,9 +30,12 @@ RDEPENDS:${PN}-ptest += "make"
 
 inherit ptest
 
+B = "${WORKDIR}/build"
+
 do_configure() {
-   LDCONFIG=true ./configure --prefix=${prefix} --shared 
--libdir=${libdir} --uname=GNU
+   LDCONFIG=true ${S}/configure --prefix=${prefix} --shared 
--libdir=${libdir} --uname=GNU
 }
+do_configure[cleandirs] += "${B}"
 
 do_compile() {
oe_runmake shared
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171910): 
https://lists.openembedded.org/g/openembedded-core/message/171910
Mute This Topic: https://lists.openembedded.org/mt/94384122/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/3] zlib: upgrade 1.2.12 -> 1.2.13

2022-10-17 Thread Ross Burton 
Drop a number of patches whicih have been merged upstream.

Signed-off-by: Ross Burton 
---
 ...t-inputs-provided-to-the-CRC-functio.patch | 54 ---
 ...etting-a-gzip-header-extra-field-wit.patch | 38 -
 ...processing-bug-that-dereferences-NUL.patch | 36 -
 meta/recipes-core/zlib/zlib/cc.patch  | 27 --
 .../zlib/zlib/ldflags-tests.patch | 45 
 .../zlib/{zlib_1.2.12.bb => zlib_1.2.13.bb}   |  7 +--
 6 files changed, 1 insertion(+), 206 deletions(-)
 delete mode 100644 
meta/recipes-core/zlib/zlib/0001-Correct-incorrect-inputs-provided-to-the-CRC-functio.patch
 delete mode 100644 
meta/recipes-core/zlib/zlib/0001-Fix-a-bug-when-getting-a-gzip-header-extra-field-wit.patch
 delete mode 100644 
meta/recipes-core/zlib/zlib/0001-Fix-extra-field-processing-bug-that-dereferences-NUL.patch
 delete mode 100644 meta/recipes-core/zlib/zlib/cc.patch
 delete mode 100644 meta/recipes-core/zlib/zlib/ldflags-tests.patch
 rename meta/recipes-core/zlib/{zlib_1.2.12.bb => zlib_1.2.13.bb} (75%)

diff --git 
a/meta/recipes-core/zlib/zlib/0001-Correct-incorrect-inputs-provided-to-the-CRC-functio.patch
 
b/meta/recipes-core/zlib/zlib/0001-Correct-incorrect-inputs-provided-to-the-CRC-functio.patch
deleted file mode 100644
index ad5e59de040..000
--- 
a/meta/recipes-core/zlib/zlib/0001-Correct-incorrect-inputs-provided-to-the-CRC-functio.patch
+++ /dev/null
@@ -1,54 +0,0 @@
-From ec3df00224d4b396e2ac6586ab5d25f673caa4c2 Mon Sep 17 00:00:00 2001
-From: Mark Adler 
-Date: Wed, 30 Mar 2022 11:14:53 -0700
-Subject: [PATCH] Correct incorrect inputs provided to the CRC functions.
-
-The previous releases of zlib were not sensitive to incorrect CRC
-inputs with bits set above the low 32. This commit restores that
-behavior, so that applications with such bugs will continue to
-operate as before.
-
-Upstream-Status: Backport 
[https://github.com/madler/zlib/commit/ec3df00224d4b396e2ac6586ab5d25f673caa4c2]
-Signed-off-by: Jacob Kroon 

- crc32.c | 8 
- 1 file changed, 4 insertions(+), 4 deletions(-)
-
-diff --git a/crc32.c b/crc32.c
-index a1bdce5..451887b 100644
 a/crc32.c
-+++ b/crc32.c
-@@ -630,7 +630,7 @@ unsigned long ZEXPORT crc32_z(crc, buf, len)
- #endif /* DYNAMIC_CRC_TABLE */
- 
- /* Pre-condition the CRC */
--crc ^= 0x;
-+crc = (~crc) & 0x;
- 
- /* Compute the CRC up to a word boundary. */
- while (len && ((z_size_t)buf & 7) != 0) {
-@@ -749,7 +749,7 @@ unsigned long ZEXPORT crc32_z(crc, buf, len)
- #endif /* DYNAMIC_CRC_TABLE */
- 
- /* Pre-condition the CRC */
--crc ^= 0x;
-+crc = (~crc) & 0x;
- 
- #ifdef W
- 
-@@ -1077,7 +1077,7 @@ uLong ZEXPORT crc32_combine64(crc1, crc2, len2)
- #ifdef DYNAMIC_CRC_TABLE
- once(&made, make_crc_table);
- #endif /* DYNAMIC_CRC_TABLE */
--return multmodp(x2nmodp(len2, 3), crc1) ^ crc2;
-+return multmodp(x2nmodp(len2, 3), crc1) ^ (crc2 & 0x);
- }
- 
- /* = 
*/
-@@ -1112,5 +1112,5 @@ uLong crc32_combine_op(crc1, crc2, op)
- uLong crc2;
- uLong op;
- {
--return multmodp(op, crc1) ^ crc2;
-+return multmodp(op, crc1) ^ (crc2 & 0x);
- }
diff --git 
a/meta/recipes-core/zlib/zlib/0001-Fix-a-bug-when-getting-a-gzip-header-extra-field-wit.patch
 
b/meta/recipes-core/zlib/zlib/0001-Fix-a-bug-when-getting-a-gzip-header-extra-field-wit.patch
deleted file mode 100644
index 96ab563121c..000
--- 
a/meta/recipes-core/zlib/zlib/0001-Fix-a-bug-when-getting-a-gzip-header-extra-field-wit.patch
+++ /dev/null
@@ -1,38 +0,0 @@
-From eff308af425b67093bab25f80f1ae950166bece1 Mon Sep 17 00:00:00 2001
-From: Mark Adler 
-Date: Sat, 30 Jul 2022 15:51:11 -0700
-Subject: [PATCH] Fix a bug when getting a gzip header extra field with 
inflate().
-
-If the extra field was larger than the space the user provided with
-inflateGetHeader(), and if multiple calls of inflate() delivered
-the extra header data, then there could be a buffer overflow of the
-provided space. This commit assures that provided space is not
-exceeded.
-
-CVE: CVE-2022-37434
-Upstream-Status: Backport 
[https://github.com/madler/zlib/commit/eff308af425b67093bab25f80f1ae950166be]
-Signed-off-by: Khem Raj 

- inflate.c | 5 +++--
- 1 file changed, 3 insertions(+), 2 deletions(-)
-
-diff --git a/inflate.c b/inflate.c
-index 7be8c63..7a72897 100644
 a/inflate.c
-+++ b/inflate.c
-@@ -763,9 +763,10 @@ int flush;
- copy = state->length;
- if (copy > have) copy = have;
- if (copy) {
-+len = state->head->extra_len - state->length;
- if (state->head != Z_NULL &&
--state->head->extra != Z_NULL) {
--len = state->head->extra_len - state->length;
-+state->head->extra != Z_NULL &&
-+len < state->hea

[OE-core] [PATCH 1/3] zlib: use .gz archive and set a PREMIRROR

2022-10-17 Thread Ross Burton 
When a new zlib release is made, the top-level URL is no longer available
and it is only available as a .gz under the /fossils/ directory.

When this happens the source fetch fails and bitbake noisily warns that
it is using the mirrors.  Avoid this by using the .gz tarball and add
the /fossils/ directory to PREMIRRORS so fetches will check there too.

Signed-off-by: Ross Burton 
---
 meta/recipes-core/zlib/zlib_1.2.12.bb | 9 +++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-core/zlib/zlib_1.2.12.bb 
b/meta/recipes-core/zlib/zlib_1.2.12.bb
index b999f13530e..2491cb941f5 100644
--- a/meta/recipes-core/zlib/zlib_1.2.12.bb
+++ b/meta/recipes-core/zlib/zlib_1.2.12.bb
@@ -6,7 +6,8 @@ SECTION = "libs"
 LICENSE = "Zlib"
 LIC_FILES_CHKSUM = 
"file://zlib.h;beginline=6;endline=23;md5=5377232268e952e9ef63bc555f7aa6c0"
 
-SRC_URI = "https://zlib.net/${BP}.tar.xz \
+# The source tarball needs to be .gz as only the .gz ends up in fossils/
+SRC_URI = "https://zlib.net/${BP}.tar.gz \
file://cc.patch \
file://ldflags-tests.patch \
file://0001-configure-Pass-LDFLAGS-to-link-tests.patch \
@@ -17,7 +18,11 @@ SRC_URI = "https://zlib.net/${BP}.tar.xz \
"
 UPSTREAM_CHECK_URI = "http://zlib.net/";
 
-SRC_URI[sha256sum] = 
"7db46b8d7726232a621befaab4a1c870f00a90805511c0e0090441dac57def18"
+SRC_URI[sha256sum] = 
"91844808532e5ce316b3c010929493c0244f3d37593afd6de04f71821d5136d9"
+
+# When a new release is made the previous release is moved to fossils/, so add 
this
+# to PREMIRRORS so it is also searched automatically.
+PREMIRRORS:append = " https://zlib.net/ https://zlib.net/fossils/";
 
 CFLAGS += "-D_REENTRANT"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171909): 
https://lists.openembedded.org/g/openembedded-core/message/171909
Mute This Topic: https://lists.openembedded.org/mt/94384120/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] vulkan-samples: add lfs=0 to SRC_URI to avoid git smudge errors in do_unpack

2022-10-17 Thread Martin Jansa 
* we don't need other_lib/ios/Debug-iphoneos/libSDL2.a from
  https://github.com/KhronosGroup/KTX-Software.git so we can explicitly
  disable LFS here to avoid do_unpack error, bitbake will then use
  GIT_LFS_SKIP_SMUDGE=1 to override smudge setting in gitconfig,
  otherwise we would need bitbake patch to fetch LFS objects from the
  submodules as well

* do_fetch won't fetch LFS objects without explicitly requesting lfs in SRC_URI
  then do_unpack might run git smudge when enabled in .gitconfig (or 
/etc/gitconfig) with:

[filter "lfs"]
   smudge = git-lfs smudge -- %f
   process = git-lfs filter-process
   required = true
   clean = git-lfs clean -- %f

  and do_unpack fails as in:
  http://errors.yoctoproject.org/Errors/Details/672888/

The default /etc/gitconfig in ubuntu has this added automatically by
git-lfs postinst:

  root@ljama:~# rm /etc/gitconfig
  root@ljama:~# git lfs install --skip-repo --system
  Git LFS initialized.
  root@ljama:~# cat /etc/gitconfig
  [filter "lfs"]
clean = git-lfs clean -- %f
smudge = git-lfs smudge -- %f
process = git-lfs filter-process
required = true
  root@ljama:~# cat /var/lib/dpkg/info/git-lfs.postinst

  set -e

  # Set up /etc/gitconfig for git-lfs. The --skip-repo option prevents failure 
if
  # / is a Git repository with existing non-git-lfs hooks.

  git lfs install --skip-repo --system > /dev/null 2>&1

according to
https://changelogs.ubuntu.com/changelogs/pool/universe/g/git-lfs/git-lfs_3.0.2-1/changelog
it was added in:

git-lfs (2.6.0-1) unstable; urgency=medium

  * New upstream release
  * Bump standards version to 4.2.1
  * Add postinst/prerm to set up/remove git-lfs gitconfig

FWIW: vulkan-samples still fail to build with DEBUG_BUILD enabled:
http://errors.yoctoproject.org/Errors/Details/672892/

Signed-off-by: Martin Jansa 
---
 meta/recipes-graphics/vulkan/vulkan-samples_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-graphics/vulkan/vulkan-samples_git.bb 
b/meta/recipes-graphics/vulkan/vulkan-samples_git.bb
index 332411b312..d0b3458e1b 100644
--- a/meta/recipes-graphics/vulkan/vulkan-samples_git.bb
+++ b/meta/recipes-graphics/vulkan/vulkan-samples_git.bb
@@ -5,7 +5,7 @@ LICENSE = "Apache-2.0"
 
 LIC_FILES_CHKSUM = "file://LICENSE;md5=48aa35cefb768436223a6e7f18dc2a2a"
 
-SRC_URI = 
"gitsm://github.com/KhronosGroup/Vulkan-Samples.git;branch=master;protocol=https
 \
+SRC_URI = 
"gitsm://github.com/KhronosGroup/Vulkan-Samples.git;branch=master;protocol=https;lfs=0
 \

file://0001-CMakeLists.txt-do-not-hardcode-lib-as-installation-t.patch \
file://debugfix.patch \

file://0001-Qualify-move-as-std-move.patch;patchdir=third_party/spirv-cross \
-- 
2.38.0


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

[OE-core] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2022-10-17 Thread Stephen Jolley 
All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:

https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 419
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now,  "4.1", "4.2", "4.3", "4.99" and "Future", the more
pressing/urgent issues being in "4.1" and then "4.2".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171913): 
https://lists.openembedded.org/g/openembedded-core/message/171913
Mute This Topic: https://lists.openembedded.org/mt/94386965/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] linux-firmware: split rtl8761 firmware

2022-10-17 Thread Christian Eggers 
Realtek Bluetooth devices require binary firmware files. Package them
separately in order to avoid installing the full linux-firmware package
on embedded devices.

Affected (end user) products (incomplete list):
- TP-Link UB500
- Logilink BT0054

Signed-off-by: Christian Eggers 
---
 .../linux-firmware/linux-firmware_20220913.bb   | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/meta/recipes-kernel/linux-firmware/linux-firmware_20220913.bb 
b/meta/recipes-kernel/linux-firmware/linux-firmware_20220913.bb
index 45c9d0e86123..eea9251a840e 100644
--- a/meta/recipes-kernel/linux-firmware/linux-firmware_20220913.bb
+++ b/meta/recipes-kernel/linux-firmware/linux-firmware_20220913.bb
@@ -235,6 +235,7 @@ PACKAGES =+ "${PN}-ralink-license ${PN}-ralink \
  ${PN}-vt6656-license ${PN}-vt6656 \
  ${PN}-rs9113 ${PN}-rs9116 \
  ${PN}-rtl-license ${PN}-rtl8188 ${PN}-rtl8192cu ${PN}-rtl8192ce 
${PN}-rtl8192su ${PN}-rtl8723 ${PN}-rtl8821 \
+ ${PN}-rtl8761 \
  ${PN}-rtl8168 \
  ${PN}-cypress-license \
  ${PN}-broadcom-license \
@@ -563,6 +564,7 @@ LICENSE:${PN}-rtl8192cu = "Firmware-rtlwifi_firmware"
 LICENSE:${PN}-rtl8192ce = "Firmware-rtlwifi_firmware"
 LICENSE:${PN}-rtl8192su = "Firmware-rtlwifi_firmware"
 LICENSE:${PN}-rtl8723 = "Firmware-rtlwifi_firmware"
+LICENSE:${PN}-rtl8761 = "Firmware-rtlwifi_firmware"
 LICENSE:${PN}-rtl8821 = "Firmware-rtlwifi_firmware"
 LICENSE:${PN}-rtl-license = "Firmware-rtlwifi_firmware"
 LICENSE:${PN}-rtl8168 = "WHENCE"
@@ -588,6 +590,9 @@ FILES:${PN}-rtl8723 = " \
 FILES:${PN}-rtl8821 = " \
   ${nonarch_base_libdir}/firmware/rtlwifi/rtl8821*.bin \
 "
+FILES:${PN}-rtl8761 = " \
+  ${nonarch_base_libdir}/firmware/rtl_bt/rtl8761*.bin \
+"
 FILES:${PN}-rtl8168 = " \
   ${nonarch_base_libdir}/firmware/rtl_nic/rtl8168*.fw \
 "
@@ -598,6 +603,7 @@ RDEPENDS:${PN}-rtl8192cu += "${PN}-rtl-license"
 RDEPENDS:${PN}-rtl8192su = "${PN}-rtl-license"
 RDEPENDS:${PN}-rtl8723 += "${PN}-rtl-license"
 RDEPENDS:${PN}-rtl8821 += "${PN}-rtl-license"
+RDEPENDS:${PN}-rtl8761 += "${PN}-rtl-license"
 RDEPENDS:${PN}-rtl8168 += "${PN}-whence-license"
 
 # For ti-connectivity
-- 
2.35.3


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171914): 
https://lists.openembedded.org/g/openembedded-core/message/171914
Mute This Topic: https://lists.openembedded.org/mt/94387658/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] vulkan-loader: Move libvulkan.so to main package

2022-10-17 Thread Tom Hochstein 
I found a few examples online for both ways. In SaschaWillems examples, .so is 
used:

https://github.com/SaschaWillems/Vulkan/blob/master/base/VulkanAndroid.cpp#L142

In Vulkan-Tools there's a mix. Here the implementation falls back to .so.1 if 
.so is not found:

https://github.com/KhronosGroup/Vulkan-Tools/blob/master/vulkaninfo/vulkaninfo.h#L256-L257

While here only .so is used:

https://github.com/KhronosGroup/Vulkan-Tools/blob/master/common/vulkan_wrapper.cpp#L25
https://github.com/KhronosGroup/Vulkan-Tools/blob/master/scripts/generate_vulkan_wrapper.py#L2043

With no consistency or guidance I'm not sure what the right solution is. At 
first I thought perhaps it is better for the caller to be more specific so that 
a compatibility problem is detected with a dlopen failure. Complicating that, 
though, is that vulkan-loader 1.2 is not compatible with 1.3. Plus why does 
Vulkan-Tools use .so.1 second? Probably to get around the fact that the .so is 
in the dev package?

Is it possible and/or reasonable for a binary to load the .so then check the 
version and handle that at runtime? If so, then including the .so in the main 
package makes sense. Or should the user in this case be expected to use 
RDEPENDS to install the .so?

From: Martin Jansa 
Sent: Monday, October 17, 2022 7:29 AM
To: Ross Burton 
Cc: Tom Hochstein ; 
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] vulkan-loader: Move libvulkan.so to main package


On Mon, Oct 17, 2022 at 2:10 PM Ross Burton 
mailto:ross.bur...@arm.com>> wrote:
On 16 Oct 2022, at 22:43, Tom Hochstein via 
lists.openembedded.org
 
mailto:nxp@lists.openembedded.org>>
 wrote:
>
> Since libvulkan.so is commonly loaded dynamically, put it in the main
> package.

Can you give an example?

I'm wondering the same, because e.g.  tensorflow-lite. arm-compute-library were 
also trying to dlopen libOpenCL.so and we've patched them to dlopen 
libOpenCL.so.1 instead, so why should libvulkan.so be different.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171915): 
https://lists.openembedded.org/g/openembedded-core/message/171915
Mute This Topic: https://lists.openembedded.org/mt/94372555/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] go-mod.bbclass: Remove repeated word

2022-10-17 Thread Fabio Estevam 
The word 'the' appears repeatedly. Remove one occurrence.

Signed-off-by: Fabio Estevam 
---
 meta/classes-recipe/go-mod.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes-recipe/go-mod.bbclass 
b/meta/classes-recipe/go-mod.bbclass
index 927746a338be..61571596bcfa 100644
--- a/meta/classes-recipe/go-mod.bbclass
+++ b/meta/classes-recipe/go-mod.bbclass
@@ -6,7 +6,7 @@
 
 # Handle Go Modules support
 #
-# When using Go Modules, the the current working directory MUST be at or below
+# When using Go Modules, the current working directory MUST be at or below
 # the location of the 'go.mod' file when the go tool is used, and there is no
 # way to tell it to look elsewhere.  It will automatically look upwards for the
 # file, but not downwards.
-- 
2.25.1


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

[OE-core] Yocto Project Summit: 2011.11

2022-10-17 Thread Armin Kuster 

Hello,

This is a reminder that the Yocto Project Summit is scheduled for 
November 29th to December. Registration is open.


The CFP still open and will close in 12 days from now on Oct 28th.


For more information see: 
https://www.yoctoproject.org/yocto-project-summit-2022-11/


regards,
Armin

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

[OE-core][kirkstone 00/13] Patch review

2022-10-17 Thread Steve Sakoman 
Please review this set of patches for kirkstone and have comments back by
end of day Wednesday.

Passed a-full on autobuilder:

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

The following changes since commit e728d0965d6fda8ac54e065ca7bf7eb9da9a8170:

  coreutils: add openssl PACKAGECONFIG (2022-09-30 09:35:23 -1000)

are available in the Git repository at:

  https://git.openembedded.org/openembedded-core-contrib stable/kirkstone-nut
  
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/kirkstone-nut

Adrian Freihofer (1):
  own-mirrors: add crate

Bhabu Bindu (1):
  qemu: Fix CVE-2021-3611

Chen Qi (1):
  image_types_wic.bbclass: fix cross binutils dependency

He Zhe (2):
  lttng-tools: Upgrade 2.13.4 -> 2.13.8
  lttng-modules: Fix crash on powerpc64

Michael Halstead (1):
  uninative: Upgrade to 3.7 to work with glibc 2.36

Ross Burton (1):
  qemu: fix CVE-2022-2962

Teoh Jay Shen (1):
  tiff: Security fixes CVE-2022-2867,CVE-2022-2868 and CVE-2022-2869

Tim Orling (1):
  python3: upgrade 3.10.4 -> 3.10.7

Virendra Thakur (1):
  qemu: Fix CVE-2021-3750 for qemu

Xiangyu Chen (2):
  qemu: Backport patches from upstream to support float128 on qemu-ppc64
  linux-yocto-dev: add qemuarm64

pgowda (1):
  binutils : Fix CVE-2022-38128

 meta/classes/image_types_wic.bbclass  |2 +-
 meta/classes/own-mirrors.bbclass  |1 +
 meta/classes/sanity.bbclass   |2 +-
 meta/conf/distro/include/yocto-uninative.inc  |   10 +-
 .../binutils/binutils-2.38.inc|3 +
 .../binutils/0018-CVE-2022-38128-1.patch  |  350 
 .../binutils/0018-CVE-2022-38128-2.patch  |  436 +
 .../binutils/0018-CVE-2022-38128-3.patch  |   95 ++
 ...h-92036-Fix-gc_fini_untrack-GH-92037.patch |   54 -
 ...report-missing-dependencies-for-disa.patch |8 +-
 .../{python3_3.10.4.bb => python3_3.10.7.bb}  |3 +-
 meta/recipes-devtools/qemu/qemu.inc   |   49 +
 ...ulip-Restrict-DMA-engine-to-memories.patch |   64 +
 ...end-float_exception_flags-to-16-bits.patch |   75 +
 ...32t-for-reply-queue-head-tail-values.patch |   83 +
 ...ftfloat-Add-flag-specific-to-Inf-Inf.patch |   59 +
 ...id_function_take_MemTxAttrs_argument.patch |   60 +
 ...softfloat-Add-flag-specific-to-Inf-0.patch |  126 ++
 ...et_function_take_MemTxAttrs_argument.patch |   98 ++
 ...dd-flags-specific-to-Inf-Inf-and-0-0.patch |   73 +
 ...ed_function_take_MemTxAttrs_argument.patch |   78 +
 ...-Add-flag-specific-to-signaling-nans.patch |  121 ++
 ...rw_function_take_MemTxAttrs_argument.patch |  158 ++
 ...e-float_invalid_op_addsub-for-new-fl.patch |  114 ++
 ...te_function_take_MemTxAttrs_argument.patch | 1453 +
 ...e-float_invalid_op_mul-for-new-flags.patch |   86 +
 ...ap_function_take_MemTxAttrs_argument.patch |  227 +++
 ...e-float_invalid_op_div-for-new-flags.patch |   99 ++
 ..._buf_rw_function_take_a_void_pointer.patch |   41 +
 ...arget-ppc-Update-fmadd-for-new-flags.patch |  102 ++
 ..._dma_buf_write_functions_take_a_void.patch |  167 ++
 .../0010-target-ppc-Split-out-do_fmadd.patch  |   71 +
 ...rw_function_take_MemTxAttrs_argument.patch |   91 ++
 ...s-max-min-cj-dp-to-use-VSX-registers.patch |   93 ++
 ...rw_function_take_MemTxAttrs_argument.patch |   65 +
 ...-Move-xs-max-min-cj-dp-to-decodetree.patch |  121 ++
 ...te_function_take_MemTxAttrs_argument.patch |  129 ++
 ...get-ppc-fix-xscvqpdp-register-access.patch |   41 +
 ...ad_function_take_MemTxAttrs_argument.patch |  222 +++
 ...rget-ppc-move-xscvqpdp-to-decodetree.patch |  130 ++
 ...uf_rw_function_propagate_MemTxResult.patch |   91 ++
 ...tore_fpscr-doesn-t-update-bits-0-to-.patch |   70 +
 ...ma_function_take_MemTxAttrs_argument.patch |  120 ++
 ...get-ppc-Introduce-TRANS-FLAGS-macros.patch |  133 ++
 ...ma_function_take_MemTxAttrs_argument.patch |  151 ++
 ...get-ppc-Implement-Vector-Expand-Mask.patch |  105 ++
 ...r_dma_function_propagate_MemTxResult.patch |   65 +
 ...et-ppc-Implement-Vector-Extract-Mask.patch |  141 ++
 ...r_dma_function_propagate_MemTxResult.patch |  175 ++
 ...ppc-Implement-Vector-Mask-Move-insns.patch |  187 +++
 ...ma_function_take_MemTxAttrs_argument.patch |  303 
 ...xs-n-madd-am-ds-p-xs-n-msub-am-ds-p-.patch |  258 +++
 ...ma_function_take_MemTxAttrs_argument.patch |  271 +++
 ...mplement-xs-n-maddqp-o-xs-n-msubqp-o.patch |  174 ++
 ...i_dma_function_propagate_MemTxResult.patch |   47 +
 ...i_dma_function_propagate_MemTxResult.patch |  296 
 .../qemu/qemu/CVE-2021-3611_1.patch   |   74 +
 .../qemu/qemu/CVE-2021-3611_2.patch   |   43 +
 .../qemu/qemu/CVE-2021-3750-1.patch   |   59 +
 .../qemu/qemu/CVE-2021-3750-2.patch   |   65 +
 .../qemu/qemu/CVE-2021-3750-3.patch   |  156 ++
 meta/recipes-kernel/linux/linux-yocto-dev.bb  |2 +-
 ...4-fix-kernel-crash-caused-by-do_get_.patch |   94 ++
 .../lttng/lttng-modules_2.13.4.bb |1 +
 ...-tools_2.13.4.bb => lttng-tools_2.13.8.bb} |

[OE-core][kirkstone 01/13] tiff: Security fixes CVE-2022-2867,CVE-2022-2868 and CVE-2022-2869

2022-10-17 Thread Steve Sakoman 
From: Teoh Jay Shen 

This series of patches include fixes for CVE-2022-2867,CVE-2022-2868 and 
CVE-2022-2869.
These patches are modified using devtool and a review was conducted to make 
sure they all get applied in the correct location.

References:

https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2867
https://security-tracker.debian.org/tracker/CVE-2022-2867

https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2868
https://security-tracker.debian.org/tracker/CVE-2022-2868

https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2869
https://security-tracker.debian.org/tracker/CVE-2022-2869

Merge request:

https://gitlab.com/libtiff/libtiff/-/merge_requests/294/diffs?commit_id=7d7bfa4416366ec64068ac389414241ed4730a54

Patches from:

https://gitlab.com/libtiff/libtiff/-/commit/bcf28bb7f630f24fa47701a9907013f3548092cd?merge_request_iid=294
https://gitlab.com/libtiff/libtiff/-/commit/7d7bfa4416366ec64068ac389414241ed4730a54?merge_request_iid=294
https://gitlab.com/libtiff/libtiff/-/commit/b258ed69a485a9cfb299d9f060eb2a46c54e5903?merge_request_iid=294

Notes:
These CVEs are fixed in tiff v4.4.0

Signed-off-by: Teoh Jay Shen 
Signed-off-by: Steve Sakoman 
---
 .../libtiff/tiff/CVE-2022-2867.patch  | 129 ++
 .../libtiff/tiff/CVE-2022-2869.patch  |  84 
 ...ed69a485a9cfb299d9f060eb2a46c54e5903.patch |  45 ++
 meta/recipes-multimedia/libtiff/tiff_4.3.0.bb |   3 +
 4 files changed, 261 insertions(+)
 create mode 100644 meta/recipes-multimedia/libtiff/tiff/CVE-2022-2867.patch
 create mode 100644 meta/recipes-multimedia/libtiff/tiff/CVE-2022-2869.patch
 create mode 100644 
meta/recipes-multimedia/libtiff/tiff/b258ed69a485a9cfb299d9f060eb2a46c54e5903.patch

diff --git a/meta/recipes-multimedia/libtiff/tiff/CVE-2022-2867.patch 
b/meta/recipes-multimedia/libtiff/tiff/CVE-2022-2867.patch
new file mode 100644
index 00..ae33a3b4e7
--- /dev/null
+++ b/meta/recipes-multimedia/libtiff/tiff/CVE-2022-2867.patch
@@ -0,0 +1,129 @@
+From 6ad097dac1d4908705f5a9d43dea76b7f2de89eb Mon Sep 17 00:00:00 2001
+From: Su_Laus 
+Date: Sun, 6 Feb 2022 17:53:53 +0100
+Subject: [PATCH] tiffcrop.c: This update fixes also issues #350 and #351.
+
+ Issue 350 is fixed by checking for not allowed zone input cases like -Z 0:0
+ in getCropOffsets().
+
+CVE: CVE-2022-2867
+
+Upstream-Status: Backport
+[https://gitlab.com/libtiff/libtiff/-/commit/7d7bfa4416366ec64068ac389414241ed4730a54?merge_request_iid=294]
+
+Signed-off-by: Teoh Jay Shen 
+
+---
+ tools/tiffcrop.c | 58 +---
+ 1 file changed, 40 insertions(+), 18 deletions(-)
+
+diff --git a/tools/tiffcrop.c b/tools/tiffcrop.c
+index 4a4ace8..0ef5bb2 100644
+--- a/tools/tiffcrop.c
 b/tools/tiffcrop.c
+@@ -5194,20 +5194,33 @@ computeInputPixelOffsets(struct crop_mask *crop, 
struct image_data *image,
+   y1 = _TIFFClampDoubleToUInt32(crop->corners[i].Y1);
+   y2 = _TIFFClampDoubleToUInt32(crop->corners[i].Y2);
+   }
+-  /* region needs to be within image sizes 0.. width-1; 0..length-1 
+-   * - be aware x,y are already casted to (uint32_t) and avoid (0 - 1)
++  /* a) Region needs to be within image sizes 0.. width-1; 0..length-1 
++   * b) Corners are expected to be submitted as top-left to bottom-right.
++   *Therefore, check that and reorder input.
++   * (be aware x,y are already casted to (uint32_t) and avoid (0 - 1) )
+*/
+- if (x1 > image->width - 1)
++  uint32_t aux;
++  if (x1 > x2) {
++aux = x1;
++x1 = x2;
++x2 = aux;
++  }
++  if (y1 > y2) {
++aux = y1;
++y1 = y2;
++y2 = aux;
++  }
++  if (x1 > image->width - 1)
+ crop->regionlist[i].x1 = image->width - 1;
+- else if (x1 > 0)
+-crop->regionlist[i].x1 = (uint32_t) (x1 - 1);
++  else if (x1 > 0)
++crop->regionlist[i].x1 = (uint32_t)(x1 - 1);
+ 
+- if (x2 > image->width - 1)
+-   crop->regionlist[i].x2 = image->width - 1;
+- else if (x2 > 0)
+-   crop->regionlist[i].x2 = (uint32_t)(x2 - 1);
++  if (x2 > image->width - 1)
++crop->regionlist[i].x2 = image->width - 1;
++  else if (x2 > 0)
++crop->regionlist[i].x2 = (uint32_t)(x2 - 1);
+ 
+-  zwidth  = crop->regionlist[i].x2 - crop->regionlist[i].x1 + 1; 
++  zwidth = crop->regionlist[i].x2 - crop->regionlist[i].x1 + 1;
+ 
+   if (y1 > image->length - 1)
+ crop->regionlist[i].y1 = image->length - 1;
+@@ -5219,8 +5232,7 @@ computeInputPixelOffsets(struct crop_mask *crop, struct 
image_data *image,
+   else if (y2 > 0)
+ crop->regionlist[i].y2 = (uint32_t)(y2 - 1);
+ 
+-  zlength = crop->regionlist[i].y2 - crop->regionlist[i].y1 + 1; 
+-
++  zlength = crop->regionlist[i].y2 - crop->regionlist[i].y1 + 1;
+   if (zwidth > max_width)
+ max_width = zwidth;
+   if (zlength > max_length)
+@@ -5250,7 +5262,7 @@ computeInputPixelOffsets(s

[OE-core][kirkstone 02/13] binutils : Fix CVE-2022-38128

2022-10-17 Thread Steve Sakoman 
From: pgowda 

Upstream-Status: Backport 
[https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=f07c08e115e27cddf5a0030dc6332bbee1bd9c6a]
Upstream-Status: Backport 
[https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=175b91507b83ad42607d2f6dadaf55b7b511bdbe]
Upstream-Status: Backport 
[https://sourceware.org/git/?p=binutils-gdb.git;a=patch;h=695c6dfe7e85006b98c8b746f3fd5f913c94ebff]

Signed-off-by: pgowda 
Signed-off-by: Steve Sakoman 
---
 .../binutils/binutils-2.38.inc|   3 +
 .../binutils/0018-CVE-2022-38128-1.patch  | 350 ++
 .../binutils/0018-CVE-2022-38128-2.patch  | 436 ++
 .../binutils/0018-CVE-2022-38128-3.patch  |  95 
 4 files changed, 884 insertions(+)
 create mode 100644 
meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-1.patch
 create mode 100644 
meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-2.patch
 create mode 100644 
meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-3.patch

diff --git a/meta/recipes-devtools/binutils/binutils-2.38.inc 
b/meta/recipes-devtools/binutils/binutils-2.38.inc
index fc88d4a79e..8259ec3232 100644
--- a/meta/recipes-devtools/binutils/binutils-2.38.inc
+++ b/meta/recipes-devtools/binutils/binutils-2.38.inc
@@ -39,5 +39,8 @@ SRC_URI = "\
  file://0017-CVE-2022-38127-2.patch \
  file://0017-CVE-2022-38127-3.patch \
  file://0017-CVE-2022-38127-4.patch \
+ file://0018-CVE-2022-38128-1.patch \
+ file://0018-CVE-2022-38128-2.patch \
+ file://0018-CVE-2022-38128-3.patch \
 "
 S  = "${WORKDIR}/git"
diff --git 
a/meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-1.patch 
b/meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-1.patch
new file mode 100644
index 00..0a490d86b3
--- /dev/null
+++ b/meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-1.patch
@@ -0,0 +1,350 @@
+From f07c08e115e27cddf5a0030dc6332bbee1bd9c6a Mon Sep 17 00:00:00 2001
+From: Alan Modra 
+Date: Thu, 21 Jul 2022 08:38:14 +0930
+Subject: [PATCH] binutils/dwarf.c: abbrev caching
+
+I'm inclined to think that abbrev caching is counter-productive.  The
+time taken to search the list of abbrevs converted to internal form is
+non-zero, and it's easy to decode the raw abbrevs.  It's especially
+silly to cache empty lists of decoded abbrevs (happens with zero
+padding in .debug_abbrev), or abbrevs as they are displayed when there
+is no further use of those abbrevs.  This patch stops caching in those
+cases.
+
+   * dwarf.c (record_abbrev_list_for_cu): Add free_list param.
+   Put abbrevs on abbrev_lists here.
+   (new_abbrev_list): Delete function.
+   (process_abbrev_set): Return newly allocated list.  Move
+   abbrev base, offset and size checking to..
+   (find_and_process_abbrev_set): ..here, new function.  Handle
+   lookup of cached abbrevs here, and calculate start and end
+   for process_abbrev_set.  Return free_list if newly alloc'd.
+   (process_debug_info): Consolidate cached list lookup, new list
+   alloc and processing into find_and_process_abbrev_set call.
+   Free list when not cached.
+   (display_debug_abbrev): Similarly.
+
+Upstream-Status: Backport 
[https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=f07c08e115e27cddf5a0030dc6332bbee1bd9c6a]
+
+Signed-off-by: Pgowda 
+---
+ binutils/dwarf.c | 208 +--
+ 1 file changed, 110 insertions(+), 98 deletions(-)
+
+diff --git a/binutils/dwarf.c b/binutils/dwarf.c
+index 267ed3bb382..2fc352f74c5 100644
+--- a/binutils/dwarf.c
 b/binutils/dwarf.c
+@@ -882,8 +882,15 @@ static unsigned long  next_free_abbrev_m
+ #define ABBREV_MAP_ENTRIES_INCREMENT   8
+ 
+ static void
+-record_abbrev_list_for_cu (dwarf_vma start, dwarf_vma end, abbrev_list * list)
++record_abbrev_list_for_cu (dwarf_vma start, dwarf_vma end,
++ abbrev_list *list, abbrev_list *free_list)
+ {
++  if (free_list != NULL)
++{
++  list->next = abbrev_lists;
++  abbrev_lists = list;
++}
++
+   if (cu_abbrev_map == NULL)
+ {
+   num_abbrev_map_entries = INITIAL_NUM_ABBREV_MAP_ENTRIES;
+@@ -936,20 +943,6 @@ free_all_abbrevs (void)
+ }
+ 
+ static abbrev_list *
+-new_abbrev_list (dwarf_vma abbrev_base, dwarf_vma abbrev_offset)
+-{
+-  abbrev_list * list = (abbrev_list *) xcalloc (sizeof * list, 1);
+-
+-  list->abbrev_base = abbrev_base;
+-  list->abbrev_offset = abbrev_offset;
+-
+-  list->next = abbrev_lists;
+-  abbrev_lists = list;
+-
+-  return list;
+-}
+-
+-static abbrev_list *
+ find_abbrev_list_by_abbrev_offset (dwarf_vma abbrev_base,
+  dwarf_vma abbrev_offset)
+ {
+@@ -966,7 +959,7 @@ find_abbrev_list_by_abbrev_offset (dwarf
+ /* Find the abbreviation map for the CU that includes OFFSET.
+OFFSET is an absolute offset from the start of the .debug_info section.  */
+ /* FIXME: This function is going to slow down readelf & objdump.

[OE-core][kirkstone 03/13] qemu: Fix CVE-2021-3750 for qemu

2022-10-17 Thread Steve Sakoman 
From: Virendra Thakur 

Add patch to fix CVE-2021-3750

Signed-off-by: Virendra Thakur 
Signed-off-by: Steve Sakoman 
---
 meta/recipes-devtools/qemu/qemu.inc   |   3 +
 .../qemu/qemu/CVE-2021-3750-1.patch   |  59 +++
 .../qemu/qemu/CVE-2021-3750-2.patch   |  65 
 .../qemu/qemu/CVE-2021-3750-3.patch   | 156 ++
 4 files changed, 283 insertions(+)
 create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2021-3750-1.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2021-3750-2.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2021-3750-3.patch

diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index a493ac8add..816f9a7eac 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -43,6 +43,9 @@ SRC_URI = "https://download.qemu.org/${BPN}-${PV}.tar.xz \
file://CVE-2022-0358.patch \
file://CVE-2022-0216_1.patch \
file://CVE-2022-0216_2.patch \
+   file://CVE-2021-3750-1.patch \
+   file://CVE-2021-3750-2.patch \
+   file://CVE-2021-3750-3.patch \
"
 UPSTREAM_CHECK_REGEX = "qemu-(?P\d+(\.\d+)+)\.tar"
 
diff --git a/meta/recipes-devtools/qemu/qemu/CVE-2021-3750-1.patch 
b/meta/recipes-devtools/qemu/qemu/CVE-2021-3750-1.patch
new file mode 100644
index 00..e898c20767
--- /dev/null
+++ b/meta/recipes-devtools/qemu/qemu/CVE-2021-3750-1.patch
@@ -0,0 +1,59 @@
+From b9d383ab797f54ae5fa8746117770709921dc529 Mon Sep 17 00:00:00 2001
+From: =?utf8?q?Philippe=20Mathieu-Daud=C3=A9?= 
+Date: Wed, 15 Dec 2021 19:24:19 +0100
+Subject: [PATCH] hw/intc/arm_gicv3: Check for !MEMTX_OK instead of MEMTX_ERROR
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf8
+Content-Transfer-Encoding: 8bit
+
+Quoting Peter Maydell:
+
+ "These MEMTX_* aren't from the memory transaction
+  API functions; they're just being used by gicd_readl() and
+  friends as a way to indicate a success/failure so that the
+  actual MemoryRegionOps read/write fns like gicv3_dist_read()
+  can log a guest error."
+
+We are going to introduce more MemTxResult bits, so it is
+safer to check for !MEMTX_OK rather than MEMTX_ERROR.
+
+Reviewed-by: Peter Xu 
+Reviewed-by: David Hildenbrand 
+Reviewed-by: Peter Maydell 
+Reviewed-by: Stefan Hajnoczi 
+Signed-off-by: Philippe Mathieu-DaudÃf© 
+Signed-off-by: Peter Maydell 
+Signed-off-by: Virendra Thakur 
+
+CVE: CVE-2021-3750
+
+Upstream-Status: Backport 
[https://git.qemu.org/?p=qemu.git;a=commit;h=b9d383ab797f54ae5fa8746117770709921dc529]
+---
+ hw/intc/arm_gicv3_redist.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/hw/intc/arm_gicv3_redist.c b/hw/intc/arm_gicv3_redist.c
+index c8ff3ec..99b11ca 100644
+--- a/hw/intc/arm_gicv3_redist.c
 b/hw/intc/arm_gicv3_redist.c
+@@ -462,7 +462,7 @@ MemTxResult gicv3_redist_read(void *opaque, hwaddr offset, 
uint64_t *data,
+ break;
+ }
+
+-if (r == MEMTX_ERROR) {
++if (r != MEMTX_OK) {
+ qemu_log_mask(LOG_GUEST_ERROR,
+   "%s: invalid guest read at offset " TARGET_FMT_plx
+   " size %u\n", __func__, offset, size);
+@@ -521,7 +521,7 @@ MemTxResult gicv3_redist_write(void *opaque, hwaddr 
offset, uint64_t data,
+ break;
+ }
+
+-if (r == MEMTX_ERROR) {
++if (r != MEMTX_OK) {
+ qemu_log_mask(LOG_GUEST_ERROR,
+   "%s: invalid guest write at offset " TARGET_FMT_plx
+   " size %u\n", __func__, offset, size);
+--
+1.8.3.1
+
diff --git a/meta/recipes-devtools/qemu/qemu/CVE-2021-3750-2.patch 
b/meta/recipes-devtools/qemu/qemu/CVE-2021-3750-2.patch
new file mode 100644
index 00..f163b4fab3
--- /dev/null
+++ b/meta/recipes-devtools/qemu/qemu/CVE-2021-3750-2.patch
@@ -0,0 +1,65 @@
+From 58e74682baf4e1ad26b064d8c02e5bc99c75c5d9 Mon Sep 17 00:00:00 2001
+From: =?utf8?q?Philippe=20Mathieu-Daud=C3=A9?= 
+Date: Wed, 15 Dec 2021 19:24:20 +0100
+Subject: [PATCH] softmmu/physmem: Simplify flatview_write and
+ address_space_access_valid
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf8
+Content-Transfer-Encoding: 8bit
+
+Remove unuseful local 'result' variables.
+
+Reviewed-by: Peter Xu 
+Reviewed-by: David Hildenbrand 
+Reviewed-by: Alexander Bulekov 
+Reviewed-by: Stefan Hajnoczi 
+Signed-off-by: Philippe Mathieu-DaudÃf© 
+Message-Id: <20211215182421.418374-3-phi...@redhat.com>
+Signed-off-by: Thomas Huth 
+Signed-off-by: Virendra Thakur 
+
+CVE: CVE-2021-3750
+
+Upstream-Status: Backport 
[https://git.qemu.org/?p=qemu.git;a=commit;h=58e74682baf4e1ad26b064d8c02e5bc99c75c5d9]
+---
+ softmmu/physmem.c | 11 +++
+ 1 file changed, 3 insertions(+), 8 deletions(-)
+
+diff --git a/softmmu/physmem.c b/softmmu/physmem.c
+index 43ae70f..3d968ca 100644
+--- a/softmmu/physmem.c
 b/softmmu/physmem.c
+@@ -2826,14 +2826,11 @@ static MemTxResult flatview_write(FlatVi
+ hwaddr l;

[OE-core][kirkstone 05/13] qemu: fix CVE-2022-2962

2022-10-17 Thread Steve Sakoman 
From: Ross Burton 

Backport the fix for CVE-2022-2962.

(From OE-Core rev: 943d28a3395455fd475cb6c84247d106adf5fca3)

Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie 
(cherry picked from commit ddc4258012e0d3fa946c319b601b0e73db7ac5e6)
Signed-off-by: Bhabu Bindu 

Signed-off-by: virendra thakur 
Signed-off-by: Steve Sakoman 
---
 meta/recipes-devtools/qemu/qemu.inc   |  1 +
 ...ulip-Restrict-DMA-engine-to-memories.patch | 64 +++
 2 files changed, 65 insertions(+)
 create mode 100644 
meta/recipes-devtools/qemu/qemu/0001-net-tulip-Restrict-DMA-engine-to-memories.patch

diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index cb5f9358da..76ae603ee4 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -70,6 +70,7 @@ SRC_URI = "https://download.qemu.org/${BPN}-${PV}.tar.xz \

file://0022_let_ld_pointer_pci_dma_function_propagate_MemTxResult.patch \
file://CVE-2021-3611_1.patch \
file://CVE-2021-3611_2.patch \
+   file://0001-net-tulip-Restrict-DMA-engine-to-memories.patch \
"
 UPSTREAM_CHECK_REGEX = "qemu-(?P\d+(\.\d+)+)\.tar"
 
diff --git 
a/meta/recipes-devtools/qemu/qemu/0001-net-tulip-Restrict-DMA-engine-to-memories.patch
 
b/meta/recipes-devtools/qemu/qemu/0001-net-tulip-Restrict-DMA-engine-to-memories.patch
new file mode 100644
index 00..6c85a77ba7
--- /dev/null
+++ 
b/meta/recipes-devtools/qemu/qemu/0001-net-tulip-Restrict-DMA-engine-to-memories.patch
@@ -0,0 +1,64 @@
+CVE: CVE-2022-2962
+Upstream-Status: Backport
+Signed-off-by: Ross Burton 
+
+From 5c5c50b0a73d78ffe18336c9996fef5eae90 Mon Sep 17 00:00:00 2001
+From: Zheyu Ma 
+Date: Sun, 21 Aug 2022 20:43:43 +0800
+Subject: [PATCH] net: tulip: Restrict DMA engine to memories
+
+The DMA engine is started by I/O access and then itself accesses the
+I/O registers, triggering a reentrancy bug.
+
+The following log can reveal it:
+==5637==ERROR: AddressSanitizer: stack-overflow
+#0 0x5595435f6078 in tulip_xmit_list_update qemu/hw/net/tulip.c:673
+#1 0x5595435f204a in tulip_write qemu/hw/net/tulip.c:805:13
+#2 0x559544637f86 in memory_region_write_accessor 
qemu/softmmu/memory.c:492:5
+#3 0x5595446379fa in access_with_adjusted_size qemu/softmmu/memory.c:554:18
+#4 0x5595446372fa in memory_region_dispatch_write qemu/softmmu/memory.c
+#5 0x55954468b74c in flatview_write_continue qemu/softmmu/physmem.c:2825:23
+#6 0x559544683662 in flatview_write qemu/softmmu/physmem.c:2867:12
+#7 0x5595446833f3 in address_space_write qemu/softmmu/physmem.c:2963:18
+#8 0x5595435fb082 in dma_memory_rw_relaxed qemu/include/sysemu/dma.h:87:12
+#9 0x5595435fb082 in dma_memory_rw qemu/include/sysemu/dma.h:130:12
+#10 0x5595435fb082 in dma_memory_write qemu/include/sysemu/dma.h:171:12
+#11 0x5595435fb082 in stl_le_dma qemu/include/sysemu/dma.h:272:1
+#12 0x5595435fb082 in stl_le_pci_dma qemu/include/hw/pci/pci.h:910:1
+#13 0x5595435fb082 in tulip_desc_write qemu/hw/net/tulip.c:101:9
+#14 0x5595435f7e3d in tulip_xmit_list_update qemu/hw/net/tulip.c:706:9
+#15 0x5595435f204a in tulip_write qemu/hw/net/tulip.c:805:13
+
+Fix this bug by restricting the DMA engine to memories regions.
+
+Signed-off-by: Zheyu Ma 
+Signed-off-by: Jason Wang 
+---
+ hw/net/tulip.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/hw/net/tulip.c b/hw/net/tulip.c
+index 097e905bec..b9e42c322a 100644
+--- a/hw/net/tulip.c
 b/hw/net/tulip.c
+@@ -70,7 +70,7 @@ static const VMStateDescription vmstate_pci_tulip = {
+ static void tulip_desc_read(TULIPState *s, hwaddr p,
+ struct tulip_descriptor *desc)
+ {
+-const MemTxAttrs attrs = MEMTXATTRS_UNSPECIFIED;
++const MemTxAttrs attrs = { .memory = true };
+ 
+ if (s->csr[0] & CSR0_DBO) {
+ ldl_be_pci_dma(&s->dev, p, &desc->status, attrs);
+@@ -88,7 +88,7 @@ static void tulip_desc_read(TULIPState *s, hwaddr p,
+ static void tulip_desc_write(TULIPState *s, hwaddr p,
+ struct tulip_descriptor *desc)
+ {
+-const MemTxAttrs attrs = MEMTXATTRS_UNSPECIFIED;
++const MemTxAttrs attrs = { .memory = true };
+ 
+ if (s->csr[0] & CSR0_DBO) {
+ stl_be_pci_dma(&s->dev, p, desc->status, attrs);
+-- 
+2.34.1
+
-- 
2.25.1


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

[OE-core][kirkstone 07/13] python3: upgrade 3.10.4 -> 3.10.7

2022-10-17 Thread Steve Sakoman 
From: Tim Orling 

Security and bug fixes.

Drop patch for gh-92036 which was merged in 3.10.5
Refresh 0017-setup.py-do-not-report-missing-dependencies-for-disa.pathc

Fixes:
* CVE-2020-10735
  https://nvd.nist.gov/vuln/detail/CVE-2020-10735
* CVE-2021-28861
  https://nvd.nist.gov/vuln/detail/CVE-2021-28861
* CVE-2018-25032
  https://nvd.nist.gov/vuln/detail/CVE-2018-25032

For a list of changes see:
https://docs.python.org/3.10/whatsnew/changelog.html#python-3-10-7-final
https://docs.python.org/3.10/whatsnew/changelog.html#python-3-10-6-final
https://docs.python.org/3.10/whatsnew/changelog.html#python-3-10-6-final

Signed-off-by: Tim Orling 
Signed-off-by: Steve Sakoman 
---
 ...h-92036-Fix-gc_fini_untrack-GH-92037.patch | 54 ---
 ...report-missing-dependencies-for-disa.patch |  8 +--
 .../{python3_3.10.4.bb => python3_3.10.7.bb}  |  3 +-
 3 files changed, 6 insertions(+), 59 deletions(-)
 delete mode 100644 
meta/recipes-devtools/python/python3/0001-gh-92036-Fix-gc_fini_untrack-GH-92037.patch
 rename meta/recipes-devtools/python/{python3_3.10.4.bb => python3_3.10.7.bb} 
(99%)

diff --git 
a/meta/recipes-devtools/python/python3/0001-gh-92036-Fix-gc_fini_untrack-GH-92037.patch
 
b/meta/recipes-devtools/python/python3/0001-gh-92036-Fix-gc_fini_untrack-GH-92037.patch
deleted file mode 100644
index 6a58c35cc6..00
--- 
a/meta/recipes-devtools/python/python3/0001-gh-92036-Fix-gc_fini_untrack-GH-92037.patch
+++ /dev/null
@@ -1,54 +0,0 @@
-From 178a238f25ab8aff7689d7a09d66dc1583ecd6cb Mon Sep 17 00:00:00 2001
-From: "Miss Islington (bot)"
- <31488909+miss-isling...@users.noreply.github.com>
-Date: Wed, 4 May 2022 03:23:29 -0700
-Subject: [PATCH 01/40] gh-92036: Fix gc_fini_untrack() (GH-92037)
-
-Fix a crash in subinterpreters related to the garbage collector. When
-a subinterpreter is deleted, untrack all objects tracked by its GC.
-To prevent a crash in deallocator functions expecting objects to be
-tracked by the GC, leak a strong reference to these objects on
-purpose, so they are never deleted and their deallocator functions
-are not called.
-(cherry picked from commit 14243369b5f80613628a565c224bba7fb3fcacd8)
-
-Co-authored-by: Victor Stinner 
-
-Upstream-Status: Backport

- .../2022-04-28-23-37-30.gh-issue-92036.GZJAC9.rst   | 5 +
- Modules/gcmodule.c  | 6 ++
- 2 files changed, 11 insertions(+)
- create mode 100644 Misc/NEWS.d/next/Core and 
Builtins/2022-04-28-23-37-30.gh-issue-92036.GZJAC9.rst
-
-diff --git a/Misc/NEWS.d/next/Core and 
Builtins/2022-04-28-23-37-30.gh-issue-92036.GZJAC9.rst b/Misc/NEWS.d/next/Core 
and Builtins/2022-04-28-23-37-30.gh-issue-92036.GZJAC9.rst
-new file mode 100644
-index 00..78094c5e4f
 /dev/null
-+++ b/Misc/NEWS.d/next/Core and 
Builtins/2022-04-28-23-37-30.gh-issue-92036.GZJAC9.rst 
-@@ -0,0 +1,5 @@
-+Fix a crash in subinterpreters related to the garbage collector. When a
-+subinterpreter is deleted, untrack all objects tracked by its GC. To prevent a
-+crash in deallocator functions expecting objects to be tracked by the GC, leak
-+a strong reference to these objects on purpose, so they are never deleted and
-+their deallocator functions are not called. Patch by Victor Stinner.
-diff --git a/Modules/gcmodule.c b/Modules/gcmodule.c
-index 805a159d53..43ae6fa98b 100644
 a/Modules/gcmodule.c
-+++ b/Modules/gcmodule.c
-@@ -2170,6 +2170,12 @@ gc_fini_untrack(PyGC_Head *list)
- for (gc = GC_NEXT(list); gc != list; gc = GC_NEXT(list)) {
- PyObject *op = FROM_GC(gc);
- _PyObject_GC_UNTRACK(op);
-+// gh-92036: If a deallocator function expect the object to be tracked
-+// by the GC (ex: func_dealloc()), it can crash if called on an object
-+// which is no longer tracked by the GC. Leak one strong reference on
-+// purpose so the object is never deleted and its deallocator is not
-+// called.
-+Py_INCREF(op);
- }
- }
- 
--- 
-2.25.1
-
diff --git 
a/meta/recipes-devtools/python/python3/0017-setup.py-do-not-report-missing-dependencies-for-disa.patch
 
b/meta/recipes-devtools/python/python3/0017-setup.py-do-not-report-missing-dependencies-for-disa.patch
index 0ead57e465..8c554feb4b 100644
--- 
a/meta/recipes-devtools/python/python3/0017-setup.py-do-not-report-missing-dependencies-for-disa.patch
+++ 
b/meta/recipes-devtools/python/python3/0017-setup.py-do-not-report-missing-dependencies-for-disa.patch
@@ -12,16 +12,18 @@ Upstream-Status: Inappropriate [oe-core specific]
 Signed-off-by: Alexander Kanavin 
 Signed-off-by: Martin Jansa 
 Signed-off-by: Alejandro Hernandez Samaniego 
+Refresh for 3.10.7:
+Signed-off-by: Tim Orling 
 
 ---
  setup.py | 8 
  1 file changed, 8 insertions(+)
 
 diff --git a/setup.py b/setup.py
-index 2be4738..62f0e18 100644
+index 85a2b26357..7605347bf5 100644
 --- a/setup.py
 +++ b/setup.py
-@@ -517,6 +517,14 @@ class PyBuildExt(build_ext):
+@@ -517,6 +517,14 @@ def print_three_colu

[OE-core][kirkstone 08/13] lttng-tools: Upgrade 2.13.4 -> 2.13.8

2022-10-17 Thread Steve Sakoman 
From: He Zhe 

Signed-off-by: He Zhe 
Signed-off-by: Steve Sakoman 
---
 .../lttng/{lttng-tools_2.13.4.bb => lttng-tools_2.13.8.bb}  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-kernel/lttng/{lttng-tools_2.13.4.bb => 
lttng-tools_2.13.8.bb} (98%)

diff --git a/meta/recipes-kernel/lttng/lttng-tools_2.13.4.bb 
b/meta/recipes-kernel/lttng/lttng-tools_2.13.8.bb
similarity index 98%
rename from meta/recipes-kernel/lttng/lttng-tools_2.13.4.bb
rename to meta/recipes-kernel/lttng/lttng-tools_2.13.8.bb
index 0ea4da05ce..0b6dfa48a4 100644
--- a/meta/recipes-kernel/lttng/lttng-tools_2.13.4.bb
+++ b/meta/recipes-kernel/lttng/lttng-tools_2.13.8.bb
@@ -39,7 +39,7 @@ SRC_URI = 
"https://lttng.org/files/lttng-tools/lttng-tools-${PV}.tar.bz2 \
file://disable-tests.patch \
"
 
-SRC_URI[sha256sum] = 
"565f3102410a53d484f4c8ff517978f1dc59f67f9d16f872f4357f3ca12200f6"
+SRC_URI[sha256sum] = 
"b1e959579b260790930b20f3c7aa7cefb8a40e0de80d4a777c2bf78c6b353dc1"
 
 inherit autotools ptest pkgconfig useradd python3-dir manpages systemd
 
-- 
2.25.1


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

[OE-core][kirkstone 06/13] qemu: Backport patches from upstream to support float128 on qemu-ppc64

2022-10-17 Thread Steve Sakoman 
From: Xiangyu Chen 

Background:
Due to current qemu 6.2 doesn't support float128, this cause some POSIX 
APIs(e.g. double difftime()..)
return a wrong value, this issue can be reproduced by open_posix_testsuit 
difftime case[1].

The qemu upstream has already supported ppc64 float128, but need to update to 
qemu 7.0 or later.
We backport the commits[2] from upstream to support that in qemu-ppc64 6.2.0.

[1] difftime test case:
https://github.com/linux-test-project/ltp/tree/master/testcases/open_posix_testsuite/conformance/interfaces/difftime

[2] commits link:
LINK: 
https://git.qemu.org/?p=qemu.git;a=commit;h=149a48f6e6ccedfa01307d45884aa480f5bf77c5
  
https://git.qemu.org/?p=qemu.git;a=commit;h=ba11446c40903b9d97fb75a078d43fee6444d3b6
  
https://git.qemu.org/?p=qemu.git;a=commit;h=bead3c9b0ff8efd652afb27923d8ab4458b3bbd9
  
https://git.qemu.org/?p=qemu.git;a=commit;h=10cc964030fca459591d9353571f3b1b4e1b5aec
  
https://git.qemu.org/?p=qemu.git;a=commit;h=e706d4455b8d54252b11fc504c56df060151cb89
  
https://git.qemu.org/?p=qemu.git;a=commit;h=941298ecd7e3103d3789d2dd87dd0f119e81c69e
  
https://git.qemu.org/?p=qemu.git;a=commit;h=4edf55698fc2ea30903657c63ed95db0d5548943
  
https://git.qemu.org/?p=qemu.git;a=commit;h=c07f82416cb7973c64d1e21c09957182b4b033dc
  
https://git.qemu.org/?p=qemu.git;a=commit;h=e4052bb773cc829a27786d68caa22f28cff19d39
  
https://git.qemu.org/?p=qemu.git;a=commit;h=ffdaff8e9c698061f57a6b1827570562c5a1c909
  
https://git.qemu.org/?p=qemu.git;a=commit;h=201fc774e0e1cc76ec23b595968004a7b14fb6e8
  
https://git.qemu.org/?p=qemu.git;a=commit;h=c5df1898a147c232f0502cda5dac8df6074070fc
  
https://git.qemu.org/?p=qemu.git;a=commit;h=38d4914c5065e14f0969161274793ded448f067f
  
https://git.qemu.org/?p=qemu.git;a=commit;h=caf6f9b568479bea6f6d97798be670f21641a006
  
https://git.qemu.org/?p=qemu.git;a=commit;h=25ee608d79c1890c0f4e8c495ec8629d5712de45
  
https://git.qemu.org/?p=qemu.git;a=commit;h=19f0862dd8fa6510b2f5b3aff4859363602cd0cf
  
https://git.qemu.org/?p=qemu.git;a=commit;h=5f1470b091007f24035d6d33149df49a6dd61682
  
https://git.qemu.org/?p=qemu.git;a=commit;h=17868d81e0074905b2c1e414af6618570e8059eb
  
https://git.qemu.org/?p=qemu.git;a=commit;h=9193eaa901c54dbff4a91ea0b12a99e0135dbca1
  
https://git.qemu.org/?p=qemu.git;a=commit;h=e4318ab2e423c4caf9a88a4e99b5e234096b81a9
  
https://git.qemu.org/?p=qemu.git;a=commit;h=3bb1aed246d7b59ceee625a82628f7369d492a8f

Signed-off-by: Xiangyu Chen 
Signed-off-by: Steve Sakoman 
---
 meta/recipes-devtools/qemu/qemu.inc   |  21 ++
 ...end-float_exception_flags-to-16-bits.patch |  75 +
 ...ftfloat-Add-flag-specific-to-Inf-Inf.patch |  59 
 ...softfloat-Add-flag-specific-to-Inf-0.patch | 126 +
 ...dd-flags-specific-to-Inf-Inf-and-0-0.patch |  73 +
 ...-Add-flag-specific-to-signaling-nans.patch | 121 
 ...e-float_invalid_op_addsub-for-new-fl.patch | 114 
 ...e-float_invalid_op_mul-for-new-flags.patch |  86 ++
 ...e-float_invalid_op_div-for-new-flags.patch |  99 +++
 ...arget-ppc-Update-fmadd-for-new-flags.patch | 102 +++
 .../0010-target-ppc-Split-out-do_fmadd.patch  |  71 +
 ...s-max-min-cj-dp-to-use-VSX-registers.patch |  93 +++
 ...-Move-xs-max-min-cj-dp-to-decodetree.patch | 121 
 ...get-ppc-fix-xscvqpdp-register-access.patch |  41 +++
 ...rget-ppc-move-xscvqpdp-to-decodetree.patch | 130 +
 ...tore_fpscr-doesn-t-update-bits-0-to-.patch |  70 +
 ...get-ppc-Introduce-TRANS-FLAGS-macros.patch | 133 +
 ...get-ppc-Implement-Vector-Expand-Mask.patch | 105 +++
 ...et-ppc-Implement-Vector-Extract-Mask.patch | 141 ++
 ...ppc-Implement-Vector-Mask-Move-insns.patch | 187 +
 ...xs-n-madd-am-ds-p-xs-n-msub-am-ds-p-.patch | 258 ++
 ...mplement-xs-n-maddqp-o-xs-n-msubqp-o.patch | 174 
 22 files changed, 2400 insertions(+)
 create mode 100644 
meta/recipes-devtools/qemu/qemu/0001-softfloat-Extend-float_exception_flags-to-16-bits.patch
 create mode 100644 
meta/recipes-devtools/qemu/qemu/0002-softfloat-Add-flag-specific-to-Inf-Inf.patch
 create mode 100644 
meta/recipes-devtools/qemu/qemu/0003-softfloat-Add-flag-specific-to-Inf-0.patch
 create mode 100644 
meta/recipes-devtools/qemu/qemu/0004-softfloat-Add-flags-specific-to-Inf-Inf-and-0-0.patch
 create mode 100644 
meta/recipes-devtools/qemu/qemu/0005-softfloat-Add-flag-specific-to-signaling-nans.patch
 create mode 100644 
meta/recipes-devtools/qemu/qemu/0006-target-ppc-Update-float_invalid_op_addsub-for-new-fl.patch
 create mode 100644 
meta/recipes-devtools/qemu/qemu/0007-target-ppc-Update-float_invalid_op_mul-for-new-flags.patch
 create mode 100644 
meta/recipes-devtools/qemu/qemu/0008-target-ppc-Update-float_invalid_op_div-for-new-flags.patch
 create mode 100644 
meta/recipes-devtools/qemu/qemu/0009-target-ppc-Update-fmadd-for-new-flags.patch
 create mode 100644 
meta/recipes-devtools/qemu/q

[OE-core][kirkstone 09/13] uninative: Upgrade to 3.7 to work with glibc 2.36

2022-10-17 Thread Steve Sakoman 
From: Michael Halstead 

Update uninative to work with the new glibc 2.36 version

Signed-off-by: Michael Halstead 
Signed-off-by: Richard Purdie 
(cherry picked from commit 410226b053e14e32add1f9b4b811f84a1c445a7c)
Signed-off-by: Steve Sakoman 
---
 meta/conf/distro/include/yocto-uninative.inc | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta/conf/distro/include/yocto-uninative.inc 
b/meta/conf/distro/include/yocto-uninative.inc
index 411fe45a24..7012db441b 100644
--- a/meta/conf/distro/include/yocto-uninative.inc
+++ b/meta/conf/distro/include/yocto-uninative.inc
@@ -6,10 +6,10 @@
 # to the distro running on the build machine.
 #
 
-UNINATIVE_MAXGLIBCVERSION = "2.35"
-UNINATIVE_VERSION = "3.6"
+UNINATIVE_MAXGLIBCVERSION = "2.36"
+UNINATIVE_VERSION = "3.7"
 
 UNINATIVE_URL ?= 
"http://downloads.yoctoproject.org/releases/uninative/${UNINATIVE_VERSION}/";
-UNINATIVE_CHECKSUM[aarch64] ?= 
"d64831cf2792c8e470c2e42230660e1a8e5de56a579cdd59978791f663c2f3ed"
-UNINATIVE_CHECKSUM[i686] ?= 
"2f0ee9b66b1bb2c85e2b592fb3c9c7f5d77399fa638d74961330cdb8de34ca3b"
-UNINATIVE_CHECKSUM[x86_64] ?= 
"9bfc4c970495b3716b2f9e52c4df9f968c02463a9a95000f6657fbc3fde1f098"
+UNINATIVE_CHECKSUM[aarch64] ?= 
"6a29bcae4b5b716d2d520e18800b33943b65f8a835eac1ff8793fc5ee65b4be6"
+UNINATIVE_CHECKSUM[i686] ?= 
"3f6d52e64996570c716108d49f8108baccf499a283bbefae438c7266b7a93305"
+UNINATIVE_CHECKSUM[x86_64] ?= 
"b110bf2e10fe420f5ca2f3ec55f048ee5f0a54c7e34856a3594e51eb2aea0570"
-- 
2.25.1


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

[OE-core][kirkstone 10/13] image_types_wic.bbclass: fix cross binutils dependency

2022-10-17 Thread Steve Sakoman 
From: Chen Qi 

Enable multilib and wic at the same time and we'll meet the
following error.

  ERROR: Nothing PROVIDES 'virtual/i686-wrsmllib32-linux-binutils'

Adjust the dependency to take multilib into consideration.

Signed-off-by: Chen Qi 
Signed-off-by: Luca Ceresoli 
(cherry picked from commit 958ee0eede859bdba659e3343856b1c226207854)
Signed-off-by: Steve Sakoman 
---
 meta/classes/image_types_wic.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/image_types_wic.bbclass 
b/meta/classes/image_types_wic.bbclass
index 5374d6125e..6453dd1b74 100644
--- a/meta/classes/image_types_wic.bbclass
+++ b/meta/classes/image_types_wic.bbclass
@@ -85,7 +85,7 @@ do_image_wic[deptask] += "do_image_complete"
 WKS_FILE_DEPENDS_DEFAULT = '${@bb.utils.contains_any("BUILD_ARCH", [ 'x86_64', 
'i686' ], "syslinux-native", "",d)}'
 WKS_FILE_DEPENDS_DEFAULT += "bmap-tools-native cdrtools-native 
btrfs-tools-native squashfs-tools-native e2fsprogs-native"
 # Unified kernel images need objcopy
-WKS_FILE_DEPENDS_DEFAULT += "virtual/${TARGET_PREFIX}binutils"
+WKS_FILE_DEPENDS_DEFAULT += "virtual/${MLPREFIX}${TARGET_PREFIX}binutils"
 WKS_FILE_DEPENDS_BOOTLOADERS = ""
 WKS_FILE_DEPENDS_BOOTLOADERS:x86 = "syslinux grub-efi systemd-boot os-release"
 WKS_FILE_DEPENDS_BOOTLOADERS:x86-64 = "syslinux grub-efi systemd-boot 
os-release"
-- 
2.25.1


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

[OE-core][kirkstone 11/13] linux-yocto-dev: add qemuarm64

2022-10-17 Thread Steve Sakoman 
From: Xiangyu Chen 

Mark the qemuarm64 as compatible

Signed-off-by: Xiangyu Chen 
Signed-off-by: Steve Sakoman 
---
 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 75b1cb2a49..403993486b 100644
--- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
@@ -50,7 +50,7 @@ PACKAGECONFIG[dt-validation] = ",,python3-dtschema-native"
 # we need the wrappers if validation isn't in the packageconfig
 DEPENDS += "${@bb.utils.contains('PACKAGECONFIG', 'dt-validation', '', 
'python3-dtschema-wrapper-native', d)}"
 
-COMPATIBLE_MACHINE = 
"^(qemuarm|qemux86|qemuppc|qemumips|qemumips64|qemux86-64|qemuriscv32|qemuriscv64)$"
+COMPATIBLE_MACHINE = 
"^(qemuarm|qemuarm64|qemux86|qemuppc|qemumips|qemumips64|qemux86-64|qemuriscv32|qemuriscv64)$"
 
 KERNEL_DEVICETREE:qemuarmv5 = "versatile-pb.dtb"
 
-- 
2.25.1


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

[OE-core][kirkstone 12/13] own-mirrors: add crate

2022-10-17 Thread Steve Sakoman 
From: Adrian Freihofer 

Support downloading crate files from a mirror at SOURCE_MIRROR_URL.

Signed-off-by: Adrian Freihofer 
Signed-off-by: Steve Sakoman 
---
 meta/classes/own-mirrors.bbclass | 1 +
 meta/classes/sanity.bbclass  | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/classes/own-mirrors.bbclass b/meta/classes/own-mirrors.bbclass
index ef972740ce..30c7ccd8e7 100644
--- a/meta/classes/own-mirrors.bbclass
+++ b/meta/classes/own-mirrors.bbclass
@@ -11,4 +11,5 @@ https?://.*/.*  ${SOURCE_MIRROR_URL} \
 ftp://.*/.* ${SOURCE_MIRROR_URL} \
 npm://.*/?.*${SOURCE_MIRROR_URL} \
 s3://.*/.*  ${SOURCE_MIRROR_URL} \
+crate://.*/.*   ${SOURCE_MIRROR_URL} \
 "
diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
index a79e36b594..5c97effb96 100644
--- a/meta/classes/sanity.bbclass
+++ b/meta/classes/sanity.bbclass
@@ -859,7 +859,7 @@ def check_sanity_everybuild(status, d):
 mirror_vars = ['MIRRORS', 'PREMIRRORS', 'SSTATE_MIRRORS']
 protocols = ['http', 'ftp', 'file', 'https', \
  'git', 'gitsm', 'hg', 'osc', 'p4', 'svn', \
- 'bzr', 'cvs', 'npm', 'sftp', 'ssh', 's3', 'az', 'ftps']
+ 'bzr', 'cvs', 'npm', 'sftp', 'ssh', 's3', 'az', 'ftps', 
'crate']
 for mirror_var in mirror_vars:
 mirrors = (d.getVar(mirror_var) or '').replace('\\n', ' ').split()
 
-- 
2.25.1


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

[OE-core][kirkstone 13/13] lttng-modules: Fix crash on powerpc64

2022-10-17 Thread Steve Sakoman 
From: He Zhe 

Backport a patch to fix the following on powerpc64 ABIv2.

root@qemuppc64:~# lttng create trace_session --live -U net://127.0.0.1
Spawning a session daemon
lttng_kretprobes: loading out-of-tree module taints kernel.
BUG: Unable to handle kernel data access on read at 0xfff8
Faulting instruction address: 0xc01f6fd0
Oops: Kernel access of bad area, sig: 11 [#1]


Signed-off-by: He Zhe 
Signed-off-by: Steve Sakoman 
---
 ...4-fix-kernel-crash-caused-by-do_get_.patch | 94 +++
 .../lttng/lttng-modules_2.13.4.bb |  1 +
 2 files changed, 95 insertions(+)
 create mode 100644 
meta/recipes-kernel/lttng/lttng-modules/0001-wrapper-powerpc64-fix-kernel-crash-caused-by-do_get_.patch

diff --git 
a/meta/recipes-kernel/lttng/lttng-modules/0001-wrapper-powerpc64-fix-kernel-crash-caused-by-do_get_.patch
 
b/meta/recipes-kernel/lttng/lttng-modules/0001-wrapper-powerpc64-fix-kernel-crash-caused-by-do_get_.patch
new file mode 100644
index 00..b3b191c7ac
--- /dev/null
+++ 
b/meta/recipes-kernel/lttng/lttng-modules/0001-wrapper-powerpc64-fix-kernel-crash-caused-by-do_get_.patch
@@ -0,0 +1,94 @@
+From 480cce4315ce5bf59a509e8a53a52545f393de68 Mon Sep 17 00:00:00 2001
+From: He Zhe 
+Date: Tue, 27 Sep 2022 15:59:42 +0800
+Subject: [PATCH] wrapper: powerpc64: fix kernel crash caused by
+ do_get_kallsyms
+
+Kernel crashes on powerpc64 ABIv2 as follow when lttng_tracer initializes,
+since do_get_kallsyms in lttng_wrapper fails to return a proper address of
+kallsyms_lookup_name.
+
+root@qemuppc64:~# lttng create trace_session --live -U net://127.0.0.1
+Spawning a session daemon
+lttng_kretprobes: loading out-of-tree module taints kernel.
+BUG: Unable to handle kernel data access on read at 0xfff8
+Faulting instruction address: 0xc01f6fd0
+Oops: Kernel access of bad area, sig: 11 [#1]
+
+NIP [c01f6fd0] module_kallsyms_lookup_name+0xf0/0x180
+LR [c01f6f28] module_kallsyms_lookup_name+0x48/0x180
+Call Trace:
+module_kallsyms_lookup_name+0x34/0x180 (unreliable)
+kallsyms_lookup_name+0x258/0x2b0
+wrapper_kallsyms_lookup_name+0x4c/0xd0 [lttng_wrapper]
+wrapper_get_pfnblock_flags_mask_init+0x28/0x60 [lttng_wrapper]
+lttng_events_init+0x40/0x344 [lttng_tracer]
+do_one_initcall+0x78/0x340
+do_init_module+0x6c/0x2f0
+__do_sys_finit_module+0xd0/0x120
+system_call_exception+0x194/0x2f0
+system_call_vectored_common+0xe8/0x278
+
+
+do_get_kallsyms makes use of kprobe_register and in turn kprobe_lookup_name
+to get the address of the kernel function kallsyms_lookup_name. In case of
+PPC64_ELF_ABI_v2, when kprobes are placed at function entry,
+kprobe_lookup_name adjusts the global entry point of the function returned
+by kallsyms_lookup_name to the local entry point(at some fixed offset of
+global one). This adjustment is all for kprobes to be able to work properly.
+Global and local entry point are defined in powerpc64 ABIv2.
+
+When the local entry point is given, some instructions at the beginning of
+the function are skipped and thus causes the above kernel crash. We just
+want to make a simple function call which needs global entry point.
+
+This patch adds 4 bytes which is the length of one instruction to
+kallsyms_lookup_name so that it will not trigger the global to local
+adjustment, and then substracts 4 bytes from the returned address. See the
+following kernel change for more details.
+
+https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=290e3070762ac80e5fc4087d8c4de7e3f1d90aca
+
+Upstream-Status: Backport
+
+Signed-off-by: He Zhe 
+Signed-off-by: Mathieu Desnoyers 
+Change-Id: I34e68e886b97e3976d0b5e25be295a8bb866c1a4
+---
+ src/wrapper/kallsyms.c | 16 
+ 1 file changed, 16 insertions(+)
+
+diff --git a/src/wrapper/kallsyms.c b/src/wrapper/kallsyms.c
+index d2848764..93017adc 100644
+--- a/src/wrapper/kallsyms.c
 b/src/wrapper/kallsyms.c
+@@ -39,10 +39,26 @@ unsigned long do_get_kallsyms(void)
+   memset(&probe, 0, sizeof(probe));
+   probe.pre_handler = dummy_kprobe_handler;
+   probe.symbol_name = "kallsyms_lookup_name";
++#ifdef PPC64_ELF_ABI_v2
++  /*
++   * With powerpc64 ABIv2, we need the global entry point of
++   * kallsyms_lookup_name to call it later, while kprobe_register would
++   * automatically adjust the global entry point to the local entry point,
++   * when a kprobe was registered at a function entry. So we add 4 bytes
++   * which is the length of one instruction to kallsyms_lookup_name to
++   * avoid the adjustment.
++   */
++  probe.offset = 4;
++#endif
+   ret = register_kprobe(&probe);
+   if (ret)
+   return 0;
++#ifdef PPC64_ELF_ABI_v2
++  /* Substract 4 bytes to get what we originally want */
++  addr = (unsigned long)(((char *)probe.addr) - 4);
++#else
+   addr = (unsigned long)probe.addr;
++#endif
+ #ifdef CONFIG_ARM
+ #ifdef CONFIG_THUMB2_KERNEL
+   if (addr)
+-- 
+2.17.

[OE-core] [PATCH] kbd: package some fonts as restricted

2022-10-17 Thread Randy MacLeod 
The distribution terms of the Agafari fonts as described in
data/consolefonts/README.Ethiopic is:

Agafari:
  Donated by the Ethiopian Science and Technology Commission
   or  and may be redistributed
  for non-commercial use under Unix environments only.

so package them seperately to make it easier for affected users
to avoid installing the fonts.

Signed-off-by: Randy MacLeod 
---
 meta/recipes-core/kbd/kbd_2.5.1.bb | 6 --
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-core/kbd/kbd_2.5.1.bb 
b/meta/recipes-core/kbd/kbd_2.5.1.bb
index aa3ab6e121..8822cdbef4 100644
--- a/meta/recipes-core/kbd/kbd_2.5.1.bb
+++ b/meta/recipes-core/kbd/kbd_2.5.1.bb
@@ -23,9 +23,11 @@ PACKAGECONFIG ?= "${@bb.utils.filter('DISTRO_FEATURES', 
'pam', d)} \
 
 PACKAGECONFIG[pam] = "--enable-vlock, --disable-vlock, libpam,"
 
-PACKAGES += "${PN}-consolefonts ${PN}-keymaps ${PN}-unimaps ${PN}-consoletrans"
+PACKAGES += "${PN}-consolefonts ${PN}-consolefonts-restricted ${PN}-keymaps 
${PN}-unimaps ${PN}-consoletrans"
 
-FILES:${PN}-consolefonts = "${datadir}/consolefonts"
+# Package some fonts as restricted, see README.Ethiopic
+FILES:${PN}-consolefonts = "${datadir}/consolefonts/[a-zB-Z0-9]*"
+FILES:${PN}-consolefonts-restricted = "${datadir}/consolefonts/Agafari*"
 FILES:${PN}-consoletrans = "${datadir}/consoletrans"
 FILES:${PN}-keymaps = "${datadir}/keymaps"
 FILES:${PN}-unimaps = "${datadir}/unimaps"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171932): 
https://lists.openembedded.org/g/openembedded-core/message/171932
Mute This Topic: https://lists.openembedded.org/mt/94398712/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] linux-firmware: package amdgpu firmware

2022-10-17 Thread Vincent Davis Jr 
Add packages for the firmware required by amdgpu kernel driver.

Signed-off-by: Vincent Davis Jr 
---
 .../linux-firmware/linux-firmware_20220913.bb| 12 
 1 file changed, 12 insertions(+)

diff --git a/meta/recipes-kernel/linux-firmware/linux-firmware_20220913.bb 
b/meta/recipes-kernel/linux-firmware/linux-firmware_20220913.bb
index 45c9d0e861..bf15e53472 100644
--- a/meta/recipes-kernel/linux-firmware/linux-firmware_20220913.bb
+++ b/meta/recipes-kernel/linux-firmware/linux-firmware_20220913.bb
@@ -228,6 +228,7 @@ do_install() {
 PACKAGES =+ "${PN}-ralink-license ${PN}-ralink \
  ${PN}-mt7601u-license ${PN}-mt7601u \
  ${PN}-radeon-license ${PN}-radeon \
+ ${PN}-amdgpu-license ${PN}-amdgpu \
  ${PN}-marvell-license ${PN}-pcie8897 ${PN}-pcie8997 \
  ${PN}-sd8686 ${PN}-sd8688 ${PN}-sd8787 ${PN}-sd8797 ${PN}-sd8801 \
  ${PN}-sd8887 ${PN}-sd8897 ${PN}-sd8997 ${PN}-usb8997 \
@@ -428,6 +429,17 @@ FILES:${PN}-radeon = " \
 
 RDEPENDS:${PN}-radeon += "${PN}-radeon-license"
 
+# For amdgpu
+LICENSE:${PN}-amdgpu = "Firmware-amdgpu"
+LICENSE:${PN}-amdgpu-license = "Firmware-amdgpu"
+
+FILES:${PN}-amdgpu-license = "${nonarch_base_libdir}/firmware/LICENSE.amdgpu"
+FILES:${PN}-amdgpu = " \
+  ${nonarch_base_libdir}/firmware/amdgpu \
+"
+
+RDEPENDS:${PN}-amdgpu += "${PN}-amdgpu-license"
+
 # For lontium
 LICENSE:${PN}-lt9611uxc = "Firmware-Lontium"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171933): 
https://lists.openembedded.org/g/openembedded-core/message/171933
Mute This Topic: https://lists.openembedded.org/mt/94403062/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] Nothing to say. Signed-off-by: yanxk

2022-10-17 Thread Yanxinkuan.FNST 
From: yanxk 

---
 nothing_but_email |1 +
 1 files changed, 1 insertions(+), 0 deletions(-)
 create mode 100644 nothing_but_email

diff --git a/nothing_but_email b/nothing_but_email
new file mode 100644
index 000..08b0898
--- /dev/null
+++ b/nothing_but_email
@@ -0,0 +1 @@
+hi?
-- 
1.7.1


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

[OE-core] scripts: include all dependencies in eSDK

2022-10-17 Thread Andrej Valek 
Without this recursive dependency on do_build task, eSDK includes only
direct image dependencies and there for devtool recipe has to rebuild
them all.

Resolves: [YOCTO#14626]

Signed-off-by: Andrej Valek 
Signed-off-by: Peter Marko 
---
 scripts/oe-check-sstate | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/oe-check-sstate b/scripts/oe-check-sstate
index f4cc5869de..5c185fa85e 100755
--- a/scripts/oe-check-sstate
+++ b/scripts/oe-check-sstate
@@ -52,7 +52,7 @@ def check(args):
 
 try:
 output = subprocess.check_output(
-'bitbake -n %s' % ' '.join(args.target),
+'bitbake -n --runall build %s' % ' '.join(args.target),
 stderr=subprocess.STDOUT,
 env=env,
 shell=True)
-- 
2.34.3


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