[OE-Core][kirkstone][master][PATCH] rng-tools: Add Arm aarch64 CPU specific configuration to address excessive CPU usage on startup

[Xiangyu Chen]

With the default jitter options aarch64 CPU-based devices typically experience 
continuous
high CPU utilisation for several minutes after rngd starts.

Accoring to the rng-tools issue #150[1] and comments[2],in order to address 
this,
the following configuration changes have been made, those configurations
also can be found on Alpine Linux[3]:

- reduce the number of threads used to 1 in total, rather than 1 per core.
- reduce the buffer size from 16535 to 4133 which reduces the time taken
  to fill the buffer (and so reduces the duration of CPU load).

[1] https://github.com/nhorman/rng-tools/issues/150
[2] https://github.com/nhorman/rng-tools/issues/150#issuecomment-953079212
[3] https://git.alpinelinux.org/aports/tree/main/rng-tools/rngd.confd-arm

Signed-off-by: Xiangyu Chen 
---
 .../rng-tools/rng-tools/default.aarch64   | 11 +++
 meta/recipes-support/rng-tools/rng-tools_6.15.bb  |  5 +
 2 files changed, 16 insertions(+)
 create mode 100644 meta/recipes-support/rng-tools/rng-tools/default.aarch64

diff --git a/meta/recipes-support/rng-tools/rng-tools/default.aarch64 
b/meta/recipes-support/rng-tools/rng-tools/default.aarch64
new file mode 100644
index 00..5a2fbcc9ef
--- /dev/null
+++ b/meta/recipes-support/rng-tools/rng-tools/default.aarch64
@@ -0,0 +1,11 @@
+# With the default jitter options Arm CPU-based devices typically experience
+# continuous high CPU utilisation for several minutes after rngd starts.
+# See https://gitlab.alpinelinux.org/alpine/aports/-/issues/13035 and
+# https://github.com/nhorman/rng-tools/issues/150
+# In order to address this the following configuration changes have been made:
+#
+#   - reduce the number of threads used to 1 in total, rather than 1 per core.
+#   - reduce the buffer size from 16535 to 4133 which reduces the time taken
+# to fill the buffer (and so reduces the duration of CPU load).
+#
+EXTRA_ARGS="-r /dev/hwrng -O jitter:buffer_size:4133 -O 
jitter:refill_thresh:4133 -O jitter:thread_count:1"
diff --git a/meta/recipes-support/rng-tools/rng-tools_6.15.bb 
b/meta/recipes-support/rng-tools/rng-tools_6.15.bb
index 0696351903..e1f6b2ad77 100644
--- a/meta/recipes-support/rng-tools/rng-tools_6.15.bb
+++ b/meta/recipes-support/rng-tools/rng-tools_6.15.bb
@@ -12,6 +12,7 @@ SRC_URI = 
"git://github.com/nhorman/rng-tools.git;branch=master;protocol=https \
file://init \
file://default \
file://rngd.service \
+   file://default.aarch64 \
"
 SRCREV = "381f69828b782afda574f259c1b7549f48f9bb77"
 
@@ -59,3 +60,7 @@ do_install:append() {
 ${D}${systemd_system_unitdir}/rngd.service
 fi
 }
+
+do_install:append:aarch64() {
+install -Dm 0644 ${WORKDIR}/default.aarch64 
${D}${sysconfdir}/default/rng-tools
+}
-- 
2.34.1


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

[OE-core] [meta-oe][PATCH V3] bc: Add ptest.

[Yan Xin Kuan]

From: Yan Xinkuan 

Add package test function for OSS 'bc', using bc in the
system to do calculation jobs according to the .b files
from the source code file of 'bc'.

Test example as below:
..
.00673400673400673400
“PASS: bc/div.b”
99836408603283573660347145562829683495827909199408566065153345558783\
9427595471.89114392327665123852
“PASS: bc/exp.b”
length(b)= 1406
“PASS: bc/fact.b”
..

If bc runs the .b files and does not crash, it would 'PASS',
otherwise it would 'FAIL'.

I ran ptest with Intel CORE i5 4450, in qemux86-64, the whole
test took up to 124 seconds, so it should be a slow test.

Thanks to Ross Burton for the professional guidance.

Signed-off-by: Yan Xinkuan 
---
 meta/conf/distro/include/ptest-packagelists.inc | 1 +
 meta/recipes-extended/bc/bc/run-ptest   | 9 +
 meta/recipes-extended/bc/bc_1.07.1.bb   | 9 +++--
 3 files changed, 17 insertions(+), 2 deletions(-)
 create mode 100644 meta/recipes-extended/bc/bc/run-ptest

diff --git a/meta/conf/distro/include/ptest-packagelists.inc 
b/meta/conf/distro/include/ptest-packagelists.inc
index 56088e4e66..5cbed54cc5 100644
--- a/meta/conf/distro/include/ptest-packagelists.inc
+++ b/meta/conf/distro/include/ptest-packagelists.inc
@@ -100,6 +100,7 @@ PTESTS_SLOW = "\
 tcl-ptest \
 util-linux-ptest \
 valgrind-ptest \
+bc-ptest \
 "

 PTESTS_SLOW:remove:riscv64 = "valgrind-ptest"
diff --git a/meta/recipes-extended/bc/bc/run-ptest 
b/meta/recipes-extended/bc/bc/run-ptest
new file mode 100644
index 00..da2156f8cd
--- /dev/null
+++ b/meta/recipes-extended/bc/bc/run-ptest
@@ -0,0 +1,9 @@
+#! /bin/sh
+
+for TEST in *.b; do
+   if bc -l $TEST 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172291): 
https://lists.openembedded.org/g/openembedded-core/message/172291
Mute This Topic: https://lists.openembedded.org/mt/94680520/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [meta-oe][PATCH V3] bc: Add ptest.

[Alexander Kanavin]

Was kvm enabled in qemu?

Alex

On Mon 31. Oct 2022 at 8.59, Yan Xin Kuan  wrote:

> From: Yan Xinkuan 
>
> Add package test function for OSS 'bc', using bc in the
> system to do calculation jobs according to the .b files
> from the source code file of 'bc'.
>
> Test example as below:
> ..
> .00673400673400673400
> “PASS: bc/div.b”
> 99836408603283573660347145562829683495827909199408566065153345558783\
> 9427595471.89114392327665123852
> “PASS: bc/exp.b”
> length(b)= 1406
> “PASS: bc/fact.b”
> ..
>
> If bc runs the .b files and does not crash, it would 'PASS',
> otherwise it would 'FAIL'.
>
> I ran ptest with Intel CORE i5 4450, in qemux86-64, the whole
> test took up to 124 seconds, so it should be a slow test.
>
> Thanks to Ross Burton for the professional guidance.
>
> Signed-off-by: Yan Xinkuan 
> ---
>  meta/conf/distro/include/ptest-packagelists.inc | 1 +
>  meta/recipes-extended/bc/bc/run-ptest   | 9 +
>  meta/recipes-extended/bc/bc_1.07.1.bb   | 9 +++--
>  3 files changed, 17 insertions(+), 2 deletions(-)
>  create mode 100644 meta/recipes-extended/bc/bc/run-ptest
>
> diff --git a/meta/conf/distro/include/ptest-packagelists.inc
> b/meta/conf/distro/include/ptest-packagelists.inc
> index 56088e4e66..5cbed54cc5 100644
> --- a/meta/conf/distro/include/ptest-packagelists.inc
> +++ b/meta/conf/distro/include/ptest-packagelists.inc
> @@ -100,6 +100,7 @@ PTESTS_SLOW = "\
>  tcl-ptest \
>  util-linux-ptest \
>  valgrind-ptest \
> +bc-ptest \
>  "
>
>  PTESTS_SLOW:remove:riscv64 = "valgrind-ptest"
> diff --git a/meta/recipes-extended/bc/bc/run-ptest
> b/meta/recipes-extended/bc/bc/run-ptest
> new file mode 100644
> index 00..da2156f8cd
> --- /dev/null
> +++ b/meta/recipes-extended/bc/bc/run-ptest
> @@ -0,0 +1,9 @@
> +#! /bin/sh
> +
> +for TEST in *.b; do
> +   if bc -l $TEST  +   echo “PASS: bc/$TEST”
> +else
> +   echo “FAIL: bc/$TEST”
> +fi
> +done
> diff --git a/meta/recipes-extended/bc/bc_1.07.1.bb
> b/meta/recipes-extended/bc/bc_1.07.1.bb
> index 1bec76bb2a..178588f11b 100644
> --- a/meta/recipes-extended/bc/bc_1.07.1.bb
> +++ b/meta/recipes-extended/bc/bc_1.07.1.bb
> @@ -15,11 +15,12 @@ DEPENDS = "flex-native"
>  SRC_URI = "${GNU_MIRROR}/${BPN}/${BP}.tar.gz \
> file://no-gen-libmath.patch \
> file://libmath.h \
> -   file://0001-dc-fix-exit-code-of-q-command.patch"
> +   file://0001-dc-fix-exit-code-of-q-command.patch \
> +   file://run-ptest"
>  SRC_URI[md5sum] = "cda93857418655ea43590736fc3ca9fc"
>  SRC_URI[sha256sum] =
> "62adfca89b0a1c0164c2cdca59ca210c1d44c3ffc46daf9931cf4942664cb02a"
>
> -inherit autotools texinfo update-alternatives
> +inherit autotools texinfo update-alternatives ptest
>
>  PACKAGECONFIG ??= "readline"
>  PACKAGECONFIG[readline] = "--with-readline,--without-readline,readline"
> @@ -29,6 +30,10 @@ do_compile:prepend() {
>  cp -f ${WORKDIR}/libmath.h ${B}/bc/libmath.h
>  }
>
> +do_install_ptest() {
> +install ${S}/Test/*.b ${D}${PTEST_PATH}
> +}
> +
>  ALTERNATIVE:${PN} = "bc dc"
>  ALTERNATIVE_PRIORITY = "100"
>
> --
> 2.25.1
>
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172292): 
https://lists.openembedded.org/g/openembedded-core/message/172292
Mute This Topic: https://lists.openembedded.org/mt/94680520/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] Add nativesdk of systemd-systemctl

[wangmy]

From: Wang Mingyu 

Signed-off-by: Wang Mingyu 
---
 .../systemd/nativesdk-systemd-systemctl.bb  | 17 +
 1 file changed, 17 insertions(+)
 create mode 100644 meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb

diff --git a/meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb 
b/meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb
new file mode 100644
index 00..66b5ec5e6e
--- /dev/null
+++ b/meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb
@@ -0,0 +1,17 @@
+SUMMARY = "Wrapper for enabling systemd services"
+
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
+
+PR = "r0"
+
+inherit nativesdk
+
+SRC_URI = "file://systemctl"
+
+S = "${WORKDIR}"
+
+do_install() {
+   install -d ${D}${bindir}
+   install -m 0755 ${WORKDIR}/systemctl ${D}${bindir}
+}
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172293): 
https://lists.openembedded.org/g/openembedded-core/message/172293
Mute This Topic: https://lists.openembedded.org/mt/94680777/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] Add nativesdk of systemd-systemctl

[Alexander Kanavin]

You need to explain the use case. Why is this beneficial to have on oe-core?

Alex

On Mon, 31 Oct 2022 at 09:17, wangmy  wrote:
>
> From: Wang Mingyu 
>
> Signed-off-by: Wang Mingyu 
> ---
>  .../systemd/nativesdk-systemd-systemctl.bb  | 17 +
>  1 file changed, 17 insertions(+)
>  create mode 100644 meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb
>
> diff --git a/meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb 
> b/meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb
> new file mode 100644
> index 00..66b5ec5e6e
> --- /dev/null
> +++ b/meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb
> @@ -0,0 +1,17 @@
> +SUMMARY = "Wrapper for enabling systemd services"
> +
> +LICENSE = "MIT"
> +LIC_FILES_CHKSUM = 
> "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
> +
> +PR = "r0"
> +
> +inherit nativesdk
> +
> +SRC_URI = "file://systemctl"
> +
> +S = "${WORKDIR}"
> +
> +do_install() {
> +   install -d ${D}${bindir}
> +   install -m 0755 ${WORKDIR}/systemctl ${D}${bindir}
> +}
> --
> 2.25.1
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172294): 
https://lists.openembedded.org/g/openembedded-core/message/172294
Mute This Topic: https://lists.openembedded.org/mt/94680777/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] Public: Re: [meta-oe][PATCH V3] bc: Add ptest.

[Alexander Kanavin]

In that case, the benchmark for the test was not performed correctly.
You need to use the kvm parameter.

Alex

On Mon, 31 Oct 2022 at 09:27, Yan Xin Kuan  wrote:
>
> runqemu was used, but no kvm parameter passed.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172295): 
https://lists.openembedded.org/g/openembedded-core/message/172295
Mute This Topic: https://lists.openembedded.org/mt/94680896/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] Add nativesdk of systemd-systemctl

[wangmy]

I need to use nativesdk-systemd-systemctl. 
I added this file in meta-oe, and the maintainers received it. 
However, they suggested that it was better to contribute to oe-core.

  --
Best Regards
---
Wang Mingyu
Development Dept.I
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST) No. 6 Wenzhu Road, 
Nanjing, 210012, China
TEL: +86+25-86630566-8568
COINS: 79988548
FAX: +86+25-83317685
MAIL: wan...@fujitsu.com
http://www.fujitsu.com/cn/fnst/

> -Original Message-
> From: Alexander Kanavin 
> Sent: Monday, October 31, 2022 4:24 PM
> To: Wang, Mingyu/王 鸣瑜 
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] Add nativesdk of systemd-systemctl
> 
> You need to explain the use case. Why is this beneficial to have on oe-core?
> 
> Alex
> 
> On Mon, 31 Oct 2022 at 09:17, wangmy  wrote:
> >
> > From: Wang Mingyu 
> >
> > Signed-off-by: Wang Mingyu 
> > ---
> >  .../systemd/nativesdk-systemd-systemctl.bb  | 17
> +
> >  1 file changed, 17 insertions(+)
> >  create mode 100644
> > meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb
> >
> > diff --git a/meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb
> > b/meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb
> > new file mode 100644
> > index 00..66b5ec5e6e
> > --- /dev/null
> > +++ b/meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb
> > @@ -0,0 +1,17 @@
> > +SUMMARY = "Wrapper for enabling systemd services"
> > +
> > +LICENSE = "MIT"
> > +LIC_FILES_CHKSUM =
> "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de
> 20420"
> > +
> > +PR = "r0"
> > +
> > +inherit nativesdk
> > +
> > +SRC_URI = "file://systemctl"
> > +
> > +S = "${WORKDIR}"
> > +
> > +do_install() {
> > +   install -d ${D}${bindir}
> > +   install -m 0755 ${WORKDIR}/systemctl ${D}${bindir} }
> > --
> > 2.25.1
> >
> >
> > 
> >

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172296): 
https://lists.openembedded.org/g/openembedded-core/message/172296
Mute This Topic: https://lists.openembedded.org/mt/94680777/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] Add nativesdk of systemd-systemctl

[Alexander Kanavin]

You need to explain why this is useful to the broader community. What
is the use case? Each addition to oe-core adds to the maintenance
costs, so it needs to be justified and explained.

Alex

On Mon, 31 Oct 2022 at 09:38, wan...@fujitsu.com  wrote:
>
> I need to use nativesdk-systemd-systemctl.
> I added this file in meta-oe, and the maintainers received it.
> However, they suggested that it was better to contribute to oe-core.
>
>   --
> Best Regards
> ---
> Wang Mingyu
> Development Dept.I
> Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST) No. 6 Wenzhu Road, 
> Nanjing, 210012, China
> TEL: +86+25-86630566-8568
> COINS: 79988548
> FAX: +86+25-83317685
> MAIL: wan...@fujitsu.com
> http://www.fujitsu.com/cn/fnst/
>
> > -Original Message-
> > From: Alexander Kanavin 
> > Sent: Monday, October 31, 2022 4:24 PM
> > To: Wang, Mingyu/王 鸣瑜 
> > Cc: openembedded-core@lists.openembedded.org
> > Subject: Re: [OE-core] [PATCH] Add nativesdk of systemd-systemctl
> >
> > You need to explain the use case. Why is this beneficial to have on oe-core?
> >
> > Alex
> >
> > On Mon, 31 Oct 2022 at 09:17, wangmy  wrote:
> > >
> > > From: Wang Mingyu 
> > >
> > > Signed-off-by: Wang Mingyu 
> > > ---
> > >  .../systemd/nativesdk-systemd-systemctl.bb  | 17
> > +
> > >  1 file changed, 17 insertions(+)
> > >  create mode 100644
> > > meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb
> > >
> > > diff --git a/meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb
> > > b/meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb
> > > new file mode 100644
> > > index 00..66b5ec5e6e
> > > --- /dev/null
> > > +++ b/meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb
> > > @@ -0,0 +1,17 @@
> > > +SUMMARY = "Wrapper for enabling systemd services"
> > > +
> > > +LICENSE = "MIT"
> > > +LIC_FILES_CHKSUM =
> > "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de
> > 20420"
> > > +
> > > +PR = "r0"
> > > +
> > > +inherit nativesdk
> > > +
> > > +SRC_URI = "file://systemctl"
> > > +
> > > +S = "${WORKDIR}"
> > > +
> > > +do_install() {
> > > +   install -d ${D}${bindir}
> > > +   install -m 0755 ${WORKDIR}/systemctl ${D}${bindir} }
> > > --
> > > 2.25.1
> > >
> > >
> > > 
> > >

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

Public: Re: [meta-oe][oe-core][PATCH V3] bc: Add ptest.

[Yan Xin Kuan]

Sure.

I did not intend to make it private.

I just do not know how, it takes time for new commers to get used to this 
mailling list kind of management.

I will find myself some docs to look into.

Maybe this is not working, for I can not see our conversation on the website:
"Public: Re: [meta-oe][PATCH V3] bc: Add ptest."

I switched it to this:
Public: Re: [meta-oe][oe-core][PATCH V3] bc: Add ptest.

Not pretty sure weather it works or not.

Nevermind, I would find some guidence in oe docs.

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

Re: Public: Re: [meta-oe][oe-core][PATCH V3] bc: Add ptest.

[Alexander Kanavin]

This conversation is on the mailing list now.

When writing a response, you need to check the list of recipients in
your message (typically in the 'To:' field), which should include
openembedded-core@lists.openembedded.org and then it will go to the
list.

Alex

On Mon, 31 Oct 2022 at 10:40, Yan Xin Kuan  wrote:
>
> Sure.
>
> I did not intend to make it private.
>
> I just do not know how, it takes time for new commers to get used to this 
> mailling list kind of management.
>
> I will find myself some docs to look into.
>
> Maybe this is not working, for I can not see our conversation on the website:
> "Public: Re: [meta-oe][PATCH V3] bc: Add ptest."
>
> I switched it to this:
> Public: Re: [meta-oe][oe-core][PATCH V3] bc: Add ptest.
>
> Not pretty sure weather it works or not.
>
> Nevermind, I would find some guidence in oe docs.
> 
>

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

[meta-oe][oe-core][PATCH V4] bc: Add ptest.

[Yan Xin Kuan]

From: Yan Xinkuan 

Add package test function for OSS 'bc',
using bc in the system to do calculation
jobs according to the .b files from the
source code file of 'bc'.

Test example as below:
..
.00673400673400673400
“PASS: bc/div.b”
9983640860328357366034714556282968349582
7909199408566065153345558783\
9427595471.89114392327665123852
“PASS: bc/exp.b”
length(b)= 1406
“PASS: bc/fact.b”
..

If bc runs the .b files and does not crash,
it would 'PASS', otherwise it would 'FAIL'.

Tested in qemux86-64, with kvm enabled, test
cost 12 secs, so it should be a fast test.

Thanks to Ross Burton and Alexander Kanavin
for the professional guidance.

Signed-off-by: Yan Xinkuan 
---
 meta/conf/distro/include/ptest-packagelists.inc | 1 +
 meta/recipes-extended/bc/bc/run-ptest   | 9 +
 meta/recipes-extended/bc/bc_1.07.1.bb   | 9 +++--
 3 files changed, 17 insertions(+), 2 deletions(-)
 create mode 100644 meta/recipes-extended/bc/bc/run-ptest

diff --git a/meta/conf/distro/include/ptest-packagelists.inc 
b/meta/conf/distro/include/ptest-packagelists.inc
index 56088e4e66..0a52a48ef1 100644
--- a/meta/conf/distro/include/ptest-packagelists.inc
+++ b/meta/conf/distro/include/ptest-packagelists.inc
@@ -69,6 +69,7 @@ PTESTS_FAST = "\
 slang-ptest \
 wayland-ptest \
 zlib-ptest \
+bc-ptest \
 "
 PTESTS_FAST:append:libc-glibc = " glibc-tests-ptest"
 PTESTS_PROBLEMS:remove:libc-glibc = "glibc-tests-ptest"
diff --git a/meta/recipes-extended/bc/bc/run-ptest 
b/meta/recipes-extended/bc/bc/run-ptest
new file mode 100644
index 00..da2156f8cd
--- /dev/null
+++ b/meta/recipes-extended/bc/bc/run-ptest
@@ -0,0 +1,9 @@
+#! /bin/sh
+
+for TEST in *.b; do
+   if bc -l $TEST 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172300): 
https://lists.openembedded.org/g/openembedded-core/message/172300
Mute This Topic: https://lists.openembedded.org/mt/94681755/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-oe][oe-core][PATCH V4] bc: Add ptest.

[Alexander Kanavin]

On Mon, 31 Oct 2022 at 10:55, Yan Xin Kuan  wrote:
> @@ -69,6 +69,7 @@ PTESTS_FAST = "\
>  slang-ptest \
>  wayland-ptest \
>  zlib-ptest \
> +bc-ptest \
>  "

This needs to be inserted in alphabetical order, otherwise looks good.

Alex

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

Re: [OE-Core][PATCH 2/2] cargo_common.bbclass: Support local github repos

[Alex Kiernan]

On Sun, Oct 30, 2022 at 6:35 PM Alexander Kanavin
 wrote:
>
> It would also help if there’s an actual recipe and component somewhere where 
> the problem exists now. The uuid-test does look like a made up example.
>

That's fair... basically it was demonstrating the problem I have with
a bunch of private repos, which I expect will crop up a lot in the
embedded rust world - if you're doing public dev, everything exists as
crates, in the private world you're consuming crates + internal stuff.
Not sure where to try and find a real world example as I'd expect
pretty much everyone will push to crates.io if their code is open -
searching around for a bit, I've failed to find any (though a couple
which have some dev only dependencies which come through git).

> Let’s merge the crate updater to core first, then we can think of handling 
> other ways to specify dependencies. ‘cargo bitbake’ is pretty broken and dead.
>

The crate updater feels like it's going to be directionally better -
testing it locally, it works for things which only consume things from
crates.io, but that's only one out of thirty or so components I have
to deal with.


> Alex
>
> On Sun 30. Oct 2022 at 19.12, Alex Kiernan  wrote:
>>
>> I was wondering about how to do that - my test case was
>> https://github.com/akiernan/uuid-test, but that's clearly not
>> adequate; the recipe there comes from `cargo bitbake` as `bitbake -c
>> update_crates` doesn't deal with git dependencies, or dig down into
>> transitive deps, which also needs solving.
>>
>> I'm not clear if something like this could be added as part of the
>> stuff that's in master-next for rust tests? Or if we need to build out
>> something new.
>>
>> On Sun, Oct 30, 2022 at 5:58 PM Alexander Kanavin
>>  wrote:
>> >
>> > There doesn’t seem to be a test case or an example for this. How can we 
>> > ensure the code is correct?
>> >
>> > Alex
>> >
>> > On Sun 30. Oct 2022 at 18.38, Alex Kiernan  wrote:
>> >>
>> >> Since disable network was added cargo configurations which reference git
>> >> repos fail as they attempt to fetch across the network as part of
>> >> do_compile, even if EXTRA_OECARGO_PATHS to add them as part of `paths`
>> >> is used, as this is documented as only working for packages which exist
>> >> in crates.io.
>> >>
>> >> Add parsing of the SRC_URIs for git repos and include `[patch]` sections
>> >> to redirect to the checked out source repos which the bitbake fetcher
>> >> has already populated.
>> >>
>> >> There are still cases which don't work - if you have multiple copies of
>> >> the same repo with different revisions, there's currently no way to
>> >> represent that and anything using a repo which has a virtual manifest
>> >> will fail to build (see https://github.com/rust-lang/cargo/issues/4934).
>> >>
>> >> Signed-off-by: Alex Kiernan 
>> >> ---
>> >>  meta/classes-recipe/cargo_common.bbclass | 30 
>> >>  1 file changed, 30 insertions(+)
>> >>
>> >> diff --git a/meta/classes-recipe/cargo_common.bbclass 
>> >> b/meta/classes-recipe/cargo_common.bbclass
>> >> index f503a001dd8e..63b13829084b 100644
>> >> --- a/meta/classes-recipe/cargo_common.bbclass
>> >> +++ b/meta/classes-recipe/cargo_common.bbclass
>> >> @@ -116,6 +116,36 @@ cargo_common_do_configure () {
>> >> EOF
>> >>  }
>> >>
>> >> +python cargo_common_do_patch_paths() {
>> >> +cargo_config = os.path.join(d.getVar("CARGO_HOME"), "config")
>> >> +if not os.path.exists(cargo_config):
>> >> +return
>> >> +
>> >> +src_uri = (d.getVar('SRC_URI') or "").split()
>> >> +if len(src_uri) == 0:
>> >> +return
>> >> +
>> >> +patches = dict()
>> >> +workdir = d.getVar('WORKDIR')
>> >> +fetcher = bb.fetch2.Fetch(src_uri, d)
>> >> +for url in fetcher.urls:
>> >> +ud = fetcher.ud[url]
>> >> +if ud.type == 'git':
>> >> +name = ud.parm.get('name')
>> >> +destsuffix = ud.parm.get('destsuffix')
>> >> +if name is not None and destsuffix is not None:
>> >> +repo = '%s://%s%s' % (ud.proto, ud.host, ud.path)
>> >> +path = '%s = { path = "%s" }' % (name, 
>> >> os.path.join(workdir, destsuffix))
>> >> +patches.setdefault(repo, []).append(path)
>> >> +
>> >> +with open(cargo_config, "a+") as config:
>> >> +for k, v in patches.items():
>> >> +print('\n[patch."%s"]' % k, file=config)
>> >> +for name in v:
>> >> +print(name, file=config)
>> >> +}
>> >> +do_configure[postfuncs] += "cargo_common_do_patch_paths"
>> >> +
>> >>  oe_cargo_fix_env () {
>> >> export CC="${RUST_TARGET_CC}"
>> >> export CXX="${RUST_TARGET_CXX}"
>> >> --
>> >> 2.35.1
>> >>
>> >>
>> >> 
>> >>
>>
>>
>> --
>> Alex Kiernan



--
Alex Kiernan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172302): 
https://lists.openembedded.org/g/openembedded-core/message/172302
Mute This Topic

[OE-core] [PATCH 01/13] cargo-update-recipe-crates.bbclass: add a class to generate SRC_URI crate lists from Cargo.lock

[Alexander Kanavin]

For better or worse, more and more rust components are appearing that do
not include their dependencies in tarballs (or git trees), and rely on cargo
to fetch them. On the other hand, bitbake does not use cargo (and quite possible
won't ever be able to), and relies on having each item explicitly listed in 
SRC_URI
with a crate:// prefix. This however creates a problem of both making such 
lists in
the first place and updating them when a recipe is updated to a newer version.

So this class can be used to perform such updates by implementing a task that 
does it;
the next commit shows the outcome for python3-bcrypt (which has been tested to 
work
and produce a successful build).

Note: the python script relies on tomllib library, which appears in Python 3.11 
and
does not exist in earlier versions - I've tested this by first updating python 
to 3.11-rc2
in oe-core.

Signed-off-by: Alexander Kanavin 
---
 .../cargo-update-recipe-crates.bbclass| 41 +++
 1 file changed, 41 insertions(+)
 create mode 100644 meta/classes-recipe/cargo-update-recipe-crates.bbclass

diff --git a/meta/classes-recipe/cargo-update-recipe-crates.bbclass 
b/meta/classes-recipe/cargo-update-recipe-crates.bbclass
new file mode 100644
index 00..f90938c734
--- /dev/null
+++ b/meta/classes-recipe/cargo-update-recipe-crates.bbclass
@@ -0,0 +1,41 @@
+#
+# Copyright OpenEmbedded Contributors
+#
+# SPDX-License-Identifier: MIT
+#
+
+##
+## Purpose:
+## This class is used to update the list of crates in SRC_URI
+## by reading Cargo.lock in the source tree.
+##
+## See meta/recipes-devtools/python/python3-bcrypt_*.bb for an example
+##
+## To perform the update: bitbake -c update_crates recipe-name
+
+addtask do_update_crates after do_patch
+do_update_crates[depends] = "python3-native:do_populate_sysroot"
+
+do_update_crates() {
+nativepython3 - <
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172303): 
https://lists.openembedded.org/g/openembedded-core/message/172303
Mute This Topic: https://lists.openembedded.org/mt/94683148/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 02/13] python3-bcrypt: convert to use cargo-update-recipe-crates class.

[Alexander Kanavin]

The component has been reimplemented in rust, and comes
with a large list of dependencies in Cargo.toml/Cargo.lock.

Rather than list them by hand, use a file generated with
cargo-update-recipe-crates class.

Signed-off-by: Alexander Kanavin 
---
 .../python/python3-bcrypt-crates.inc  | 53 ++
 .../python/python3-bcrypt_4.0.0.bb| 55 ++-
 2 files changed, 57 insertions(+), 51 deletions(-)
 create mode 100644 meta/recipes-devtools/python/python3-bcrypt-crates.inc

diff --git a/meta/recipes-devtools/python/python3-bcrypt-crates.inc 
b/meta/recipes-devtools/python/python3-bcrypt-crates.inc
new file mode 100644
index 00..78c5d5aa22
--- /dev/null
+++ b/meta/recipes-devtools/python/python3-bcrypt-crates.inc
@@ -0,0 +1,53 @@
+# Autogenerated with 'bitbake -c update_crates python3-bcrypt'
+
+SRC_URI += " \ 
+crate://crates.io/autocfg/1.1.0 \ 
+crate://crates.io/base64/0.13.0 \ 
+crate://crates.io/bcrypt/0.13.0 \ 
+crate://crates.io/bcrypt-pbkdf/0.8.1 \ 
+crate://crates.io/bitflags/1.3.2 \ 
+crate://crates.io/block-buffer/0.10.2 \ 
+crate://crates.io/blowfish/0.9.1 \ 
+crate://crates.io/byteorder/1.4.3 \ 
+crate://crates.io/cfg-if/1.0.0 \ 
+crate://crates.io/cipher/0.4.3 \ 
+crate://crates.io/cpufeatures/0.2.4 \ 
+crate://crates.io/crypto-common/0.1.6 \ 
+crate://crates.io/digest/0.10.3 \ 
+crate://crates.io/generic-array/0.14.6 \ 
+crate://crates.io/getrandom/0.2.7 \ 
+crate://crates.io/indoc/0.3.6 \ 
+crate://crates.io/indoc-impl/0.3.6 \ 
+crate://crates.io/inout/0.1.3 \ 
+crate://crates.io/instant/0.1.12 \ 
+crate://crates.io/libc/0.2.132 \ 
+crate://crates.io/lock_api/0.4.7 \ 
+crate://crates.io/once_cell/1.13.1 \ 
+crate://crates.io/parking_lot/0.11.2 \ 
+crate://crates.io/parking_lot_core/0.8.5 \ 
+crate://crates.io/paste/0.1.18 \ 
+crate://crates.io/paste-impl/0.1.18 \ 
+crate://crates.io/pbkdf2/0.10.1 \ 
+crate://crates.io/proc-macro-hack/0.5.19 \ 
+crate://crates.io/proc-macro2/1.0.43 \ 
+crate://crates.io/pyo3/0.15.2 \ 
+crate://crates.io/pyo3-build-config/0.15.2 \ 
+crate://crates.io/pyo3-macros/0.15.2 \ 
+crate://crates.io/pyo3-macros-backend/0.15.2 \ 
+crate://crates.io/quote/1.0.21 \ 
+crate://crates.io/redox_syscall/0.2.16 \ 
+crate://crates.io/scopeguard/1.1.0 \ 
+crate://crates.io/sha2/0.10.2 \ 
+crate://crates.io/smallvec/1.9.0 \ 
+crate://crates.io/subtle/2.4.1 \ 
+crate://crates.io/syn/1.0.99 \ 
+crate://crates.io/typenum/1.15.0 \ 
+crate://crates.io/unicode-ident/1.0.3 \ 
+crate://crates.io/unindent/0.1.10 \ 
+crate://crates.io/version_check/0.9.4 \ 
+crate://crates.io/wasi/0.11.0+wasi-snapshot-preview1 \ 
+crate://crates.io/winapi/0.3.9 \ 
+crate://crates.io/winapi-i686-pc-windows-gnu/0.4.0 \ 
+crate://crates.io/winapi-x86_64-pc-windows-gnu/0.4.0 \ 
+crate://crates.io/zeroize/1.5.7 \ 
+"
diff --git a/meta/recipes-devtools/python/python3-bcrypt_4.0.0.bb 
b/meta/recipes-devtools/python/python3-bcrypt_4.0.0.bb
index ac795ca8ab..857b38df2c 100644
--- a/meta/recipes-devtools/python/python3-bcrypt_4.0.0.bb
+++ b/meta/recipes-devtools/python/python3-bcrypt_4.0.0.bb
@@ -7,61 +7,14 @@ DEPENDS += "${PYTHON_PN}-cffi-native"
 
 SRC_URI[sha256sum] = 
"c59c170fc9225faad04dde1ba61d85b413946e8ce2e5f5f5ff30dfd67283f319"
 
-inherit pypi python_setuptools3_rust ptest
+inherit pypi python_setuptools3_rust ptest cargo-update-recipe-crates
 
 SRC_URI += " \
-crate://crates.io/autocfg/1.1.0 \
-crate://crates.io/base64/0.13.0 \
-crate://crates.io/bcrypt-pbkdf/0.8.1 \
-crate://crates.io/bcrypt/0.13.0 \
-crate://crates.io/bitflags/1.3.2 \
-crate://crates.io/block-buffer/0.10.2 \
-crate://crates.io/blowfish/0.9.1 \
-crate://crates.io/byteorder/1.4.3 \
-crate://crates.io/cfg-if/1.0.0 \
-crate://crates.io/cipher/0.4.3 \
-crate://crates.io/cpufeatures/0.2.4 \
-crate://crates.io/crypto-common/0.1.6 \
-crate://crates.io/digest/0.10.3 \
-crate://crates.io/generic-array/0.14.6 \
-crate://crates.io/getrandom/0.2.7 \
-crate://crates.io/indoc-impl/0.3.6 \
-crate://crates.io/indoc/0.3.6 \
-crate://crates.io/inout/0.1.3 \
-crate://crates.io/instant/0.1.12 \
-crate://crates.io/libc/0.2.132 \
-crate://crates.io/lock_api/0.4.7 \
-crate://crates.io/once_cell/1.13.1 \
-crate://crates.io/parking_lot/0.11.2 \
-crate://crates.io/parking_lot_core/0.8.5 \
-crate://crates.io/paste-impl/0.1.18 \
-crate://crates.io/paste/0.1.18 \
-crate://crates.io/pbkdf2/0.10.1 \
-crate://crates.io/proc-macro-hack/0.5.19 \
-crate://crates.io/proc-macro2/1.0.43 \
-crate://crates.io/pyo3-build-config/0.

[OE-core] [PATCH 03/13] python3-cryptography: convert to cargo-update-recipe-crates class

[Alexander Kanavin]

This allows semi-automated updates to the list of crates, which
is far too awkward to maintain by hand, particularly on version updates.

Signed-off-by: Alexander Kanavin 
---
 .../python/python3-cryptography-crates.inc| 58 +++
 .../python/python3-cryptography_38.0.1.bb | 58 +--
 2 files changed, 61 insertions(+), 55 deletions(-)
 create mode 100644 meta/recipes-devtools/python/python3-cryptography-crates.inc

diff --git a/meta/recipes-devtools/python/python3-cryptography-crates.inc 
b/meta/recipes-devtools/python/python3-cryptography-crates.inc
new file mode 100644
index 00..9339a15091
--- /dev/null
+++ b/meta/recipes-devtools/python/python3-cryptography-crates.inc
@@ -0,0 +1,58 @@
+# Autogenerated with 'bitbake -c update_crates python3-cryptography'
+
+SRC_URI += " \ 
+crate://crates.io/Inflector/0.11.4 \ 
+crate://crates.io/aliasable/0.1.3 \ 
+crate://crates.io/android_system_properties/0.1.5 \ 
+crate://crates.io/asn1/0.12.2 \ 
+crate://crates.io/asn1_derive/0.12.2 \ 
+crate://crates.io/autocfg/1.1.0 \ 
+crate://crates.io/base64/0.13.0 \ 
+crate://crates.io/bitflags/1.3.2 \ 
+crate://crates.io/bumpalo/3.10.0 \ 
+crate://crates.io/cfg-if/1.0.0 \ 
+crate://crates.io/chrono/0.4.22 \ 
+crate://crates.io/core-foundation-sys/0.8.3 \ 
+crate://crates.io/iana-time-zone/0.1.47 \ 
+crate://crates.io/indoc/0.3.6 \ 
+crate://crates.io/indoc-impl/0.3.6 \ 
+crate://crates.io/instant/0.1.12 \ 
+crate://crates.io/js-sys/0.3.59 \ 
+crate://crates.io/libc/0.2.132 \ 
+crate://crates.io/lock_api/0.4.8 \ 
+crate://crates.io/log/0.4.17 \ 
+crate://crates.io/num-integer/0.1.45 \ 
+crate://crates.io/num-traits/0.2.15 \ 
+crate://crates.io/once_cell/1.14.0 \ 
+crate://crates.io/ouroboros/0.15.4 \ 
+crate://crates.io/ouroboros_macro/0.15.4 \ 
+crate://crates.io/parking_lot/0.11.2 \ 
+crate://crates.io/parking_lot_core/0.8.5 \ 
+crate://crates.io/paste/0.1.18 \ 
+crate://crates.io/paste-impl/0.1.18 \ 
+crate://crates.io/pem/1.1.0 \ 
+crate://crates.io/proc-macro-error/1.0.4 \ 
+crate://crates.io/proc-macro-error-attr/1.0.4 \ 
+crate://crates.io/proc-macro-hack/0.5.19 \ 
+crate://crates.io/proc-macro2/1.0.43 \ 
+crate://crates.io/pyo3/0.15.2 \ 
+crate://crates.io/pyo3-build-config/0.15.2 \ 
+crate://crates.io/pyo3-macros/0.15.2 \ 
+crate://crates.io/pyo3-macros-backend/0.15.2 \ 
+crate://crates.io/quote/1.0.21 \ 
+crate://crates.io/redox_syscall/0.2.16 \ 
+crate://crates.io/scopeguard/1.1.0 \ 
+crate://crates.io/smallvec/1.9.0 \ 
+crate://crates.io/syn/1.0.99 \ 
+crate://crates.io/unicode-ident/1.0.3 \ 
+crate://crates.io/unindent/0.1.10 \ 
+crate://crates.io/version_check/0.9.4 \ 
+crate://crates.io/wasm-bindgen/0.2.82 \ 
+crate://crates.io/wasm-bindgen-backend/0.2.82 \ 
+crate://crates.io/wasm-bindgen-macro/0.2.82 \ 
+crate://crates.io/wasm-bindgen-macro-support/0.2.82 \ 
+crate://crates.io/wasm-bindgen-shared/0.2.82 \ 
+crate://crates.io/winapi/0.3.9 \ 
+crate://crates.io/winapi-i686-pc-windows-gnu/0.4.0 \ 
+crate://crates.io/winapi-x86_64-pc-windows-gnu/0.4.0 \ 
+"
diff --git a/meta/recipes-devtools/python/python3-cryptography_38.0.1.bb 
b/meta/recipes-devtools/python/python3-cryptography_38.0.1.bb
index 905293a43e..68679b745a 100644
--- a/meta/recipes-devtools/python/python3-cryptography_38.0.1.bb
+++ b/meta/recipes-devtools/python/python3-cryptography_38.0.1.bb
@@ -16,63 +16,11 @@ SRC_URI += "\
 file://0001-pyproject.toml-remove-benchmark-disable-option.patch \
 file://check-memfree.py \
 file://run-ptest \
-crate://crates.io/Inflector/0.11.4 \
-crate://crates.io/aliasable/0.1.3 \
-crate://crates.io/android_system_properties/0.1.5 \
-crate://crates.io/asn1/0.12.2 \
-crate://crates.io/asn1_derive/0.12.2 \
-crate://crates.io/autocfg/1.1.0 \
-crate://crates.io/base64/0.13.0 \
-crate://crates.io/bitflags/1.3.2 \
-crate://crates.io/bumpalo/3.10.0 \
-crate://crates.io/cfg-if/1.0.0 \
-crate://crates.io/chrono/0.4.22 \
-crate://crates.io/core-foundation-sys/0.8.3 \
-crate://crates.io/iana-time-zone/0.1.47 \
-crate://crates.io/indoc-impl/0.3.6 \
-crate://crates.io/indoc/0.3.6 \
-crate://crates.io/instant/0.1.12 \
-crate://crates.io/js-sys/0.3.59 \
-crate://crates.io/libc/0.2.132 \
-crate://crates.io/lock_api/0.4.8 \
-crate://crates.io/log/0.4.17 \
-crate://crates.io/num-integer/0.1.45 \
-crate://crates.io/num-traits/0.2.15 \
-crate://crates.io/once_cell/1.14.0 \
-crate://crates.io/ouroboros/0.15.4 \
-crate://crates.io/ouroboros_macro/0.15.4 \
-crat

[OE-core] [PATCH 04/13] groff: submit patches upstream

[Alexander Kanavin]

Signed-off-by: Alexander Kanavin 
---
 .../groff/files/0001-Make-manpages-mulitlib-identical.patch | 2 +-
 .../groff/files/0001-replace-perl-w-with-use-warnings.patch | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git 
a/meta/recipes-extended/groff/files/0001-Make-manpages-mulitlib-identical.patch 
b/meta/recipes-extended/groff/files/0001-Make-manpages-mulitlib-identical.patch
index 9105da6457..c3cfc7cea8 100644
--- 
a/meta/recipes-extended/groff/files/0001-Make-manpages-mulitlib-identical.patch
+++ 
b/meta/recipes-extended/groff/files/0001-Make-manpages-mulitlib-identical.patch
@@ -3,7 +3,7 @@ From: Jeremy Puhlman 
 Date: Sat, 7 Mar 2020 00:59:13 +
 Subject: [PATCH] Make manpages mulitlib identical
 
-Upstream-Status: Pending
+Upstream-Status: Submitted [by email to g.branden.robin...@gmail.com]
 Signed-off-by: Jeremy Puhlman 
 ---
  Makefile.am | 2 +-
diff --git 
a/meta/recipes-extended/groff/files/0001-replace-perl-w-with-use-warnings.patch 
b/meta/recipes-extended/groff/files/0001-replace-perl-w-with-use-warnings.patch
index eda6a40f51..b028fa20aa 100644
--- 
a/meta/recipes-extended/groff/files/0001-replace-perl-w-with-use-warnings.patch
+++ 
b/meta/recipes-extended/groff/files/0001-replace-perl-w-with-use-warnings.patch
@@ -15,7 +15,7 @@ doesn't work:
 
 So replace "perl -w" with "use warnings" to make it work.
 
-Upstream-Status: Pending
+Upstream-Status: Submitted [by email to g.branden.robin...@gmail.com]
 
 Signed-off-by: Robert Yang 
 
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172306): 
https://lists.openembedded.org/g/openembedded-core/message/172306
Mute This Topic: https://lists.openembedded.org/mt/94683152/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 05/13] tcl: correct patch status

[Alexander Kanavin]

Signed-off-by: Alexander Kanavin 
---
 .../recipes-devtools/tcltk/tcl/fix_non_native_build_issue.patch | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/tcltk/tcl/fix_non_native_build_issue.patch 
b/meta/recipes-devtools/tcltk/tcl/fix_non_native_build_issue.patch
index 44b2ce0a30..5a10c93a31 100644
--- a/meta/recipes-devtools/tcltk/tcl/fix_non_native_build_issue.patch
+++ b/meta/recipes-devtools/tcltk/tcl/fix_non_native_build_issue.patch
@@ -1,4 +1,4 @@
-Upstream-Status: Pending
+Upstream-Status: Inappropriate [upstream does not support installed tests]
 
 Index: unix/Makefile.in
 ===
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172307): 
https://lists.openembedded.org/g/openembedded-core/message/172307
Mute This Topic: https://lists.openembedded.org/mt/94683153/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 06/13] tcl: correct upstream version check

[Alexander Kanavin]

Sourceforge does not report the latest version reliably.

Signed-off-by: Alexander Kanavin 
---
 meta/recipes-devtools/tcltk/tcl_8.6.11.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-devtools/tcltk/tcl_8.6.11.bb 
b/meta/recipes-devtools/tcltk/tcl_8.6.11.bb
index 9f6b003ffb..f8b2a69b9f 100644
--- a/meta/recipes-devtools/tcltk/tcl_8.6.11.bb
+++ b/meta/recipes-devtools/tcltk/tcl_8.6.11.bb
@@ -33,6 +33,7 @@ SRC_URI:class-native = "${BASE_SRC_URI}"
 # https://core.tcl-lang.org/tcl/info/7079e4f91601e9c7
 CVE_CHECK_IGNORE += "CVE-2021-35331"
 
+UPSTREAM_CHECK_URI = "https://www.tcl.tk/software/tcltk/download.html";
 UPSTREAM_CHECK_REGEX = "tcl(?P\d+(\.\d+)+)-src"
 
 S = "${WORKDIR}/${BPN}${PV}"
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172308): 
https://lists.openembedded.org/g/openembedded-core/message/172308
Mute This Topic: https://lists.openembedded.org/mt/94683154/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 07/13] lttng-tools: submit determinism.patch upstream

[Alexander Kanavin]

Signed-off-by: Alexander Kanavin 
---
 meta/recipes-kernel/lttng/lttng-tools/determinism.patch | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/lttng/lttng-tools/determinism.patch 
b/meta/recipes-kernel/lttng/lttng-tools/determinism.patch
index b2ab880bd6..0a897a8e13 100644
--- a/meta/recipes-kernel/lttng/lttng-tools/determinism.patch
+++ b/meta/recipes-kernel/lttng/lttng-tools/determinism.patch
@@ -13,7 +13,7 @@ to me whether the tests need that or not.
 
 Fixes reproducibility issues for lttng-tools.
 
-Upstream-Status: Pending [needs discussion with upstream about the correct 
solution]
+Upstream-Status: Submitted [https://bugs.lttng.org/issues/1361 - needs 
discussion with upstream about the correct solution]
 RP 2021/3/1
 
 Index: lttng-tools-2.12.2/tests/regression/ust/ust-dl/Makefile.am
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172309): 
https://lists.openembedded.org/g/openembedded-core/message/172309
Mute This Topic: https://lists.openembedded.org/mt/94683155/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 08/13] cmake: drop qt4 patches

[Alexander Kanavin]

Qt4 has been dead for a very long time now.

Signed-off-by: Alexander Kanavin 
---
 meta/recipes-devtools/cmake/cmake.inc |  2 -
 ...t-OpenEmbedded-Qt4-tool-binary-names.patch | 56 -
 ...-if-system-Qt-installation-is-broken.patch | 79 ---
 3 files changed, 137 deletions(-)
 delete mode 100644 
meta/recipes-devtools/cmake/cmake/0003-cmake-support-OpenEmbedded-Qt4-tool-binary-names.patch
 delete mode 100644 
meta/recipes-devtools/cmake/cmake/0004-Fail-silently-if-system-Qt-installation-is-broken.patch

diff --git a/meta/recipes-devtools/cmake/cmake.inc 
b/meta/recipes-devtools/cmake/cmake.inc
index 1ede8eee61..7561e851c6 100644
--- a/meta/recipes-devtools/cmake/cmake.inc
+++ b/meta/recipes-devtools/cmake/cmake.inc
@@ -17,8 +17,6 @@ LIC_FILES_CHKSUM = 
"file://Copyright.txt;md5=45025187a129339459b6f1a24f7fac6e \
 CMAKE_MAJOR_VERSION = "${@'.'.join(d.getVar('PV').split('.')[0:2])}"
 
 SRC_URI = "https://cmake.org/files/v${CMAKE_MAJOR_VERSION}/cmake-${PV}.tar.gz \
-   file://0003-cmake-support-OpenEmbedded-Qt4-tool-binary-names.patch \
-   file://0004-Fail-silently-if-system-Qt-installation-is-broken.patch 
\
 "
 
 SRC_URI[sha256sum] = 
"0d9020f06f3ddf17fb537dc228e1a56c927ee506b486f55fe2dc19f69bf0c8db"
diff --git 
a/meta/recipes-devtools/cmake/cmake/0003-cmake-support-OpenEmbedded-Qt4-tool-binary-names.patch
 
b/meta/recipes-devtools/cmake/cmake/0003-cmake-support-OpenEmbedded-Qt4-tool-binary-names.patch
deleted file mode 100644
index 575a5cb7fb..00
--- 
a/meta/recipes-devtools/cmake/cmake/0003-cmake-support-OpenEmbedded-Qt4-tool-binary-names.patch
+++ /dev/null
@@ -1,56 +0,0 @@
-From 2d02ac91d5a5d72eaddba4894eaa6db3ed8fee62 Mon Sep 17 00:00:00 2001
-From: Otavio Salvador 
-Date: Thu, 12 May 2011 15:36:03 +
-Subject: [PATCH] cmake: support OpenEmbedded Qt4 tool binary names
-
-The FindQt4 module looks for Qt4 binaries to be able to gather the
-paths used for compilation and also to be using during other processes
-(translation update, translation binary generating and like) however
-OpenEmbedded has renamed those to allow old QMake to be used in
-parallel with the current one. This patch adds support for the
-OpenEmbedded specific binary names.
-
-Upstream-Status: Inappropriate [embedded specific]
-
-Signed-off-by: Otavio Salvador 
-
-The patch was slightly adapted in order to match cmake 3.2.2:
-Instead of find_program, _find_qt4_program is now used.
-
-Signed-off-by: Moritz Blume 
-Signed-off-by: Otavio Salvador 
-

- Modules/FindQt4.cmake | 10 +-
- 1 file changed, 5 insertions(+), 5 deletions(-)
-
-diff --git a/Modules/FindQt4.cmake b/Modules/FindQt4.cmake
-index 3993968..b2a8585 100644
 a/Modules/FindQt4.cmake
-+++ b/Modules/FindQt4.cmake
-@@ -518,7 +518,7 @@ endfunction()
- 
- set(QT4_INSTALLED_VERSION_TOO_OLD FALSE)
- 
--set(_QT4_QMAKE_NAMES qmake qmake4 qmake-qt4 qmake-mac)
-+set(_QT4_QMAKE_NAMES qmake qmake2 qmake4 qmake-qt4 qmake-mac)
- _qt4_find_qmake("${_QT4_QMAKE_NAMES}" QT_QMAKE_EXECUTABLE QTVERSION)
- 
- if (QT_QMAKE_EXECUTABLE AND
-@@ -1136,12 +1136,12 @@ if (QT_QMAKE_EXECUTABLE AND
-   _find_qt4_program(QT_MOC_EXECUTABLE Qt4::moc moc-qt4 moc4 moc)
-   _find_qt4_program(QT_UIC_EXECUTABLE Qt4::uic uic-qt4 uic4 uic)
-   _find_qt4_program(QT_UIC3_EXECUTABLE Qt4::uic3 uic3)
--  _find_qt4_program(QT_RCC_EXECUTABLE Qt4::rcc rcc)
--  _find_qt4_program(QT_DBUSCPP2XML_EXECUTABLE Qt4::qdbuscpp2xml qdbuscpp2xml)
--  _find_qt4_program(QT_DBUSXML2CPP_EXECUTABLE Qt4::qdbusxml2cpp qdbusxml2cpp)
-+  _find_qt4_program(QT_RCC_EXECUTABLE Qt4::rcc rcc4 rcc)
-+  _find_qt4_program(QT_DBUSCPP2XML_EXECUTABLE Qt4::qdbuscpp2xml qdbuscpp2xml4 
qdbuscpp2xml)
-+  _find_qt4_program(QT_DBUSXML2CPP_EXECUTABLE Qt4::qdbusxml2cpp qdbusxml2cpp4 
qdbusxml2cpp)
-   _find_qt4_program(QT_LUPDATE_EXECUTABLE Qt4::lupdate lupdate-qt4 lupdate4 
lupdate)
-   _find_qt4_program(QT_LRELEASE_EXECUTABLE Qt4::lrelease lrelease-qt4 
lrelease4 lrelease)
--  _find_qt4_program(QT_QCOLLECTIONGENERATOR_EXECUTABLE 
Qt4::qcollectiongenerator qcollectiongenerator-qt4 qcollectiongenerator)
-+  _find_qt4_program(QT_QCOLLECTIONGENERATOR_EXECUTABLE 
Qt4::qcollectiongenerator qcollectiongenerator-qt4 qcollectiongenerator 
qcollectiongenerator4)
-   _find_qt4_program(QT_DESIGNER_EXECUTABLE Qt4::designer designer-qt4 
designer4 designer)
-   _find_qt4_program(QT_LINGUIST_EXECUTABLE Qt4::linguist linguist-qt4 
linguist4 linguist)
- 
diff --git 
a/meta/recipes-devtools/cmake/cmake/0004-Fail-silently-if-system-Qt-installation-is-broken.patch
 
b/meta/recipes-devtools/cmake/cmake/0004-Fail-silently-if-system-Qt-installation-is-broken.patch
deleted file mode 100644
index 1b196db81a..00
--- 
a/meta/recipes-devtools/cmake/cmake/0004-Fail-silently-if-system-Qt-installation-is-broken.patch
+++ /dev/null
@@ -1,79 +0,0 @@
-From 60864efbe52cc12018efaafbc4e4c3c8b4af2b65 Mon Sep 17 00:00:00 2001
-From: Otavio Salvador 
-Date: Thu, 5 Jul 2018 10:26:48 -0300
-Subject: [PATCH] Fail silently i

[OE-core] [PATCH 09/13] kea: submit patch upstream

[Alexander Kanavin]

Signed-off-by: Alexander Kanavin 
---
 meta/recipes-connectivity/kea/files/fix-multilib-conflict.patch | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-connectivity/kea/files/fix-multilib-conflict.patch 
b/meta/recipes-connectivity/kea/files/fix-multilib-conflict.patch
index 78f475a495..451b409c88 100644
--- a/meta/recipes-connectivity/kea/files/fix-multilib-conflict.patch
+++ b/meta/recipes-connectivity/kea/files/fix-multilib-conflict.patch
@@ -12,7 +12,7 @@ Subject: [PATCH] There are conflict of config files between 
kea and lib32-kea:
 Because they are all commented out, replace the expanded libdir path with
 '$libdir' in the config files to avoid conflict.
 
-Upstream-Status: Pending
+Upstream-Status: Submitted 
[https://gitlab.isc.org/isc-projects/kea/-/issues/2602]
 Signed-off-by: Kai Kang 
 
 ---
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172311): 
https://lists.openembedded.org/g/openembedded-core/message/172311
Mute This Topic: https://lists.openembedded.org/mt/94683158/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 10/13] argp-standalone: replace with a maintained fork

[Alexander Kanavin]

Remove two patches as issues fixed upstream,
submit the third one.

License-Update: argp.h is an import from glibc and
has been refreshed to the latest version. It's still
lgpl 2.1.

Signed-off-by: Alexander Kanavin 
---
 ...dalone_1.3.bb => argp-standalone_1.4.1.bb} | 12 ++-
 .../files/0001-throw-in-funcdef.patch | 84 ---
 .../argp-standalone/files/0002-isprint.patch  | 51 ---
 .../files/out_of_tree_build.patch |  2 +-
 4 files changed, 6 insertions(+), 143 deletions(-)
 rename meta/recipes-support/argp-standalone/{argp-standalone_1.3.bb => 
argp-standalone_1.4.1.bb} (59%)
 delete mode 100644 
meta/recipes-support/argp-standalone/files/0001-throw-in-funcdef.patch
 delete mode 100644 
meta/recipes-support/argp-standalone/files/0002-isprint.patch

diff --git a/meta/recipes-support/argp-standalone/argp-standalone_1.3.bb 
b/meta/recipes-support/argp-standalone/argp-standalone_1.4.1.bb
similarity index 59%
rename from meta/recipes-support/argp-standalone/argp-standalone_1.3.bb
rename to meta/recipes-support/argp-standalone/argp-standalone_1.4.1.bb
index 8d8122612a..00b6036502 100644
--- a/meta/recipes-support/argp-standalone/argp-standalone_1.3.bb
+++ b/meta/recipes-support/argp-standalone/argp-standalone_1.4.1.bb
@@ -3,18 +3,16 @@
 
 SUMMARY = "Glibc hierarchical argument parsing standalone library"
 DESCRIPTION = "Standalone version of arguments parsing functions from GLIBC"
-HOMEPAGE = "http://www.lysator.liu.se/~nisse/misc/";
+HOMEPAGE = "https://github.com/ericonr/argp-standalone";
 LICENSE = "LGPL-2.1-only"
-LIC_FILES_CHKSUM = 
"file://argp.h;beginline=1;endline=20;md5=008b7e53dea6f9e1d9fdef0d9cf3184a"
+LIC_FILES_CHKSUM = 
"file://argp.h;beginline=1;endline=20;md5=464f2cfb1c35a5123f9e309d7afd79f8"
 SECTION = "libs"
 
-SRC_URI = "http://www.lysator.liu.se/~nisse/misc/argp-standalone-${PV}.tar.gz \
-   file://0001-throw-in-funcdef.patch \
-   file://0002-isprint.patch \
+SRC_URI = 
"git://github.com/ericonr/argp-standalone;branch=master;protocol=https \
file://out_of_tree_build.patch \
   "
-SRC_URI[md5sum] = "720704bac078d067111b32444e24ba69"
-SRC_URI[sha256sum] = 
"dec79694da1319acd2238ce95df57f3680fea2482096e483323fddf3d818d8be"
+SRCREV = "e5fe9ad9e83e6765cf8fa787f903d4c6792338b5"
+S = "${WORKDIR}/git"
 
 inherit autotools
 
diff --git 
a/meta/recipes-support/argp-standalone/files/0001-throw-in-funcdef.patch 
b/meta/recipes-support/argp-standalone/files/0001-throw-in-funcdef.patch
deleted file mode 100644
index a6e2759c5d..00
--- a/meta/recipes-support/argp-standalone/files/0001-throw-in-funcdef.patch
+++ /dev/null
@@ -1,84 +0,0 @@
-# --- T2-COPYRIGHT-NOTE-BEGIN ---
-# This copyright note is auto-generated by ./scripts/Create-CopyPatch.
-# 
-# T2 SDE: package/.../rng-tools/throw-in-funcdef.patch.argp-standalone
-# Copyright (C) 2006 The T2 SDE Project
-# 
-# More information can be found in the files COPYING and README.
-# 
-# This patch file is dual-licensed. It is available under the license the
-# patched project is licensed under, as long as it is an OpenSource license
-# as defined at http://www.opensource.org/ (e.g. BSD, X11) or under the terms
-# of the GNU General Public License as published by the Free Software
-# Foundation; either version 2 of the License, or (at your option) any later
-# version.
-# --- T2-COPYRIGHT-NOTE-END ---
-
-
-No __THROW in function implementation.
-   --jsaw
-
-Taken from buildroot
-
-Upstream-Status: Pending
-Signed-off-by: Khem Raj 
-
 argp-standalone-1.4-test2/argp.h.orig  2006-01-06 02:29:59.0 
+0100
-+++ argp-standalone-1.4-test2/argp.h   2006-01-06 02:41:10.0 +0100
-@@ -560,17 +560,17 @@
- # endif
- 
- # ifndef ARGP_EI
--#  define ARGP_EI extern __inline__
-+#  define ARGP_EI extern inline
- # endif
- 
- ARGP_EI void
--__argp_usage (__const struct argp_state *__state) __THROW
-+__argp_usage (__const struct argp_state *__state)
- {
-   __argp_state_help (__state, stderr, ARGP_HELP_STD_USAGE);
- }
- 
- ARGP_EI int
--__option_is_short (__const struct argp_option *__opt) __THROW
-+__option_is_short (__const struct argp_option *__opt)
- {
-   if (__opt->flags & OPTION_DOC)
- return 0;
-@@ -582,7 +582,7 @@
- }
- 
- ARGP_EI int
--__option_is_end (__const struct argp_option *__opt) __THROW
-+__option_is_end (__const struct argp_option *__opt)
- {
-   return !__opt->key && !__opt->name && !__opt->doc && !__opt->group;
- }
 argp-standalone-1.4-test2/argp-parse.c.orig2006-01-06 
02:47:48.0 +0100
-+++ argp-standalone-1.4-test2/argp-parse.c 2006-01-06 02:48:16.0 
+0100
-@@ -1290,13 +1290,13 @@
- /* Defined here, in case a user is not inlining the definitions in
-  * argp.h */
- void
--__argp_usage (__const struct argp_state *__state) __THROW
-+__argp_usage (__const struct argp_state *__state)
- {
-   __argp_state_help (__state, stderr, ARGP_HELP_STD_USAGE);
- }
- 
- int
--__option_is_short (__const struct argp_option *__opt)

[OE-core] [PATCH 11/13] ovmf: correct patches status

[Alexander Kanavin]

Signed-off-by: Alexander Kanavin 
---
 .../ovmf/0001-ovmf-update-path-to-native-BaseTools.patch   | 2 +-
 ...seTools-makefile-adjust-to-build-in-under-bitbake.patch | 7 ++-
 2 files changed, 7 insertions(+), 2 deletions(-)

diff --git 
a/meta/recipes-core/ovmf/ovmf/0001-ovmf-update-path-to-native-BaseTools.patch 
b/meta/recipes-core/ovmf/ovmf/0001-ovmf-update-path-to-native-BaseTools.patch
index 89d9ffab5e..0c3df4fc44 100644
--- 
a/meta/recipes-core/ovmf/ovmf/0001-ovmf-update-path-to-native-BaseTools.patch
+++ 
b/meta/recipes-core/ovmf/ovmf/0001-ovmf-update-path-to-native-BaseTools.patch
@@ -10,7 +10,7 @@ tools. The BBAKE_EDK_TOOLS_PATH string is used as a pattern 
to be replaced
 with the appropriate location before building.
 
 Signed-off-by: Ricardo Neri 
-Upstream-Status: Pending
+Upstream-Status: Inappropriate [oe-core cross compile specific]
 ---
  OvmfPkg/build.sh | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
diff --git 
a/meta/recipes-core/ovmf/ovmf/0002-BaseTools-makefile-adjust-to-build-in-under-bitbake.patch
 
b/meta/recipes-core/ovmf/ovmf/0002-BaseTools-makefile-adjust-to-build-in-under-bitbake.patch
index f6141c8af5..2293d7e938 100644
--- 
a/meta/recipes-core/ovmf/ovmf/0002-BaseTools-makefile-adjust-to-build-in-under-bitbake.patch
+++ 
b/meta/recipes-core/ovmf/ovmf/0002-BaseTools-makefile-adjust-to-build-in-under-bitbake.patch
@@ -6,8 +6,13 @@ Subject: [PATCH 2/6] BaseTools: makefile: adjust to build in 
under bitbake
 Prepend the build flags with those of bitbake. This is to build
 using the bitbake native sysroot include and library directories.
 
+Note from Alex: this is not appropriate for upstream submission as
+the recipe already does lots of similar in-place fixups elsewhere, so
+this patch shold be converted to follow that pattern. We're not going
+to fight against how upstream wants to configure the build.
+
 Signed-off-by: Ricardo Neri 
-Upstream-Status: Pending
+Upstream-Status: Inappropriate [needs to be converted to in-recipe fixups]
 ---
  BaseTools/Source/C/Makefiles/header.makefile | 17 +
  1 file changed, 9 insertions(+), 8 deletions(-)
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172313): 
https://lists.openembedded.org/g/openembedded-core/message/172313
Mute This Topic: https://lists.openembedded.org/mt/94683162/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 12/13] go: submit patch upstream

[Alexander Kanavin]

Note: it will not be reviewed until RP signs the google CLA
(link in the PR).

Signed-off-by: Alexander Kanavin 
---
 meta/recipes-devtools/go/go/filter-build-paths.patch | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/go/go/filter-build-paths.patch 
b/meta/recipes-devtools/go/go/filter-build-paths.patch
index a1aa37c2a4..a036f177e0 100644
--- a/meta/recipes-devtools/go/go/filter-build-paths.patch
+++ b/meta/recipes-devtools/go/go/filter-build-paths.patch
@@ -8,7 +8,9 @@ embedded in the go binary so that builds are reproducible 
regardless of build
 location. This codepath is hit for statically linked go binaries such as those
 on mips/ppc.
 
-Upstream-Status: Pending
+Upstream-Status: Submitted [https://github.com/golang/go/pull/56410]
+Note: RP needs to sign Google CLA for the PR to proceed.
+
 Signed-off-by: Richard Purdie 
 
 ---
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172314): 
https://lists.openembedded.org/g/openembedded-core/message/172314
Mute This Topic: https://lists.openembedded.org/mt/94683163/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 13/13] libffi: submit patch upstream

[Alexander Kanavin]

Signed-off-by: Alexander Kanavin 
---
 .../libffi/0001-arm-sysv-reverted-clang-VFP-mitigation.patch| 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/meta/recipes-support/libffi/libffi/0001-arm-sysv-reverted-clang-VFP-mitigation.patch
 
b/meta/recipes-support/libffi/libffi/0001-arm-sysv-reverted-clang-VFP-mitigation.patch
index 5e529d1ce7..4233799501 100644
--- 
a/meta/recipes-support/libffi/libffi/0001-arm-sysv-reverted-clang-VFP-mitigation.patch
+++ 
b/meta/recipes-support/libffi/libffi/0001-arm-sysv-reverted-clang-VFP-mitigation.patch
@@ -11,7 +11,7 @@ https://github.com/libffi/libffi/issues/607. Now that
 clang supports the LDC and SDC instructions, this mitigation
 has been reverted.
 
-Upstream-Status: Pending
+Upstream-Status: Submitted [https://github.com/libffi/libffi/pull/747]
 Signed-off-by: Brett Warren 
 ---
  src/arm/sysv.S | 33 -
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172315): 
https://lists.openembedded.org/g/openembedded-core/message/172315
Mute This Topic: https://lists.openembedded.org/mt/94683164/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] [yocto-security] OE-core CVE metrics for master on Sun 30 Oct 2022 02:00:01 AM HST

[Ross Burton]

On 30 Oct 2022, at 12:03, Steve Sakoman via lists.yoctoproject.org 
 wrote:
> 
> CVE-2022-43680 (CVSS3: 7.5 HIGH): expat:expat-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-43680 *

Patches incoming for this.

Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172316): 
https://lists.openembedded.org/g/openembedded-core/message/172316
Mute This Topic: https://lists.openembedded.org/mt/94684107/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] vim: upgrade 9.0.0614 -> 9.0.0820

[Tim Orling]

Includes fixes for CVE-2022-3705
https://nvd.nist.gov/vuln/detail/CVE-2022-3705

For a short list of important changes, see:
https://www.arp242.net/vimlog/

Signed-off-by: Tim Orling 
---
 meta/recipes-support/vim/vim.inc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-support/vim/vim.inc b/meta/recipes-support/vim/vim.inc
index 0710f6afbf2..298a111853a 100644
--- a/meta/recipes-support/vim/vim.inc
+++ b/meta/recipes-support/vim/vim.inc
@@ -20,8 +20,8 @@ SRC_URI = 
"git://github.com/vim/vim.git;branch=master;protocol=https \
file://no-path-adjust.patch \
"
 
-PV .= ".0614"
-SRCREV = "ef976323e770315b5fca544efb6b2faa25674d15"
+PV .= ".0820"
+SRCREV = "03d6e6f42b0deeb02d52c8a48c14abe431370c1c"
 
 # Remove when 8.3 is out
 UPSTREAM_VERSION_UNKNOWN = "1"
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172317): 
https://lists.openembedded.org/g/openembedded-core/message/172317
Mute This Topic: https://lists.openembedded.org/mt/94686115/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] Add nativesdk of systemd-systemctl

[Alexandre Belloni via lists.openembedded.org]

Hello, this causses the following failure on the AB:

AssertionError: 
The following recipes do not have a maintainer assigned to them. Please add an 
entry to meta/conf/distro/include/maintainers.inc file.
nativesdk-systemd-systemctl 
(/home/pokybuild/yocto-worker/oe-selftest-fedora/build/meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb)


On 31/10/2022 16:17:20+0800, wangmy wrote:
> From: Wang Mingyu 
> 
> Signed-off-by: Wang Mingyu 
> ---
>  .../systemd/nativesdk-systemd-systemctl.bb  | 17 +
>  1 file changed, 17 insertions(+)
>  create mode 100644 meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb
> 
> diff --git a/meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb 
> b/meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb
> new file mode 100644
> index 00..66b5ec5e6e
> --- /dev/null
> +++ b/meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb
> @@ -0,0 +1,17 @@
> +SUMMARY = "Wrapper for enabling systemd services"
> +
> +LICENSE = "MIT"
> +LIC_FILES_CHKSUM = 
> "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
> +
> +PR = "r0"
> +
> +inherit nativesdk
> +
> +SRC_URI = "file://systemctl"
> +
> +S = "${WORKDIR}"
> +
> +do_install() {
> + install -d ${D}${bindir}
> + install -m 0755 ${WORKDIR}/systemctl ${D}${bindir}
> +}
> -- 
> 2.25.1
> 

> 
> 
> 


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

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

[Ross Burton]

Signed-off-by: Ross Burton 
---
 meta/recipes-core/expat/{expat_2.4.9.bb => expat_2.5.0.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-core/expat/{expat_2.4.9.bb => expat_2.5.0.bb} (91%)

diff --git a/meta/recipes-core/expat/expat_2.4.9.bb 
b/meta/recipes-core/expat/expat_2.5.0.bb
similarity index 91%
rename from meta/recipes-core/expat/expat_2.4.9.bb
rename to meta/recipes-core/expat/expat_2.5.0.bb
index 9561edd84fc..aa8d439d5fb 100644
--- a/meta/recipes-core/expat/expat_2.4.9.bb
+++ b/meta/recipes-core/expat/expat_2.5.0.bb
@@ -15,7 +15,7 @@ SRC_URI = 
"${GITHUB_BASE_URI}/download/R_${VERSION_TAG}/expat-${PV}.tar.bz2  \
 GITHUB_BASE_URI = "https://github.com/libexpat/libexpat/releases/";
 UPSTREAM_CHECK_REGEX = "releases/tag/R_(?P.+)"
 
-SRC_URI[sha256sum] = 
"7f44d1469b110773a94b0d5abeeeffaef79f8bd6406b07e52394bcf48126437a"
+SRC_URI[sha256sum] = 
"6f0e6e01f7b30025fa05c85fdad1e5d0ec7fd35d9f61b22f34998de11969ff67"
 
 EXTRA_OECMAKE:class-native += "-DEXPAT_BUILD_DOCS=OFF"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172319): 
https://lists.openembedded.org/g/openembedded-core/message/172319
Mute This Topic: https://lists.openembedded.org/mt/94687647/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][langdale] expat cve

[Ross Burton]

---
 .../expat/expat/CVE-2022-43680.patch  | 33 +++
 meta/recipes-core/expat/expat_2.4.9.bb|  1 +
 2 files changed, 34 insertions(+)
 create mode 100644 meta/recipes-core/expat/expat/CVE-2022-43680.patch

diff --git a/meta/recipes-core/expat/expat/CVE-2022-43680.patch 
b/meta/recipes-core/expat/expat/CVE-2022-43680.patch
new file mode 100644
index 000..76c55edc768
--- /dev/null
+++ b/meta/recipes-core/expat/expat/CVE-2022-43680.patch
@@ -0,0 +1,33 @@
+CVE: CVE-2022-43680
+Upstream-Status: Backport [5290462a7ea1278a8d5c0d5b2860d4e244f997e4]
+Signed-off-by: Ross Burton 
+
+From 5290462a7ea1278a8d5c0d5b2860d4e244f997e4 Mon Sep 17 00:00:00 2001
+From: Sebastian Pipping 
+Date: Tue, 20 Sep 2022 02:44:34 +0200
+Subject: [PATCH] lib: Fix overeager DTD destruction in
+ XML_ExternalEntityParserCreate
+
+---
+ expat/lib/xmlparse.c | 8 
+ 1 file changed, 8 insertions(+)
+
+diff --git a/lib/xmlparse.c b/lib/xmlparse.c
+index aacd6e7fc..57bf103cc 100644
+--- a/lib/xmlparse.c
 b/lib/xmlparse.c
+@@ -1068,6 +1068,14 @@ parserCreate(const XML_Char *encodingName,
+   parserInit(parser, encodingName);
+ 
+   if (encodingName && ! parser->m_protocolEncodingName) {
++if (dtd) {
++  // We need to stop the upcoming call to XML_ParserFree from happily
++  // destroying parser->m_dtd because the DTD is shared with the parent
++  // parser and the only guard that keeps XML_ParserFree from destroying
++  // parser->m_dtd is parser->m_isParamEntity but it will be set to
++  // XML_TRUE only later in XML_ExternalEntityParserCreate (or not at 
all).
++  parser->m_dtd = NULL;
++}
+ XML_ParserFree(parser);
+ return NULL;
+   }
diff --git a/meta/recipes-core/expat/expat_2.4.9.bb 
b/meta/recipes-core/expat/expat_2.4.9.bb
index 9561edd84fc..bad1a96fdee 100644
--- a/meta/recipes-core/expat/expat_2.4.9.bb
+++ b/meta/recipes-core/expat/expat_2.4.9.bb
@@ -9,6 +9,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=7b3b078238d0901d3b339289117cb7fb"
 VERSION_TAG = "${@d.getVar('PV').replace('.', '_')}"
 
 SRC_URI = "${GITHUB_BASE_URI}/download/R_${VERSION_TAG}/expat-${PV}.tar.bz2  \
+   file://CVE-2022-43680.patch \
file://run-ptest \
"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172320): 
https://lists.openembedded.org/g/openembedded-core/message/172320
Mute This Topic: https://lists.openembedded.org/mt/94687680/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][langdale] expat: backport the fix for CVE-2022-43680

[Ross Burton]

Signed-off-by: Ross Burton 
---
 .../expat/expat/CVE-2022-43680.patch  | 33 +++
 meta/recipes-core/expat/expat_2.4.9.bb|  1 +
 2 files changed, 34 insertions(+)
 create mode 100644 meta/recipes-core/expat/expat/CVE-2022-43680.patch

diff --git a/meta/recipes-core/expat/expat/CVE-2022-43680.patch 
b/meta/recipes-core/expat/expat/CVE-2022-43680.patch
new file mode 100644
index 000..76c55edc768
--- /dev/null
+++ b/meta/recipes-core/expat/expat/CVE-2022-43680.patch
@@ -0,0 +1,33 @@
+CVE: CVE-2022-43680
+Upstream-Status: Backport [5290462a7ea1278a8d5c0d5b2860d4e244f997e4]
+Signed-off-by: Ross Burton 
+
+From 5290462a7ea1278a8d5c0d5b2860d4e244f997e4 Mon Sep 17 00:00:00 2001
+From: Sebastian Pipping 
+Date: Tue, 20 Sep 2022 02:44:34 +0200
+Subject: [PATCH] lib: Fix overeager DTD destruction in
+ XML_ExternalEntityParserCreate
+
+---
+ expat/lib/xmlparse.c | 8 
+ 1 file changed, 8 insertions(+)
+
+diff --git a/lib/xmlparse.c b/lib/xmlparse.c
+index aacd6e7fc..57bf103cc 100644
+--- a/lib/xmlparse.c
 b/lib/xmlparse.c
+@@ -1068,6 +1068,14 @@ parserCreate(const XML_Char *encodingName,
+   parserInit(parser, encodingName);
+ 
+   if (encodingName && ! parser->m_protocolEncodingName) {
++if (dtd) {
++  // We need to stop the upcoming call to XML_ParserFree from happily
++  // destroying parser->m_dtd because the DTD is shared with the parent
++  // parser and the only guard that keeps XML_ParserFree from destroying
++  // parser->m_dtd is parser->m_isParamEntity but it will be set to
++  // XML_TRUE only later in XML_ExternalEntityParserCreate (or not at 
all).
++  parser->m_dtd = NULL;
++}
+ XML_ParserFree(parser);
+ return NULL;
+   }
diff --git a/meta/recipes-core/expat/expat_2.4.9.bb 
b/meta/recipes-core/expat/expat_2.4.9.bb
index 9561edd84fc..bad1a96fdee 100644
--- a/meta/recipes-core/expat/expat_2.4.9.bb
+++ b/meta/recipes-core/expat/expat_2.4.9.bb
@@ -9,6 +9,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=7b3b078238d0901d3b339289117cb7fb"
 VERSION_TAG = "${@d.getVar('PV').replace('.', '_')}"
 
 SRC_URI = "${GITHUB_BASE_URI}/download/R_${VERSION_TAG}/expat-${PV}.tar.bz2  \
+   file://CVE-2022-43680.patch \
file://run-ptest \
"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172321): 
https://lists.openembedded.org/g/openembedded-core/message/172321
Mute This Topic: https://lists.openembedded.org/mt/94687694/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][langdale] expat cve

[Ross Burton]

Ignore this :)

> On 31 Oct 2022, at 15:20, Ross Burton via lists.openembedded.org 
>  wrote:
> 
> ---
> .../expat/expat/CVE-2022-43680.patch  | 33 +++
> meta/recipes-core/expat/expat_2.4.9.bb|  1 +
> 2 files changed, 34 insertions(+)
> create mode 100644 meta/recipes-core/expat/expat/CVE-2022-43680.patch
> 
> diff --git a/meta/recipes-core/expat/expat/CVE-2022-43680.patch 
> b/meta/recipes-core/expat/expat/CVE-2022-43680.patch
> new file mode 100644
> index 000..76c55edc768
> --- /dev/null
> +++ b/meta/recipes-core/expat/expat/CVE-2022-43680.patch
> @@ -0,0 +1,33 @@
> +CVE: CVE-2022-43680
> +Upstream-Status: Backport [5290462a7ea1278a8d5c0d5b2860d4e244f997e4]
> +Signed-off-by: Ross Burton 
> +
> +From 5290462a7ea1278a8d5c0d5b2860d4e244f997e4 Mon Sep 17 00:00:00 2001
> +From: Sebastian Pipping 
> +Date: Tue, 20 Sep 2022 02:44:34 +0200
> +Subject: [PATCH] lib: Fix overeager DTD destruction in
> + XML_ExternalEntityParserCreate
> +
> +---
> + expat/lib/xmlparse.c | 8 
> + 1 file changed, 8 insertions(+)
> +
> +diff --git a/lib/xmlparse.c b/lib/xmlparse.c
> +index aacd6e7fc..57bf103cc 100644
> +--- a/lib/xmlparse.c
>  b/lib/xmlparse.c
> +@@ -1068,6 +1068,14 @@ parserCreate(const XML_Char *encodingName,
> +   parserInit(parser, encodingName);
> + 
> +   if (encodingName && ! parser->m_protocolEncodingName) {
> ++if (dtd) {
> ++  // We need to stop the upcoming call to XML_ParserFree from happily
> ++  // destroying parser->m_dtd because the DTD is shared with the parent
> ++  // parser and the only guard that keeps XML_ParserFree from destroying
> ++  // parser->m_dtd is parser->m_isParamEntity but it will be set to
> ++  // XML_TRUE only later in XML_ExternalEntityParserCreate (or not at 
> all).
> ++  parser->m_dtd = NULL;
> ++}
> + XML_ParserFree(parser);
> + return NULL;
> +   }
> diff --git a/meta/recipes-core/expat/expat_2.4.9.bb 
> b/meta/recipes-core/expat/expat_2.4.9.bb
> index 9561edd84fc..bad1a96fdee 100644
> --- a/meta/recipes-core/expat/expat_2.4.9.bb
> +++ b/meta/recipes-core/expat/expat_2.4.9.bb
> @@ -9,6 +9,7 @@ LIC_FILES_CHKSUM = 
> "file://COPYING;md5=7b3b078238d0901d3b339289117cb7fb"
> VERSION_TAG = "${@d.getVar('PV').replace('.', '_')}"
> 
> SRC_URI = "${GITHUB_BASE_URI}/download/R_${VERSION_TAG}/expat-${PV}.tar.bz2  \
> +   file://CVE-2022-43680.patch \
>file://run-ptest \
>"
> 
> -- 
> 2.34.1
> 
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172322): 
https://lists.openembedded.org/g/openembedded-core/message/172322
Mute This Topic: https://lists.openembedded.org/mt/94687680/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][kirkstone][master][PATCH] rng-tools: Add Arm aarch64 CPU specific configuration to address excessive CPU usage on startup

[Khem Raj]

On Mon, Oct 31, 2022 at 12:51 AM Xiangyu Chen
 wrote:
>
> With the default jitter options aarch64 CPU-based devices typically 
> experience continuous
> high CPU utilisation for several minutes after rngd starts.
>
> Accoring to the rng-tools issue #150[1] and comments[2],in order to address 
> this,
> the following configuration changes have been made, those configurations
> also can be found on Alpine Linux[3]:
>
> - reduce the number of threads used to 1 in total, rather than 1 per core.
> - reduce the buffer size from 16535 to 4133 which reduces the time taken
>   to fill the buffer (and so reduces the duration of CPU load).
>
> [1] https://github.com/nhorman/rng-tools/issues/150
> [2] https://github.com/nhorman/rng-tools/issues/150#issuecomment-953079212
> [3] https://git.alpinelinux.org/aports/tree/main/rng-tools/rngd.confd-arm
>
> Signed-off-by: Xiangyu Chen 
> ---
>  .../rng-tools/rng-tools/default.aarch64   | 11 +++
>  meta/recipes-support/rng-tools/rng-tools_6.15.bb  |  5 +
>  2 files changed, 16 insertions(+)
>  create mode 100644 meta/recipes-support/rng-tools/rng-tools/default.aarch64
>
> diff --git a/meta/recipes-support/rng-tools/rng-tools/default.aarch64 
> b/meta/recipes-support/rng-tools/rng-tools/default.aarch64
> new file mode 100644
> index 00..5a2fbcc9ef
> --- /dev/null
> +++ b/meta/recipes-support/rng-tools/rng-tools/default.aarch64
> @@ -0,0 +1,11 @@
> +# With the default jitter options Arm CPU-based devices typically experience
> +# continuous high CPU utilisation for several minutes after rngd starts.
> +# See https://gitlab.alpinelinux.org/alpine/aports/-/issues/13035 and
> +# https://github.com/nhorman/rng-tools/issues/150
> +# In order to address this the following configuration changes have been 
> made:
> +#
> +#   - reduce the number of threads used to 1 in total, rather than 1 per 
> core.
> +#   - reduce the buffer size from 16535 to 4133 which reduces the time taken
> +# to fill the buffer (and so reduces the duration of CPU load).
> +#
> +EXTRA_ARGS="-r /dev/hwrng -O jitter:buffer_size:4133 -O 
> jitter:refill_thresh:4133 -O jitter:thread_count:1"
> diff --git a/meta/recipes-support/rng-tools/rng-tools_6.15.bb 
> b/meta/recipes-support/rng-tools/rng-tools_6.15.bb
> index 0696351903..e1f6b2ad77 100644
> --- a/meta/recipes-support/rng-tools/rng-tools_6.15.bb
> +++ b/meta/recipes-support/rng-tools/rng-tools_6.15.bb
> @@ -12,6 +12,7 @@ SRC_URI = 
> "git://github.com/nhorman/rng-tools.git;branch=master;protocol=https \
> file://init \
> file://default \
> file://rngd.service \
> +   file://default.aarch64 \
> "
>  SRCREV = "381f69828b782afda574f259c1b7549f48f9bb77"
>
> @@ -59,3 +60,7 @@ do_install:append() {
>  ${D}${systemd_system_unitdir}/rngd.service
>  fi
>  }
> +
> +do_install:append:aarch64() {
> +install -Dm 0644 ${WORKDIR}/default.aarch64 
> ${D}${sysconfdir}/default/rng-tools
> +}

Perhaps drop the aarch64 specific default file inside a folder called
aarch64 under meta/recipes-support/rng-tools/rng-tools
and we don't need any changes in recipe.

> --
> 2.34.1
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172323): 
https://lists.openembedded.org/g/openembedded-core/message/172323
Mute This Topic: https://lists.openembedded.org/mt/94680433/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] openssh: Install internal header/lib files

[Willy Tu via lists.openembedded.org]

Friendly ping. Is there any more concern on this?

Willy Tu


On Mon, Oct 24, 2022 at 10:07 AM Willy Tu via lists.openembedded.org
 wrote:
>
> Testing it out more and it seems like the current change is fine in that 
> regard.
>
> I was building it against an OpenBMC image which include the change and the 
> header and libssh.a files doesn't show up in the image itself
>
> ```
> ./tmp/work/izumi-openbmc-linux-gnueabi/obmc-phosphor-image
> ```
> doesn't have those files. I believe that's what we are looking for?
>
> Willy Tu
>
> On Mon, Oct 24, 2022 at 9:05 AM Willy Tu via lists.openembedded.org 
>  wrote:
>>
>> I am testing it out again and it seems like it does install to the target .
>>
>> ```
>> $ find -name libssh.a
>> ./tmp/sysroots-components/armv7a/openssh/usr/lib/libssh.a
>> ./tmp/work/armv7a-openbmc-linux-gnueabi/openssh/9.0p1-r0/image/usr/lib/libssh.a
>> ./tmp/work/armv7a-openbmc-linux-gnueabi/openssh/9.0p1-r0/sysroot-destdir/usr/lib/libssh.a
>> ./tmp/work/armv7a-openbmc-linux-gnueabi/openssh/9.0p1-r0/packages-split/openssh-staticdev/usr/lib/libssh.a
>> ./tmp/work/armv7a-openbmc-linux-gnueabi/openssh/9.0p1-r0/openssh-9.0p1/libssh.a
>> ./tmp/work/armv7a-openbmc-linux-gnueabi/openssh/9.0p1-r0/package/usr/lib/libssh.a
>> ./tmp/work/armv7a-openbmc-linux-gnueabi/hiba/1.0+gitAUTOINC+3199239c6a-r0/recipe-sysroot/usr/lib/libssh.a
>> ```
>> We don't want this, right?
>>
>> I'll have to try to figure it out and fix it.
>>
>> Willy Tu
>>
>> On Mon, Oct 24, 2022 at 7:57 AM Tristan Lelong  wrote:
>>>
>>>
>>>
>>> On Fri, Oct 21, 2022 at 6:22 PM Willy Tu  wrote:

 Hi Ross,

 Thanks for the feedback.

 Can you point to the right repo to update? Just to make sure that I 
 understand the concern, you are not referring to 
 https://github.com/openembedded/meta-openembedded/pull/597, right? I am 
 making changes to 
 http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-connectivity/openssh/openssh_9.0p1.bb
  which I thought is part of oe-core.

 @Tristan Lelong is the maintainer for hiba and is okay with the change. Do 
 you have any suggestions on installing it to just the sysroot in openssh 
 while using it from the hiba recipe? I was not able to do that when I 
 tried it.
>>>
>>>
>>> This was indeed discussed previously in another version of the patch, it 
>>> seemed the best way to expose OpenSSH's internal files was via the devel 
>>> package (not installed on the target), rather than hook into another 
>>> package's syroot.
>>>
>>> The OpenSSH static libraries and header files are currently not made 
>>> officially available because the API is not considered stable enough, but 
>>> exporting them in OE for HIBA (gated by a PACKAGECONFIG) in order to 
>>> support HIBA is fine.
>>>


 Thanks,

 Willy Tu




 On Fri, Oct 21, 2022 at 7:59 AM Ross Burton  wrote:
>
> Hi,
>
> oe-core doesn’t accept merge requests on the github mirrors, and you 
> pushed to meta-oe, which is a different repository.
>
> >> + if ${@bb.utils.contains('DISTRO_FEATURES', 'opensshinternals', 
> >> 'true', 'false', d)}; then
>
> This should be a PACKAGECONFIG, as it’s not a distro-wide setting.
>
> >> + install -d ${D}${includedir}/ssh
> >> + install -d ${D}${includedir}/ssh/openbsd-compat
> >> + install -m0644 ${S}/*.h ${D}${includedir}/ssh
> >> + install -m0644 ${S}/openbsd-compat/*.h 
> >> ${D}${includedir}/ssh/openbsd-compat
> >> +
> >> + install -d ${D}${libdir}
> >> + install -m0644 ${S}/libssh.a ${D}${libdir}
> >> + install -m0644 ${S}/openbsd-compat/libopenbsd-compat.a ${D}${libdir}
> >> + fi
>
> So you’re installing bits of the SSH source into the *target* packages 
> because one piece of software needs the build tree. This is clearly an 
> unsupported use of openssh, as the hiba build instructions literally say 
> “build openssh, then point hiba’s configure at that build tree”.  If
>
> I suggest a better approach would be to have a bbappend in your layer 
> which adds the files you need to *just the sysroot*, so the target 
> packages are unaltered.
>
> Ross
>>>
>>>
>>>
>>> --
>>> Tristan Lelong | SRE | tlel...@google.com |
>>
>>
>>
>>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172324): 
https://lists.openembedded.org/g/openembedded-core/message/172324
Mute This Topic: https://lists.openembedded.org/mt/94475279/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][kirkstone] expat: backport the fix for CVE-2022-43680

[Ross Burton]

Signed-off-by: Ross Burton 
---
 .../expat/expat/CVE-2022-43680.patch  | 33 +++
 meta/recipes-core/expat/expat_2.4.9.bb|  1 +
 2 files changed, 34 insertions(+)
 create mode 100644 meta/recipes-core/expat/expat/CVE-2022-43680.patch

diff --git a/meta/recipes-core/expat/expat/CVE-2022-43680.patch 
b/meta/recipes-core/expat/expat/CVE-2022-43680.patch
new file mode 100644
index 000..76c55edc768
--- /dev/null
+++ b/meta/recipes-core/expat/expat/CVE-2022-43680.patch
@@ -0,0 +1,33 @@
+CVE: CVE-2022-43680
+Upstream-Status: Backport [5290462a7ea1278a8d5c0d5b2860d4e244f997e4]
+Signed-off-by: Ross Burton 
+
+From 5290462a7ea1278a8d5c0d5b2860d4e244f997e4 Mon Sep 17 00:00:00 2001
+From: Sebastian Pipping 
+Date: Tue, 20 Sep 2022 02:44:34 +0200
+Subject: [PATCH] lib: Fix overeager DTD destruction in
+ XML_ExternalEntityParserCreate
+
+---
+ expat/lib/xmlparse.c | 8 
+ 1 file changed, 8 insertions(+)
+
+diff --git a/lib/xmlparse.c b/lib/xmlparse.c
+index aacd6e7fc..57bf103cc 100644
+--- a/lib/xmlparse.c
 b/lib/xmlparse.c
+@@ -1068,6 +1068,14 @@ parserCreate(const XML_Char *encodingName,
+   parserInit(parser, encodingName);
+ 
+   if (encodingName && ! parser->m_protocolEncodingName) {
++if (dtd) {
++  // We need to stop the upcoming call to XML_ParserFree from happily
++  // destroying parser->m_dtd because the DTD is shared with the parent
++  // parser and the only guard that keeps XML_ParserFree from destroying
++  // parser->m_dtd is parser->m_isParamEntity but it will be set to
++  // XML_TRUE only later in XML_ExternalEntityParserCreate (or not at 
all).
++  parser->m_dtd = NULL;
++}
+ XML_ParserFree(parser);
+ return NULL;
+   }
diff --git a/meta/recipes-core/expat/expat_2.4.9.bb 
b/meta/recipes-core/expat/expat_2.4.9.bb
index cb007708c78..22f9845a99b 100644
--- a/meta/recipes-core/expat/expat_2.4.9.bb
+++ b/meta/recipes-core/expat/expat_2.4.9.bb
@@ -9,6 +9,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=7b3b078238d0901d3b339289117cb7fb"
 VERSION_TAG = "${@d.getVar('PV').replace('.', '_')}"
 
 SRC_URI = 
"https://github.com/libexpat/libexpat/releases/download/R_${VERSION_TAG}/expat-${PV}.tar.bz2
  \
+   file://CVE-2022-43680.patch \
file://run-ptest \
"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172325): 
https://lists.openembedded.org/g/openembedded-core/message/172325
Mute This Topic: https://lists.openembedded.org/mt/94688283/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] [kirkstone][PATCH] overlayfs: Allow not used mount points

[Vyacheslav Yurkov]

The patch is now in master. Just a reminder to queue it to kirkstone as 
well.


Thanks,
Vyacheslav

On 12.10.2022 18:40, Steve Sakoman wrote:

On Tue, Oct 11, 2022 at 7:23 AM Vyacheslav Yurkov  wrote:

Just checking if something is missing to include this fix to kirkstone.

Yes, it needs to make it into the master branch first :-) I will then
cherry-pick for langdale and kirstone.

Richard is on holiday until 24 Oct, so it will occur shortly
thereafter.  It is already queued for the master branch, so there is
nothing else you need to do!

Steve


On 05.10.2022 13:17, Vyacheslav Yurkov via lists.openembedded.org wrote:

From: Vyacheslav Yurkov 

When machine configuration defines a mount point, which is not used in
any recipe, allow to fall through and only report a note in the logs.
This can be expected behavior, when a mount point is defined for several
machines, but not used in all of them

Signed-off-by: Vyacheslav Yurkov 
---
   meta/classes/overlayfs.bbclass | 6 +-
   meta/lib/oe/overlayfs.py   | 6 +-
   2 files changed, 10 insertions(+), 2 deletions(-)

diff --git a/meta/classes/overlayfs.bbclass b/meta/classes/overlayfs.bbclass
index f7069edd41..c3564b6ec1 100644
--- a/meta/classes/overlayfs.bbclass
+++ b/meta/classes/overlayfs.bbclass
@@ -96,7 +96,11 @@ python do_create_overlayfs_units() {
   overlayMountPoints = d.getVarFlags("OVERLAYFS_MOUNT_POINT")
   for mountPoint in overlayMountPoints:
   bb.debug(1, "Process variable flag %s" % mountPoint)
-for lower in d.getVarFlag('OVERLAYFS_WRITABLE_PATHS', 
mountPoint).split():
+lowerList = d.getVarFlag('OVERLAYFS_WRITABLE_PATHS', mountPoint)
+if not lowerList:
+bb.note("No mount points defined for %s flag, skipping" % 
(mountPoint))
+continue
+for lower in lowerList.split():
   bb.debug(1, "Prepare mount unit for %s with data mount point %s" 
%
(lower, d.getVarFlag('OVERLAYFS_MOUNT_POINT', 
mountPoint)))
   prepareUnits(d.getVarFlag('OVERLAYFS_MOUNT_POINT', mountPoint), 
lower)
diff --git a/meta/lib/oe/overlayfs.py b/meta/lib/oe/overlayfs.py
index b5d5e88e80..590c0de58a 100644
--- a/meta/lib/oe/overlayfs.py
+++ b/meta/lib/oe/overlayfs.py
@@ -38,7 +38,11 @@ def unitFileList(d):
   bb.fatal("Missing required mount point for OVERLAYFS_MOUNT_POINT[%s] 
in your MACHINE configuration" % mountPoint)

   for mountPoint in overlayMountPoints:
-for path in d.getVarFlag('OVERLAYFS_WRITABLE_PATHS', 
mountPoint).split():
+mountPointList = d.getVarFlag('OVERLAYFS_WRITABLE_PATHS', mountPoint)
+if not mountPointList:
+bb.debug(1, "No mount points defined for %s flag, don't add to file 
list", mountPoint)
+continue
+for path in mountPointList.split():
   fileList.append(mountUnitName(path))
   fileList.append(helperUnitName(path))







-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172326): 
https://lists.openembedded.org/g/openembedded-core/message/172326
Mute This Topic: https://lists.openembedded.org/mt/94132926/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: update 1.19 -> 1.19.2

[Alexander Kanavin]

Drop stack-protector.patch as issue fixed upstream.

Signed-off-by: Alexander Kanavin 
---
 .../go/{go-1.19.inc => go-1.19.2.inc} |  3 +-
 ...ive_1.19.bb => go-binary-native_1.19.2.bb} |  7 ++--
 ...an_1.19.bb => go-cross-canadian_1.19.2.bb} |  0
 .../{go-cross_1.19.bb => go-cross_1.19.2.bb}  |  0
 ...crosssdk_1.19.bb => go-crosssdk_1.19.2.bb} |  0
 ...{go-native_1.19.bb => go-native_1.19.2.bb} |  0
 ...o-runtime_1.19.bb => go-runtime_1.19.2.bb} |  0
 ...ent-based-hash-generation-less-pedan.patch |  8 ++---
 .../go/go/stack-protector.patch   | 32 ---
 .../go/{go_1.19.bb => go_1.19.2.bb}   |  0
 10 files changed, 9 insertions(+), 41 deletions(-)
 rename meta/recipes-devtools/go/{go-1.19.inc => go-1.19.2.inc} (85%)
 rename meta/recipes-devtools/go/{go-binary-native_1.19.bb => 
go-binary-native_1.19.2.bb} (75%)
 rename meta/recipes-devtools/go/{go-cross-canadian_1.19.bb => 
go-cross-canadian_1.19.2.bb} (100%)
 rename meta/recipes-devtools/go/{go-cross_1.19.bb => go-cross_1.19.2.bb} (100%)
 rename meta/recipes-devtools/go/{go-crosssdk_1.19.bb => go-crosssdk_1.19.2.bb} 
(100%)
 rename meta/recipes-devtools/go/{go-native_1.19.bb => go-native_1.19.2.bb} 
(100%)
 rename meta/recipes-devtools/go/{go-runtime_1.19.bb => go-runtime_1.19.2.bb} 
(100%)
 delete mode 100644 meta/recipes-devtools/go/go/stack-protector.patch
 rename meta/recipes-devtools/go/{go_1.19.bb => go_1.19.2.bb} (100%)

diff --git a/meta/recipes-devtools/go/go-1.19.inc 
b/meta/recipes-devtools/go/go-1.19.2.inc
similarity index 85%
rename from meta/recipes-devtools/go/go-1.19.inc
rename to meta/recipes-devtools/go/go-1.19.2.inc
index f733a807b4..206ee3ca45 100644
--- a/meta/recipes-devtools/go/go-1.19.inc
+++ b/meta/recipes-devtools/go/go-1.19.2.inc
@@ -14,6 +14,5 @@ SRC_URI += "\
 file://0001-exec.go-do-not-write-linker-flags-into-buildids.patch \
 file://0001-src-cmd-dist-buildgo.go-do-not-hardcode-host-compile.patch \
 file://filter-build-paths.patch \
-file://stack-protector.patch \
 "
-SRC_URI[main.sha256sum] = 
"9419cc70dc5a2523f29a77053cafff658ed21ef3561d9b6b020280ebceab28b9"
+SRC_URI[main.sha256sum] = 
"2ce930d70a931de660fdaf271d70192793b1b240272645bf0275779f6704df6b"
diff --git a/meta/recipes-devtools/go/go-binary-native_1.19.bb 
b/meta/recipes-devtools/go/go-binary-native_1.19.2.bb
similarity index 75%
rename from meta/recipes-devtools/go/go-binary-native_1.19.bb
rename to meta/recipes-devtools/go/go-binary-native_1.19.2.bb
index eda90f3753..65d7c9de49 100644
--- a/meta/recipes-devtools/go/go-binary-native_1.19.bb
+++ b/meta/recipes-devtools/go/go-binary-native_1.19.2.bb
@@ -7,10 +7,11 @@ LIC_FILES_CHKSUM = 
"file://LICENSE;md5=5d4950ecb7b26d2c5e4e7b4e0dd74707"
 
 PROVIDES = "go-native"
 
+# Checksums available at https://go.dev/dl/
 SRC_URI = 
"https://dl.google.com/go/go${PV}.${BUILD_GOOS}-${BUILD_GOARCH}.tar.gz;name=go_${BUILD_GOTUPLE}";
-SRC_URI[go_linux_amd64.sha256sum] = 
"464b6b66591f6cf055bc5df90a9750bf5fbc9d038722bb84a9d56a2bea974be6"
-SRC_URI[go_linux_arm64.sha256sum] = 
"efa97fac9574fc6ef6c9ff3e3758fb85f1439b046573bf434cccb5e012bd00c8"
-SRC_URI[go_linux_ppc64le.sha256sum] = 
"92bf5aa598a01b279d03847c32788a3a7e0a247a029dedb7c759811c2a4241fc"
+SRC_URI[go_linux_amd64.sha256sum] = 
"5e8c5a74fe6470dd7e055a461acda8bb4050ead8c2df70f227e3ff7d8eb7eeb6"
+SRC_URI[go_linux_arm64.sha256sum] = 
"b62a8d9654436c67c14a0c91e931d50440541f09eb991a987536cb982903126d"
+SRC_URI[go_linux_ppc64le.sha256sum] = 
"37e1d4342f7103aeb9babeabe8c71ef3dba23db28db525071119e94b2aa21d7d"
 
 UPSTREAM_CHECK_URI = "https://golang.org/dl/";
 UPSTREAM_CHECK_REGEX = "go(?P\d+(\.\d+)+)\.linux"
diff --git a/meta/recipes-devtools/go/go-cross-canadian_1.19.bb 
b/meta/recipes-devtools/go/go-cross-canadian_1.19.2.bb
similarity index 100%
rename from meta/recipes-devtools/go/go-cross-canadian_1.19.bb
rename to meta/recipes-devtools/go/go-cross-canadian_1.19.2.bb
diff --git a/meta/recipes-devtools/go/go-cross_1.19.bb 
b/meta/recipes-devtools/go/go-cross_1.19.2.bb
similarity index 100%
rename from meta/recipes-devtools/go/go-cross_1.19.bb
rename to meta/recipes-devtools/go/go-cross_1.19.2.bb
diff --git a/meta/recipes-devtools/go/go-crosssdk_1.19.bb 
b/meta/recipes-devtools/go/go-crosssdk_1.19.2.bb
similarity index 100%
rename from meta/recipes-devtools/go/go-crosssdk_1.19.bb
rename to meta/recipes-devtools/go/go-crosssdk_1.19.2.bb
diff --git a/meta/recipes-devtools/go/go-native_1.19.bb 
b/meta/recipes-devtools/go/go-native_1.19.2.bb
similarity index 100%
rename from meta/recipes-devtools/go/go-native_1.19.bb
rename to meta/recipes-devtools/go/go-native_1.19.2.bb
diff --git a/meta/recipes-devtools/go/go-runtime_1.19.bb 
b/meta/recipes-devtools/go/go-runtime_1.19.2.bb
similarity index 100%
rename from meta/recipes-devtools/go/go-runtime_1.19.bb
rename to meta/recipes-devtools/go/go-runtime_1.19.2.bb
diff --git 
a/meta/recipes-devtools/go/go/0001-cmd-go-make-content-based-hash-generation-less-pedan.patch
 
b/meta/recipes-devt

[OE-core] [PATCH] go: Upgrade to 1.19.2

[Khem Raj]

go1.19.1 (released 2022-09-06) includes security fixes to the net/http and 
net/url packages,
as well as bug fixes to the compiler, the go command, the pprof command, the 
linker, the
runtime, and the crypto/tls and crypto/x509 packages. See the Go 1.19.1 
milestone[1] on our
issue tracker for details.

go1.19.2 (released 2022-10-04) includes security fixes to the archive/tar,
net/http/httputil, and regexp packages, as well as bug fixes to the compiler, 
the linker,
the runtime, and the go/types package. See the Go 1.19.2 milestone[2] on our 
issue tracker
for details.

Forward port patches as needed
Drop stack-protector.patch, its already upstream

Includes fixed for CVE-2022-2879, CVE-2022-2880, and CVE-2022-41715

[1] 
https://github.com/golang/go/issues?q=milestone%3AGo1.19.1+label%3ACherryPickApproved
[2] 
https://github.com/golang/go/issues?q=milestone%3AGo1.19.2+label%3ACherryPickApproved

Signed-off-by: Khem Raj 
---
 .../go/{go-1.19.inc => go-1.19.2.inc} |  3 +-
 ...ive_1.19.bb => go-binary-native_1.19.2.bb} |  6 ++--
 ...an_1.19.bb => go-cross-canadian_1.19.2.bb} |  0
 .../{go-cross_1.19.bb => go-cross_1.19.2.bb}  |  0
 ...crosssdk_1.19.bb => go-crosssdk_1.19.2.bb} |  0
 ...{go-native_1.19.bb => go-native_1.19.2.bb} |  0
 ...o-runtime_1.19.bb => go-runtime_1.19.2.bb} |  0
 ...ent-based-hash-generation-less-pedan.patch | 22 ++---
 .../go/go/stack-protector.patch   | 32 ---
 .../go/{go_1.19.bb => go_1.19.2.bb}   |  0
 10 files changed, 13 insertions(+), 50 deletions(-)
 rename meta/recipes-devtools/go/{go-1.19.inc => go-1.19.2.inc} (85%)
 rename meta/recipes-devtools/go/{go-binary-native_1.19.bb => 
go-binary-native_1.19.2.bb} (77%)
 rename meta/recipes-devtools/go/{go-cross-canadian_1.19.bb => 
go-cross-canadian_1.19.2.bb} (100%)
 rename meta/recipes-devtools/go/{go-cross_1.19.bb => go-cross_1.19.2.bb} (100%)
 rename meta/recipes-devtools/go/{go-crosssdk_1.19.bb => go-crosssdk_1.19.2.bb} 
(100%)
 rename meta/recipes-devtools/go/{go-native_1.19.bb => go-native_1.19.2.bb} 
(100%)
 rename meta/recipes-devtools/go/{go-runtime_1.19.bb => go-runtime_1.19.2.bb} 
(100%)
 delete mode 100644 meta/recipes-devtools/go/go/stack-protector.patch
 rename meta/recipes-devtools/go/{go_1.19.bb => go_1.19.2.bb} (100%)

diff --git a/meta/recipes-devtools/go/go-1.19.inc 
b/meta/recipes-devtools/go/go-1.19.2.inc
similarity index 85%
rename from meta/recipes-devtools/go/go-1.19.inc
rename to meta/recipes-devtools/go/go-1.19.2.inc
index f733a807b4..206ee3ca45 100644
--- a/meta/recipes-devtools/go/go-1.19.inc
+++ b/meta/recipes-devtools/go/go-1.19.2.inc
@@ -14,6 +14,5 @@ SRC_URI += "\
 file://0001-exec.go-do-not-write-linker-flags-into-buildids.patch \
 file://0001-src-cmd-dist-buildgo.go-do-not-hardcode-host-compile.patch \
 file://filter-build-paths.patch \
-file://stack-protector.patch \
 "
-SRC_URI[main.sha256sum] = 
"9419cc70dc5a2523f29a77053cafff658ed21ef3561d9b6b020280ebceab28b9"
+SRC_URI[main.sha256sum] = 
"2ce930d70a931de660fdaf271d70192793b1b240272645bf0275779f6704df6b"
diff --git a/meta/recipes-devtools/go/go-binary-native_1.19.bb 
b/meta/recipes-devtools/go/go-binary-native_1.19.2.bb
similarity index 77%
rename from meta/recipes-devtools/go/go-binary-native_1.19.bb
rename to meta/recipes-devtools/go/go-binary-native_1.19.2.bb
index eda90f3753..ebf45954e6 100644
--- a/meta/recipes-devtools/go/go-binary-native_1.19.bb
+++ b/meta/recipes-devtools/go/go-binary-native_1.19.2.bb
@@ -8,9 +8,9 @@ LIC_FILES_CHKSUM = 
"file://LICENSE;md5=5d4950ecb7b26d2c5e4e7b4e0dd74707"
 PROVIDES = "go-native"
 
 SRC_URI = 
"https://dl.google.com/go/go${PV}.${BUILD_GOOS}-${BUILD_GOARCH}.tar.gz;name=go_${BUILD_GOTUPLE}";
-SRC_URI[go_linux_amd64.sha256sum] = 
"464b6b66591f6cf055bc5df90a9750bf5fbc9d038722bb84a9d56a2bea974be6"
-SRC_URI[go_linux_arm64.sha256sum] = 
"efa97fac9574fc6ef6c9ff3e3758fb85f1439b046573bf434cccb5e012bd00c8"
-SRC_URI[go_linux_ppc64le.sha256sum] = 
"92bf5aa598a01b279d03847c32788a3a7e0a247a029dedb7c759811c2a4241fc"
+SRC_URI[go_linux_amd64.sha256sum] = 
"5e8c5a74fe6470dd7e055a461acda8bb4050ead8c2df70f227e3ff7d8eb7eeb6"
+SRC_URI[go_linux_arm64.sha256sum] = 
"b62a8d9654436c67c14a0c91e931d50440541f09eb991a987536cb982903126d"
+SRC_URI[go_linux_ppc64le.sha256sum] = 
"37e1d4342f7103aeb9babeabe8c71ef3dba23db28db525071119e94b2aa21d7d"
 
 UPSTREAM_CHECK_URI = "https://golang.org/dl/";
 UPSTREAM_CHECK_REGEX = "go(?P\d+(\.\d+)+)\.linux"
diff --git a/meta/recipes-devtools/go/go-cross-canadian_1.19.bb 
b/meta/recipes-devtools/go/go-cross-canadian_1.19.2.bb
similarity index 100%
rename from meta/recipes-devtools/go/go-cross-canadian_1.19.bb
rename to meta/recipes-devtools/go/go-cross-canadian_1.19.2.bb
diff --git a/meta/recipes-devtools/go/go-cross_1.19.bb 
b/meta/recipes-devtools/go/go-cross_1.19.2.bb
similarity index 100%
rename from meta/recipes-devtools/go/go-cross_1.19.bb
rename to meta/recipes-devtools/go/go-cross_1.19.2.bb
diff --git a/meta/recipes-devtools/go/g

Re: [OE-core] OE-core CVE metrics for master on Sun 30 Oct 2022 02:00:01 AM HST

[Khem Raj]

On Sun, Oct 30, 2022 at 5:03 AM Steve Sakoman  wrote:
>
> Branch: master
>
> New this week: 2 CVEs
> CVE-2022-3705 (CVSS3: 7.5 HIGH): vim 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3705 *
> CVE-2022-43680 (CVSS3: 7.5 HIGH): expat:expat-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-43680 *
>
> Removed this week: 17 CVEs
> CVE-2022-3165 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3165 *
> CVE-2022-3352 (CVSS3: 7.8 HIGH): vim 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3352 *
> CVE-2022-3358 (CVSS3: 7.5 HIGH): openssl:openssl-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3358 *
> CVE-2022-3550 (CVSS3: 9.8 CRITICAL): xserver-xorg 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3550 *
> CVE-2022-3551 (CVSS3: 7.5 HIGH): xserver-xorg 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3551 *
> CVE-2022-3553 (CVSS3: 7.5 HIGH): xserver-xorg 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3553 *
> CVE-2022-3554 (CVSS3: 7.5 HIGH): libx11:libx11-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3554 *
> CVE-2022-3555 (CVSS3: 7.5 HIGH): libx11:libx11-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3555 *
> CVE-2022-3570 (CVSS3: 9.8 CRITICAL): tiff 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3570 *
> CVE-2022-3597 (CVSS3: 6.5 MEDIUM): tiff 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3597 *
> CVE-2022-3598 (CVSS3: 6.5 MEDIUM): tiff 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3598 *
> CVE-2022-3599 (CVSS3: 6.5 MEDIUM): tiff 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3599 *
> CVE-2022-3626 (CVSS3: 6.5 MEDIUM): tiff 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3626 *
> CVE-2022-3627 (CVSS3: 6.5 MEDIUM): tiff 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3627 *
> CVE-2022-39253 (CVSS3: 5.5 MEDIUM): git 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39253 *
> CVE-2022-39260 (CVSS3: 8.8 HIGH): git 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39260 *
> CVE-2022-41556 (CVSS3: 7.5 HIGH): lighttpd 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41556 *
>
> Full list:  Found 5 unpatched CVEs
> CVE-2022-2879 (CVSS3: 7.5 HIGH): go 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2879 *
> CVE-2022-2880 (CVSS3: 7.5 HIGH): go 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2880 *
> CVE-2022-3705 (CVSS3: 7.5 HIGH): vim 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3705 *
> CVE-2022-41715 (CVSS3: 7.5 HIGH): go 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41715 *

Sent a patch for 1.19.2 upgrade which should take care of all go CVEs
reported here.

> CVE-2022-43680 (CVSS3: 7.5 HIGH): expat:expat-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-43680 *
>
> For further information see: 
> https://autobuilder.yocto.io/pub/non-release/patchmetrics/
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172329): 
https://lists.openembedded.org/g/openembedded-core/message/172329
Mute This Topic: https://lists.openembedded.org/mt/94662953/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] Add nativesdk of systemd-systemctl

[Ross Burton]

On 31 Oct 2022, at 08:17, wangmy via lists.openembedded.org 
 wrote:
> 
> From: Wang Mingyu 
> 
> Signed-off-by: Wang Mingyu 
> ---
> .../systemd/nativesdk-systemd-systemctl.bb  | 17 +
> 1 file changed, 17 insertions(+)
> create mode 100644 meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb
> 
> diff --git a/meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb 
> b/meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb
> new file mode 100644
> index 00..66b5ec5e6e
> --- /dev/null
> +++ b/meta/recipes-core/systemd/nativesdk-systemd-systemctl.bb
> @@ -0,0 +1,17 @@
> +SUMMARY = "Wrapper for enabling systemd services"
> +
> +LICENSE = "MIT"
> +LIC_FILES_CHKSUM = 
> "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
> +
> +PR = "r0"
> +
> +inherit nativesdk
> +
> +SRC_URI = "file://systemctl"
> +
> +S = "${WORKDIR}"
> +
> +do_install() {
> + install -d ${D}${bindir}
> + install -m 0755 ${WORKDIR}/systemctl ${D}${bindir}
> +}

As the native and nativesdk recipes are almost identical, write a single recipe 
called systemd-systemctl which uses BBCLASSEXTEND which replaces this recipe 
and the existing native form.

You can then fix the ownership in maintainers to refer to the base recipe, and 
solve the oe-selftest failure too.

Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172330): 
https://lists.openembedded.org/g/openembedded-core/message/172330
Mute This Topic: https://lists.openembedded.org/mt/94680777/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] bluez5: Point hciattach bcm43xx firmware search path to /lib/firmware

[Marek Vasut]

Currently the hciattach bcm43xx firmware loader looks up the firmware
blob in /etc/firmware . Change this to /lib/firmware instead, so that
the path is consistent with Linux kernel which also looks up firmware
for the WiFi part in /lib/firmware .

Signed-off-by: Marek Vasut 
---
Cc: Alexander Kanavin 
Cc: Alexandre Belloni 
Cc: Richard Purdie 
---
 meta/recipes-connectivity/bluez5/bluez5.inc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-connectivity/bluez5/bluez5.inc 
b/meta/recipes-connectivity/bluez5/bluez5.inc
index f07e318897..fe10be7324 100644
--- a/meta/recipes-connectivity/bluez5/bluez5.inc
+++ b/meta/recipes-connectivity/bluez5/bluez5.inc
@@ -68,6 +68,8 @@ EXTRA_OECONF = "\
   --without-zsh-completion-dir \
 "
 
+CFLAGS:append = " -DFIRMWARE_DIR=\\"/lib/firmware\\""
+
 # bluez5 builds a large number of useful utilities but does not
 # install them.  Specify which ones we want put into ${PN}-noinst-tools.
 NOINST_TOOLS_READLINE ??= ""
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172331): 
https://lists.openembedded.org/g/openembedded-core/message/172331
Mute This Topic: https://lists.openembedded.org/mt/94689423/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 1/1] wayland: fix CVE-2021-3782

[Narpat Mali]

An internal reference count is held on the buffer pool,
incremented every time a new buffer is created from the pool.
The reference count is maintained as an int;
on LP64 systems this can cause thereference count to overflow if
the client creates a large number of wl_shm buffer objects,
or if it can coerce the server to create a large number of external references
to the buffer storage. With the reference count overflowing, a use-after-free
can be constructed on the wl_shm_pool tracking structure,
where values may be incremented or decremented;
it may also be possible to construct a limited oracle to leak 4 bytes of
server-side memory to the attacking client at a time.

Reference:
https://nvd.nist.gov/vuln/detail/CVE-2021-3782

Upstream patch:
https://gitlab.freedesktop.org/wayland/wayland/-/commit/b19488c7154b902354cb26a27f11415d7799b0b2

Signed-off-by: Narpat Mali 
---
 .../wayland/wayland/CVE-2021-3782.patch   | 111 ++
 .../wayland/wayland_1.20.0.bb |   2 +
 2 files changed, 113 insertions(+)
 create mode 100644 meta/recipes-graphics/wayland/wayland/CVE-2021-3782.patch

diff --git a/meta/recipes-graphics/wayland/wayland/CVE-2021-3782.patch 
b/meta/recipes-graphics/wayland/wayland/CVE-2021-3782.patch
new file mode 100644
index 00..df204508e9
--- /dev/null
+++ b/meta/recipes-graphics/wayland/wayland/CVE-2021-3782.patch
@@ -0,0 +1,111 @@
+From 5eed6609619cc2e4eaa8618d11c15d442abf54be Mon Sep 17 00:00:00 2001
+From: Derek Foreman 
+Date: Fri, 28 Jan 2022 13:18:37 -0600
+Subject: [PATCH] util: Limit size of wl_map
+
+Since server IDs are basically indistinguishable from really big client
+IDs at many points in the source, it's theoretically possible to overflow
+a map and either overflow server IDs into the client ID space, or grow
+client IDs into the server ID space. This would currently take a massive
+amount of RAM, but the definition of massive changes yearly.
+
+Prevent this by placing a ridiculous but arbitrary upper bound on the
+number of items we can put in a map: 0xF0, somewhere over 15 million.
+This should satisfy pathological clients without restriction, but stays
+well clear of the 0xFF00 transition point between server and client
+IDs. It will still take an improbable amount of RAM to hit this, and a
+client could still exhaust all RAM in this way, but our goal is to prevent
+overflow and undefined behaviour.
+
+Fixes #224
+
+Signed-off-by: Derek Foreman 
+
+Upstream-Status: Backport
+CVE: CVE-2021-3782
+
+Reference to upstream patch:
+https://gitlab.freedesktop.org/wayland/wayland/-/commit/b19488c7154b902354cb26a27f11415d7799b0b2
+
+[DP: adjust context for wayland version 1.20.0]
+Signed-off-by: Dragos-Marian Panait 
+---
+ src/wayland-private.h |  1 +
+ src/wayland-util.c| 25 +++--
+ 2 files changed, 24 insertions(+), 2 deletions(-)
+
+diff --git a/src/wayland-private.h b/src/wayland-private.h
+index 9bf8cb7..35dc40e 100644
+--- a/src/wayland-private.h
 b/src/wayland-private.h
+@@ -45,6 +45,7 @@
+ #define WL_MAP_SERVER_SIDE 0
+ #define WL_MAP_CLIENT_SIDE 1
+ #define WL_SERVER_ID_START 0xff00
++#define WL_MAP_MAX_OBJECTS 0x00f0
+ #define WL_CLOSURE_MAX_ARGS 20
+ 
+ struct wl_object {
+diff --git a/src/wayland-util.c b/src/wayland-util.c
+index d5973bf..3e45d19 100644
+--- a/src/wayland-util.c
 b/src/wayland-util.c
+@@ -195,6 +195,7 @@ wl_map_insert_new(struct wl_map *map, uint32_t flags, void 
*data)
+   union map_entry *start, *entry;
+   struct wl_array *entries;
+   uint32_t base;
++  uint32_t count;
+ 
+   if (map->side == WL_MAP_CLIENT_SIDE) {
+   entries = &map->client_entries;
+@@ -215,10 +216,25 @@ wl_map_insert_new(struct wl_map *map, uint32_t flags, 
void *data)
+   start = entries->data;
+   }
+ 
++  /* wl_array only grows, so if we have too many objects at
++   * this point there's no way to clean up. We could be more
++   * pro-active about trying to avoid this allocation, but
++   * it doesn't really matter because at this point there is
++   * nothing to be done but disconnect the client and delete
++   * the whole array either way.
++   */
++  count = entry - start;
++  if (count > WL_MAP_MAX_OBJECTS) {
++  /* entry->data is freshly malloced garbage, so we'd
++   * better make it a NULL so wl_map_for_each doesn't
++   * dereference it later. */
++  entry->data = NULL;
++  return 0;
++  }
+   entry->data = data;
+   entry->next |= (flags & 0x1) << 1;
+ 
+-  return (entry - start) + base;
++  return count + base;
+ }
+ 
+ int
+@@ -235,6 +251,9 @@ wl_map_insert_at(struct wl_map *map, uint32_t flags, 
uint32_t i, void *data)
+   i -= WL_SERVER_ID_START;
+   }
+ 
++  if (i > WL_MAP_MAX_OBJECTS)
++  return -1;
++
+   count = entries->size / sizeof *start;
+   if (count < i)
+   r

Re: [OE-core] [PATCH] bluez5: Point hciattach bcm43xx firmware search path to /lib/firmware

[Jose Quaresma]

Hi Marek,

Marek Vasut  escreveu no dia segunda, 31/10/2022 à(s) 16:30:

> Currently the hciattach bcm43xx firmware loader looks up the firmware
> blob in /etc/firmware . Change this to /lib/firmware instead, so that
> the path is consistent with Linux kernel which also looks up firmware
> for the WiFi part in /lib/firmware .
>
> Signed-off-by: Marek Vasut 
> ---
> Cc: Alexander Kanavin 
> Cc: Alexandre Belloni 
> Cc: Richard Purdie 
> ---
>  meta/recipes-connectivity/bluez5/bluez5.inc | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-connectivity/bluez5/bluez5.inc
> b/meta/recipes-connectivity/bluez5/bluez5.inc
> index f07e318897..fe10be7324 100644
> --- a/meta/recipes-connectivity/bluez5/bluez5.inc
> +++ b/meta/recipes-connectivity/bluez5/bluez5.inc
> @@ -68,6 +68,8 @@ EXTRA_OECONF = "\
>--without-zsh-completion-dir \
>  "
>
> +CFLAGS:append = " -DFIRMWARE_DIR=\\"/lib/firmware\\""
>

Escape chars can be tricky when parsing and as the path
doesn't have any space we can have " -DFIRMWARE_DIR=/lib/firmware"
or not?

Another options to avoid escape chars can be
CFLAGS:append = ' -DFIRMWARE_DIR="/lib/firmware"'

Jose


> +
>  # bluez5 builds a large number of useful utilities but does not
>  # install them.  Specify which ones we want put into ${PN}-noinst-tools.
>  NOINST_TOOLS_READLINE ??= ""
> --
> 2.35.1
>
>
> 
>
>

-- 
Best regards,

José Quaresma

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

[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 413
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.2", "4.3", "4.99" and "Future", the more pressing/urgent
issues being in "4.2" and then "4.3".

 

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 (#172334): 
https://lists.openembedded.org/g/openembedded-core/message/172334
Mute This Topic: https://lists.openembedded.org/mt/94695965/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] systemd: change syntax for SRC_URI append

[Peter Bergin]

In order to be able to override the git repo used in a bbappend
file the additions of files to SRC_URI needs to be done with :append
instead of +=, otherwise those will not be added.

My use case for this change is to try to build latest
systemd that is located in another repo than the one used
by the recipe (systemd.git instead of systemd-stable.git).
With this change this is possible to do by having SRC_URI, SRCREV
and SRCBRANCH in a bbappend.

Signed-off-by: Peter Bergin 
---
 meta/recipes-core/systemd/systemd_251.4.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/systemd/systemd_251.4.bb 
b/meta/recipes-core/systemd/systemd_251.4.bb
index 87668cadc7..f6c9640823 100644
--- a/meta/recipes-core/systemd/systemd_251.4.bb
+++ b/meta/recipes-core/systemd/systemd_251.4.bb
@@ -14,7 +14,7 @@ inherit useradd pkgconfig meson perlnative update-rc.d 
update-alternatives qemu
 # that we don't build both udev and systemd in world builds.
 REQUIRED_DISTRO_FEATURES = "systemd"
 
-SRC_URI += " \
+SRC_URI:append = " \
file://touchscreen.rules \
file://00-create-volatile.conf \
${@bb.utils.contains('PACKAGECONFIG', 'polkit_hostnamed_fallback', 
'file://org.freedesktop.hostname1_no_polkit.conf', '', d)} \
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172335): 
https://lists.openembedded.org/g/openembedded-core/message/172335
Mute This Topic: https://lists.openembedded.org/mt/94696056/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] gptfdisk: remove warning message from target system

[Peter Bergin]

A recent change in libuuid made warning when running
sgdisk. Backport patch from upstream to silent warning.

The warning:
"Warning! Unable to generate a proper UUID! Creating an improper one as a 
last
 resort! Windows 7 may crash if you save this partition table!"

Signed-off-by: Peter Bergin 
---
 ...to-deal-with-minor-change-in-libuuid.patch | 27 +++
 meta/recipes-devtools/fdisk/gptfdisk_1.0.9.bb |  1 +
 2 files changed, 28 insertions(+)
 create mode 100644 
meta/recipes-devtools/fdisk/gptfdisk/0001-Updated-guid.cc-to-deal-with-minor-change-in-libuuid.patch

diff --git 
a/meta/recipes-devtools/fdisk/gptfdisk/0001-Updated-guid.cc-to-deal-with-minor-change-in-libuuid.patch
 
b/meta/recipes-devtools/fdisk/gptfdisk/0001-Updated-guid.cc-to-deal-with-minor-change-in-libuuid.patch
new file mode 100644
index 00..f358081092
--- /dev/null
+++ 
b/meta/recipes-devtools/fdisk/gptfdisk/0001-Updated-guid.cc-to-deal-with-minor-change-in-libuuid.patch
@@ -0,0 +1,27 @@
+From c640d9011a8330ebaad501784fb0ee1ce5e7a5ef Mon Sep 17 00:00:00 2001
+From: Rod Smith 
+Date: Sat, 16 Apr 2022 09:32:04 -0400
+Subject: [PATCH] Updated guid.cc to deal with minor change in libuuid
+
+Upstream-Status: Backport 
[https://sourceforge.net/p/gptfdisk/code/ci/6a8416cbd12d55f882bb751993b94f72d338d96f/]
+Signed-off-by: Peter Bergin 
+---
+ guid.cc | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/guid.cc b/guid.cc
+index 1e73ab7..d3e4fd5 100644
+--- a/guid.cc
 b/guid.cc
+@@ -141,7 +141,7 @@ void GUIDData::Zero(void) {
+ void GUIDData::Randomize(void) {
+int i, uuidGenerated = 0;
+ 
+-#ifdef _UUID_UUID_H
++#if defined (_UUID_UUID_H) || defined (_UL_LIBUUID_UUID_H)
+uuid_generate(uuidData);
+ReverseBytes(&uuidData[0], 4);
+ReverseBytes(&uuidData[4], 2);
+-- 
+2.34.1
+
diff --git a/meta/recipes-devtools/fdisk/gptfdisk_1.0.9.bb 
b/meta/recipes-devtools/fdisk/gptfdisk_1.0.9.bb
index e473b9cd55..2c093c20ae 100644
--- a/meta/recipes-devtools/fdisk/gptfdisk_1.0.9.bb
+++ b/meta/recipes-devtools/fdisk/gptfdisk_1.0.9.bb
@@ -9,6 +9,7 @@ DEPENDS = "util-linux"
 
 SRC_URI = "${SOURCEFORGE_MIRROR}/${BPN}/${PV}/${BP}.tar.gz \
file://0001-gptcurses-correctly-include-curses.h.patch \
+   
file://0001-Updated-guid.cc-to-deal-with-minor-change-in-libuuid.patch \
"
 SRC_URI[sha256sum] = 
"dafead2693faeb8e8b97832b23407f6ed5b3219bc1784f482dd855774e2d50c2"
 
-- 
2.34.1


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

[OE-core] Current high bug count owners for Yocto Project 4.2

[Stephen Jolley]

All,

Below is the list as of top 36 bug owners as of the end of WW44 of who have
open medium or higher bugs and enhancements against YP 4.2.   There are 123
possible work days left until the final release candidates for YP 4.2 needs
to be released.


Who

Count


michael.opdenac...@bootlin.com

34


ross.bur...@arm.com

30


randy.macl...@windriver.com

26


bruce.ashfi...@gmail.com

24


david.re...@windriver.com

23


richard.pur...@linuxfoundation.org

17


jpewhac...@gmail.com

10


sakib.sa...@windriver.com

10


pa...@zhukoff.net

9


saul.w...@windriver.com

9


tim.orl...@konsulko.com

4


sundeep.kokko...@gmail.com

3


akuster...@gmail.com

3


martin.ja...@gmail.com

2


aeh...@gmail.com

2


zheng@windriver.com

2


jon.ma...@arm.com

2


hongxu@windriver.com

2


pgowda@gmail.com

2


raj.k...@gmail.com

2


s...@bigsur.com

2


alexandre.bell...@bootlin.com

1


rybczyn...@gmail.com

1


mostthings...@gmail.com

1


qi.c...@windriver.com

1


sundeep.kokko...@windriver.com

1


thomas.per...@bootlin.com

1


tvgamb...@gmail.com

1


open.sou...@oleksandr-kravchuk.com

1


mhalst...@linuxfoundation.org

1


st...@sakoman.com

1


hummerbl...@gmail.com

1


ptsne...@gmail.com

1


anton.anto...@arm.com

1


martin.bee...@online.de

1


nicolas.deche...@linaro.org

1


Grand Total

233

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 (#172337): 
https://lists.openembedded.org/g/openembedded-core/message/172337
Mute This Topic: https://lists.openembedded.org/mt/94696183/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] systemd: change syntax for SRC_URI append

[Alexander Kanavin]

On Mon, 31 Oct 2022 at 22:09, Peter Bergin  wrote:
>
> In order to be able to override the git repo used in a bbappend
> file the additions of files to SRC_URI needs to be done with :append
> instead of +=, otherwise those will not be added.
>
> My use case for this change is to try to build latest
> systemd that is located in another repo than the one used
> by the recipe (systemd.git instead of systemd-stable.git).
> With this change this is possible to do by having SRC_URI, SRCREV
> and SRCBRANCH in a bbappend.

Sorry but overriding these three things in a bbappend is a horrible
idea, and should not be done. Copy and tweak the whole recipe please.

Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172338): 
https://lists.openembedded.org/g/openembedded-core/message/172338
Mute This Topic: https://lists.openembedded.org/mt/94696056/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] systemd: change syntax for SRC_URI append

[Peter Bergin]

Hi Alex,

On 2022-10-31 22:24, Alexander Kanavin wrote:

On Mon, 31 Oct 2022 at 22:09, Peter Bergin  wrote:

In order to be able to override the git repo used in a bbappend
file the additions of files to SRC_URI needs to be done with :append
instead of +=, otherwise those will not be added.

My use case for this change is to try to build latest
systemd that is located in another repo than the one used
by the recipe (systemd.git instead of systemd-stable.git).
With this change this is possible to do by having SRC_URI, SRCREV
and SRCBRANCH in a bbappend.

Sorry but overriding these three things in a bbappend is a horrible
idea, and should not be done. Copy and tweak the whole recipe please.


Sure, I can do that. My aim for override those in a bbappend is just for 
development purposes and nothing I plan to use in production or push in 
public. My way of working when I realized this was to build latest 
master of systemd that had a bunch of patches that I would like to test. 
To do that I needed to change git repo to systemd.git. When tested I 
plan to backport relevant patches that I need to add to current systemd 
version in oe-core to my local layer until next systemd release. Then I 
thought this could simplify things for more people. But I'm fine if this 
is not accepted for upstream and I can work around that.


Best regards,
/Peter



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172339): 
https://lists.openembedded.org/g/openembedded-core/message/172339
Mute This Topic: https://lists.openembedded.org/mt/94696056/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] bluez5: Point hciattach bcm43xx firmware search path to /lib/firmware

[Marek Vasut]

On 10/31/22 20:18, Jose Quaresma wrote:

Hi Marek,


Hi,


Marek Vasut  escreveu no dia segunda, 31/10/2022 à(s) 16:30:


Currently the hciattach bcm43xx firmware loader looks up the firmware
blob in /etc/firmware . Change this to /lib/firmware instead, so that
the path is consistent with Linux kernel which also looks up firmware
for the WiFi part in /lib/firmware .

Signed-off-by: Marek Vasut 
---
Cc: Alexander Kanavin 
Cc: Alexandre Belloni 
Cc: Richard Purdie 
---
  meta/recipes-connectivity/bluez5/bluez5.inc | 2 ++
  1 file changed, 2 insertions(+)

diff --git a/meta/recipes-connectivity/bluez5/bluez5.inc
b/meta/recipes-connectivity/bluez5/bluez5.inc
index f07e318897..fe10be7324 100644
--- a/meta/recipes-connectivity/bluez5/bluez5.inc
+++ b/meta/recipes-connectivity/bluez5/bluez5.inc
@@ -68,6 +68,8 @@ EXTRA_OECONF = "\
--without-zsh-completion-dir \
  "

+CFLAGS:append = " -DFIRMWARE_DIR=\\"/lib/firmware\\""



Escape chars can be tricky when parsing and as the path
doesn't have any space we can have " -DFIRMWARE_DIR=/lib/firmware"
or not?


No, because then the macro gets expanded in place in hciconfig_bcm43xx.c 
to something like printf(/lib/firmware); which the compiler does not 
like obviously. The quotes are really mandatory there, I tried various 
combinations (sigh) until I arrived at this working one.



Another options to avoid escape chars can be
CFLAGS:append = ' -DFIRMWARE_DIR="/lib/firmware"'


[...]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172340): 
https://lists.openembedded.org/g/openembedded-core/message/172340
Mute This Topic: https://lists.openembedded.org/mt/94689423/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] [dunfell][PATCH] xserver-xorg: backport fixes for CVE-2022-3550, CVE-2022-3551 and CVE-2022-3553

[Steve Sakoman]

On Sun, Oct 30, 2022 at 3:39 AM Minjae Kim  wrote:
>
> From: Steve Sakoman 

This seems to be in error since I didn't author this patch ;-)
>
> 
> xkb: proof GetCountedString against request length attacks
> pstream-Status: Backport 
> [https://cgit.freedesktop.org/xorg/xserver/commit/?id=11beef0b7f1ed290348e45618e5fa0d2bffcb72e]
>
> 
> xkb: fix some possible memleaks in XkbGetKbdByName
> Upstream-Status: Backport 
> [https://cgit.freedesktop.org/xorg/xserver/commit/?id=18f91b950e22c2a342a4fbc55e9ddf7534a707d2]
>
> 
> xquartz: Fix a possible crash when editing the Application
> menu due to mutaing immutable arrays
> Upstream-Status: 
> Backport[https://cgit.freedesktop.org/xorg/xserver/commit/?id=dfd057996b26420309c324ec844a5ba6dd07eda3]
>
> Signed-off-by:Minjae Kim 
> ---
>  .../xserver-xorg/CVE-2022-3550.patch  | 34 +++
>  .../xserver-xorg/CVE-2022-3551.patch  | 60 +++
>  .../xserver-xorg/CVE-2022-3553.patch  | 44 ++

All three of the patches are missing the CVE: and UpstreamStatus: tags
as well as your Signed-off-by:

Please submit a V2 with these issues fixed.

Many thanks for your help with CVEs!

Steve

>  .../xorg-xserver/xserver-xorg_1.20.14.bb  |  3 +
>  4 files changed, 141 insertions(+)
>  create mode 100644 
> meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2022-3550.patch
>  create mode 100644 
> meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2022-3551.patch
>  create mode 100644 
> meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2022-3553.patch
>
> diff --git 
> a/meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2022-3550.patch 
> b/meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2022-3550.patch
> new file mode 100644
> index 00..c1241f6ac5
> --- /dev/null
> +++ b/meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2022-3550.patch
> @@ -0,0 +1,34 @@
> +From 27963f7eb6d986f20c88daa40af39834ee9cf9ec Mon Sep 17 00:00:00 2001
> +From: Peter Hutterer 
> +Date: Sun, 30 Oct 2022 13:02:46 +
> +Subject: [PATCH] xkb: proof GetCountedString against request length attacks
> +
> +GetCountedString did a check for the whole string to be within the
> +request buffer but not for the initial 2 bytes that contain the length
> +field. A swapped client could send a malformed request to trigger a
> +swaps() on those bytes, writing into random memory.
> +
> +Signed-off-by: Peter Hutterer 
> +---
> + xkb/xkb.c | 5 +
> + 1 file changed, 5 insertions(+)
> +
> +diff --git a/xkb/xkb.c b/xkb/xkb.c
> +index 68c59df..c9726bc 100644
> +--- a/xkb/xkb.c
>  b/xkb/xkb.c
> +@@ -5138,6 +5138,11 @@ _GetCountedString(char **wire_inout, ClientPtr 
> client, char **str)
> + CARD16 len;
> +
> + wire = *wire_inout;
> ++
> ++if (client->req_len <
> ++bytes_to_int32(wire + 2 - (char *) client->requestBuffer))
> ++return BadValue;
> ++
> + len = *(CARD16 *) wire;
> + if (client->swapped) {
> + swaps(&len);
> +--
> +2.17.1
> +
> diff --git 
> a/meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2022-3551.patch 
> b/meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2022-3551.patch
> new file mode 100644
> index 00..365b11ea1c
> --- /dev/null
> +++ b/meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2022-3551.patch
> @@ -0,0 +1,60 @@
> +From a13cd058d30f30537f7e68b934238fab20f6d55a Mon Sep 17 00:00:00 2001
> +From: Peter Hutterer 
> +Date: Sun, 30 Oct 2022 13:09:00 +
> +Subject: [PATCH] xkb: fix some possible memleaks in XkbGetKbdByName
> +
> +GetComponentByName returns an allocated string, so let's free that if we
> +fail somewhere.
> +
> +Signed-off-by: Peter Hutterer 
> +---
> + xkb/xkb.c | 27 ---
> + 1 file changed, 20 insertions(+), 7 deletions(-)
> +
> +diff --git a/xkb/xkb.c b/xkb/xkb.c
> +index c9726bc..072c138 100644
> +--- a/xkb/xkb.c
>  b/xkb/xkb.c
> +@@ -5908,19 +5908,32 @@ ProcXkbGetKbdByName(ClientPtr client)
> + xkb = dev->key->xkbInfo->desc;
> + status = Success;
> + str = (unsigned char *) &stuff[1];
> +-if (GetComponentSpec(&str, TRUE, &status))  /* keymap, unsupported */
> +-return BadMatch;
> ++{
> ++char *keymap = GetComponentSpec(&str, TRUE, &status);  /* keymap, 
> unsupported */
> ++if (keymap) {
> ++free(keymap);
> ++return BadMatch;
> ++}
> ++}
> + names.keycodes = GetComponentSpec(&str, TRUE, &status);
> + names.types = GetComponentSpec(&str, TRUE, &status);
> + names.compat = GetComponentSpec(&str, TRUE, &status);
> + names.symbols = GetComponentSpec(&str, TRUE, &status);
> + names.geometry = GetComponentSpec(&str, TRUE, &status);
> +-if (status != Success)
> +-return status;
> +-len = str - ((unsigned char *) stuff);
> +-if ((XkbPaddedSize(len) / 4) != stuff->length)
> +-return BadLength;
> ++if (status == Success) {
> ++len = str - ((unsigned char *) stuff);
> ++if ((XkbPaddedS

Re: [OE-core] [PATCH] systemd: change syntax for SRC_URI append

[Alexander Kanavin]

On Mon, 31 Oct 2022 at 22:32, Peter Bergin  wrote:
> Sure, I can do that. My aim for override those in a bbappend is just for
> development purposes and nothing I plan to use in production or push in
> public. My way of working when I realized this was to build latest
> master of systemd that had a bunch of patches that I would like to test.
> To do that I needed to change git repo to systemd.git. When tested I
> plan to backport relevant patches that I need to add to current systemd
> version in oe-core to my local layer until next systemd release. Then I
> thought this could simplify things for more people. But I'm fine if this
> is not accepted for upstream and I can work around that.

We had a related discussion recently regarding mesa, where there is a
similar desire to 'reuse' the recipe from core as much as possible but
build from a different revision. Typically this would be done by
having some kind of common .inc file (systemd.inc in this case), and
then adding the missing parts in a custom .bb that includes the .inc
across layers (bitbake allows this). No promises about keeping things
in .inc compatible with whatever happens in custom layers though.

Another option is to use the devupstream class, and there are examples
in oe-core for it. Would that work for you?

Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172342): 
https://lists.openembedded.org/g/openembedded-core/message/172342
Mute This Topic: https://lists.openembedded.org/mt/94696056/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 12/13] go: submit patch upstream

[Richard Purdie]

On Mon, 2022-10-31 at 12:47 +0100, Alexander Kanavin wrote:
> Note: it will not be reviewed until RP signs the google CLA
> (link in the PR).
> 
> Signed-off-by: Alexander Kanavin 
> ---
>  meta/recipes-devtools/go/go/filter-build-paths.patch | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-devtools/go/go/filter-build-paths.patch 
> b/meta/recipes-devtools/go/go/filter-build-paths.patch
> index a1aa37c2a4..a036f177e0 100644
> --- a/meta/recipes-devtools/go/go/filter-build-paths.patch
> +++ b/meta/recipes-devtools/go/go/filter-build-paths.patch
> @@ -8,7 +8,9 @@ embedded in the go binary so that builds are reproducible 
> regardless of build
>  location. This codepath is hit for statically linked go binaries such as 
> those
>  on mips/ppc.
>  
> -Upstream-Status: Pending
> +Upstream-Status: Submitted [https://github.com/golang/go/pull/56410]
> +Note: RP needs to sign Google CLA for the PR to proceed.
> +

I did sort that, I'm not sure I quite wanted to get into a larger
discussion on how to do it properly and to rewrite the patch and run
more tests though...

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172343): 
https://lists.openembedded.org/g/openembedded-core/message/172343
Mute This Topic: https://lists.openembedded.org/mt/94683163/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 1/3] kernel: classes: Extract savedefconfig to a class

[Ross Burton]

On 12 Oct 2022, at 20:43, Alex Kiernan via lists.openembedded.org 
 wrote:
> 
> On Wed, Oct 12, 2022 at 5:36 PM Ross Burton  wrote:
>> 
>> On 12 Oct 2022, at 08:18, Alex Kiernan via lists.openembedded.org 
>>  wrote:
>>> 
>>> Move savedefconfig task to a class so we can reuse it in other recipes
>>> which support it.
>> 
>> There are three users of cml1 in oe-core: kernel, uboot, and busybox.  Does 
>> busybox support savedefconfig?
>> 
> 
> It doesn't and fairly obviously goes boom…

If you really keen you could see if savedefconfig is a valid target somehow 
(search make -p for savedefconfig?), but to be honest given Ulrich’s reply I’m 
fine with the cml1 class supporting a function that most implementations, if 
not all, support.

It seems preferable to a class which is just "oe_runmake savedefconfig”, at 
least.

Ross


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172344): 
https://lists.openembedded.org/g/openembedded-core/message/172344
Mute This Topic: https://lists.openembedded.org/mt/94276340/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 12/13] go: submit patch upstream

[Alexander Kanavin]

On Mon, 31 Oct 2022 at 22:55, Richard Purdie
 wrote:

> I did sort that, I'm not sure I quite wanted to get into a larger
> discussion on how to do it properly and to rewrite the patch and run
> more tests though...

I wasn't inspired by those review comments either, perhaps we can
convince upstream to take the existing patch as a 'bug report' and
leave the actual fix to them.

Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172345): 
https://lists.openembedded.org/g/openembedded-core/message/172345
Mute This Topic: https://lists.openembedded.org/mt/94683163/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] bluez5: Point hciattach bcm43xx firmware search path to /lib/firmware

[Peter Kjellerstedt]

> -Original Message-
> From: openembedded-core@lists.openembedded.org  c...@lists.openembedded.org> On Behalf Of Marek Vasut
> Sent: den 31 oktober 2022 21:54
> To: Jose Quaresma 
> Cc: openembedded-core@lists.openembedded.org; Alexander Kanavin
> ; Alexandre Belloni ;
> Richard Purdie 
> Subject: Re: [OE-core] [PATCH] bluez5: Point hciattach bcm43xx firmware
> search path to /lib/firmware
> 
> On 10/31/22 20:18, Jose Quaresma wrote:
> > Hi Marek,
> 
> Hi,
> 
> > Marek Vasut  escreveu no dia segunda, 31/10/2022 à(s)
> 16:30:
> >
> >> Currently the hciattach bcm43xx firmware loader looks up the firmware
> >> blob in /etc/firmware . Change this to /lib/firmware instead, so that
> >> the path is consistent with Linux kernel which also looks up firmware
> >> for the WiFi part in /lib/firmware .
> >>
> >> Signed-off-by: Marek Vasut 
> >> ---
> >> Cc: Alexander Kanavin 
> >> Cc: Alexandre Belloni 
> >> Cc: Richard Purdie 
> >> ---
> >>   meta/recipes-connectivity/bluez5/bluez5.inc | 2 ++
> >>   1 file changed, 2 insertions(+)
> >>
> >> diff --git a/meta/recipes-connectivity/bluez5/bluez5.inc
> >> b/meta/recipes-connectivity/bluez5/bluez5.inc
> >> index f07e318897..fe10be7324 100644
> >> --- a/meta/recipes-connectivity/bluez5/bluez5.inc
> >> +++ b/meta/recipes-connectivity/bluez5/bluez5.inc
> >> @@ -68,6 +68,8 @@ EXTRA_OECONF = "\
> >> --without-zsh-completion-dir \
> >>   "
> >>
> >> +CFLAGS:append = " -DFIRMWARE_DIR=\\"/lib/firmware\\""
> >>
> >
> > Escape chars can be tricky when parsing and as the path
> > doesn't have any space we can have " -DFIRMWARE_DIR=/lib/firmware"
> > or not?
> 
> No, because then the macro gets expanded in place in hciconfig_bcm43xx.c
> to something like printf(/lib/firmware); which the compiler does not
> like obviously. The quotes are really mandatory there, I tried various
> combinations (sigh) until I arrived at this working one.
> 
> > Another options to avoid escape chars can be
> > CFLAGS:append = ' -DFIRMWARE_DIR="/lib/firmware"'
> 
> [...]

You should change "/lib" to "${nonarch_base_libdir}".

//Peter


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

Re: [meta-oe][oe-core][PATCH V4] bc: Add ptest.

[Yan Xin Kuan]

Got it.
Can be seen in v5.

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

[meta-oe][oe-core][PATCH V5] bc: Add ptest.

[Yan Xin Kuan]

From: Yan Xinkuan 

Add ptest for OSS 'bc' by using 'bc' in the system to do calculation jobs 
according to the .b files from the source file.

Test example as below:
..
.00673400673400673400
“PASS: bc/div.b”
99836408603283573660347145562829683495827909199408566065153345558783\
9427595471.89114392327665123852
“PASS: bc/exp.b”
length(b)= 1406
“PASS: bc/fact.b”
..

If bc runs the .b files and does not crash, it would 'PASS', otherwise 'FAIL'.

Tested in qemux86-64, with kvm enabled, test cost 12 secs, so it should be a 
fast test.

Thanks to Ross Burton and Alexander Kanavin for the professional guidance.

Signed-off-by: Yan Xinkuan 
---
 meta/conf/distro/include/ptest-packagelists.inc | 1 +
 meta/recipes-extended/bc/bc/run-ptest   | 9 +
 meta/recipes-extended/bc/bc_1.07.1.bb   | 9 +++--
 3 files changed, 17 insertions(+), 2 deletions(-)
 create mode 100644 meta/recipes-extended/bc/bc/run-ptest

diff --git a/meta/conf/distro/include/ptest-packagelists.inc 
b/meta/conf/distro/include/ptest-packagelists.inc
index 56088e4e66..32b0e5297a 100644
--- a/meta/conf/distro/include/ptest-packagelists.inc
+++ b/meta/conf/distro/include/ptest-packagelists.inc
@@ -8,6 +8,7 @@ PTESTS_FAST = "\
 apr-ptest \
 apr-util-ptest \
 attr-ptest \
+bc-ptest \
 bluez5-ptest \
 bzip2-ptest \
 diffstat-ptest \
diff --git a/meta/recipes-extended/bc/bc/run-ptest 
b/meta/recipes-extended/bc/bc/run-ptest
new file mode 100644
index 00..66a1b9d708
--- /dev/null
+++ b/meta/recipes-extended/bc/bc/run-ptest
@@ -0,0 +1,9 @@
+#! /bin/sh
+
+for TEST in *.b; do
+   if bc -l $TEST 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172348): 
https://lists.openembedded.org/g/openembedded-core/message/172348
Mute This Topic: https://lists.openembedded.org/mt/94699073/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-Core][master][kirkstone][PATCH V2] rng-tools: Add Arm aarch64 CPU specific configuration to address excessive CPU usage on startup

[Xiangyu Chen]

With the default jitter options aarch64 CPU-based devices typically experience 
continuous
high CPU utilisation for several minutes after rngd starts.

Accoring to the rng-tools issue #150[1] and comments[2],in order to address 
this,
the following configuration changes have been made, those configurations
also can be found on Alpine Linux[3]:

- reduce the number of threads used to 1 in total, rather than 1 per core.
- reduce the buffer size from 16535 to 4133 which reduces the time taken
  to fill the buffer (and so reduces the duration of CPU load).

[1] https://github.com/nhorman/rng-tools/issues/150
[2] https://github.com/nhorman/rng-tools/issues/150#issuecomment-953079212
[3] https://git.alpinelinux.org/aports/tree/main/rng-tools/rngd.confd-arm

Signed-off-by: Xiangyu Chen 
---
Changes in V2:
  *put the aarch64 specific default file in 
meta/recipes-support/rng-tools/rng-tools/aarch64

---
 .../rng-tools/rng-tools/aarch64/default   | 11 +++
 1 file changed, 11 insertions(+)
 create mode 100644 meta/recipes-support/rng-tools/rng-tools/aarch64/default

diff --git a/meta/recipes-support/rng-tools/rng-tools/aarch64/default 
b/meta/recipes-support/rng-tools/rng-tools/aarch64/default
new file mode 100644
index 00..5a2fbcc9ef
--- /dev/null
+++ b/meta/recipes-support/rng-tools/rng-tools/aarch64/default
@@ -0,0 +1,11 @@
+# With the default jitter options Arm CPU-based devices typically experience
+# continuous high CPU utilisation for several minutes after rngd starts.
+# See https://gitlab.alpinelinux.org/alpine/aports/-/issues/13035 and
+# https://github.com/nhorman/rng-tools/issues/150
+# In order to address this the following configuration changes have been made:
+#
+#   - reduce the number of threads used to 1 in total, rather than 1 per core.
+#   - reduce the buffer size from 16535 to 4133 which reduces the time taken
+# to fill the buffer (and so reduces the duration of CPU load).
+#
+EXTRA_ARGS="-r /dev/hwrng -O jitter:buffer_size:4133 -O 
jitter:refill_thresh:4133 -O jitter:thread_count:1"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172349): 
https://lists.openembedded.org/g/openembedded-core/message/172349
Mute This Topic: https://lists.openembedded.org/mt/94701000/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][kirkstone][master][PATCH] rng-tools: Add Arm aarch64 CPU specific configuration to address excessive CPU usage on startup

[Xiangyu Chen]

On 10/31/22 23:40, Khem Raj wrote:

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

On Mon, Oct 31, 2022 at 12:51 AM Xiangyu Chen
 wrote:

With the default jitter options aarch64 CPU-based devices typically experience 
continuous
high CPU utilisation for several minutes after rngd starts.

Accoring to the rng-tools issue #150[1] and comments[2],in order to address 
this,
the following configuration changes have been made, those configurations
also can be found on Alpine Linux[3]:

- reduce the number of threads used to 1 in total, rather than 1 per core.
- reduce the buffer size from 16535 to 4133 which reduces the time taken
   to fill the buffer (and so reduces the duration of CPU load).

[1] https://github.com/nhorman/rng-tools/issues/150
[2] https://github.com/nhorman/rng-tools/issues/150#issuecomment-953079212
[3] https://git.alpinelinux.org/aports/tree/main/rng-tools/rngd.confd-arm

Signed-off-by: Xiangyu Chen 
---
  .../rng-tools/rng-tools/default.aarch64   | 11 +++
  meta/recipes-support/rng-tools/rng-tools_6.15.bb  |  5 +
  2 files changed, 16 insertions(+)
  create mode 100644 meta/recipes-support/rng-tools/rng-tools/default.aarch64

diff --git a/meta/recipes-support/rng-tools/rng-tools/default.aarch64 
b/meta/recipes-support/rng-tools/rng-tools/default.aarch64
new file mode 100644
index 00..5a2fbcc9ef
--- /dev/null
+++ b/meta/recipes-support/rng-tools/rng-tools/default.aarch64
@@ -0,0 +1,11 @@
+# With the default jitter options Arm CPU-based devices typically experience
+# continuous high CPU utilisation for several minutes after rngd starts.
+# See https://gitlab.alpinelinux.org/alpine/aports/-/issues/13035 and
+# https://github.com/nhorman/rng-tools/issues/150
+# In order to address this the following configuration changes have been made:
+#
+#   - reduce the number of threads used to 1 in total, rather than 1 per core.
+#   - reduce the buffer size from 16535 to 4133 which reduces the time taken
+# to fill the buffer (and so reduces the duration of CPU load).
+#
+EXTRA_ARGS="-r /dev/hwrng -O jitter:buffer_size:4133 -O jitter:refill_thresh:4133 
-O jitter:thread_count:1"
diff --git a/meta/recipes-support/rng-tools/rng-tools_6.15.bb 
b/meta/recipes-support/rng-tools/rng-tools_6.15.bb
index 0696351903..e1f6b2ad77 100644
--- a/meta/recipes-support/rng-tools/rng-tools_6.15.bb
+++ b/meta/recipes-support/rng-tools/rng-tools_6.15.bb
@@ -12,6 +12,7 @@ SRC_URI = 
"git://github.com/nhorman/rng-tools.git;branch=master;protocol=https \
 file://init \
 file://default \
 file://rngd.service \
+   file://default.aarch64 \
 "
  SRCREV = "381f69828b782afda574f259c1b7549f48f9bb77"

@@ -59,3 +60,7 @@ do_install:append() {
  ${D}${systemd_system_unitdir}/rngd.service
  fi
  }
+
+do_install:append:aarch64() {
+install -Dm 0644 ${WORKDIR}/default.aarch64 
${D}${sysconfdir}/default/rng-tools
+}

Perhaps drop the aarch64 specific default file inside a folder called
aarch64 under meta/recipes-support/rng-tools/rng-tools
and we don't need any changes in recipe.


Thanks,  already sent the v2 patch.

https://lists.openembedded.org/g/openembedded-core/message/172349


--
2.34.1





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