[OE-core] [PATCH V3] man-pages: remove conflict pages

2023-12-20 Thread Changqing Li
From: Changqing Li 

Remove the pages which libxcrypt and shadow already have to avoid
following conflicts during install man-pages and libxcrypt/shadow at the
same time.

Error: Transaction test error:
  file /usr/share/man/man3/crypt.3 from install of
  libcrypt-doc-4.4.33-r0.x86_64 conflicts with file from package
  man-pages-6.04-r0.x86_64

Signed-off-by: Changqing Li 
---
 .../recipes-extended/man-pages/man-pages_6.05.01.bb | 13 -
 1 file changed, 4 insertions(+), 9 deletions(-)

diff --git a/meta/recipes-extended/man-pages/man-pages_6.05.01.bb 
b/meta/recipes-extended/man-pages/man-pages_6.05.01.bb
index 2726eded8b..f0eb1a6132 100644
--- a/meta/recipes-extended/man-pages/man-pages_6.05.01.bb
+++ b/meta/recipes-extended/man-pages/man-pages_6.05.01.bb
@@ -30,17 +30,12 @@ do_compile[noexec] = "1"
 
 do_install() {
 oe_runmake install prefix=${prefix} DESTDIR=${D}
+rm -rf ${D}${mandir}/man3/crypt.3
+rm -rf ${D}${mandir}/man3/crypt_r.3
+rm -rf ${D}${mandir}/man3/getspnam.3
+rm -rf ${D}${mandir}/man5/passwd.5
 }
 
 # Only deliveres man-pages so FILES:${PN} gets everything
 FILES:${PN}-doc = ""
 FILES:${PN} = "${mandir}/*"
-
-inherit update-alternatives
-
-ALTERNATIVE_PRIORITY = "100"
-ALTERNATIVE:${PN} = "crypt.3 crypt_r.3 getspnam.3 passwd.5"
-ALTERNATIVE_LINK_NAME[crypt.3] = "${mandir}/man3/crypt.3"
-ALTERNATIVE_LINK_NAME[crypt_r.3] = "${mandir}/man3/crypt_r.3"
-ALTERNATIVE_LINK_NAME[getspnam.3] = "${mandir}/man3/getspnam.3"
-ALTERNATIVE_LINK_NAME[passwd.5] = "${mandir}/man5/passwd.5"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192826): 
https://lists.openembedded.org/g/openembedded-core/message/192826
Mute This Topic: https://lists.openembedded.org/mt/103295823/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] libxcrypt.inc: use alternatives to resolve crypt.3 conflict

2023-12-20 Thread Changqing Li


On 12/19/23 16:29, Richard Purdie wrote:

CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know 
the content is safe.

On Tue, 2023-12-19 at 12:07 +0800, Changqing Li wrote:

Kindly ping


And why have this change:

In old version of man-pages's README,  it mentioned:

Note that sometimes these pages are duplicates of pages also distributed
in other
packages. Be careful not to overwrite more up-to-date versions.

So we set man-pages to lower priority,  so the doc in the related
packages are used.


And if we delete them from man-pages recipes, it will make man-pages
missing these docs

when eg: libcrypt-doc is not installed.

in man-pages recipe, ALTERNATIVE_PRIORITY set to 100. So I send an V2 to
update

ALTERNATIVE_PRIORITY of libcrypt-doc to 200.

Please delete the version from man-pages. Those are only added there if
the upstream doesn't have a man page. libxcrypt does now have this so
the doc isn't needed from there.


Thanks for explaining this,   V3 is sent.

Regards

Changqing


I suspect a future version of man-pages will do this anyway.

Cheers,

Richard





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



Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-5.0_M1.rc3)

2023-12-20 Thread Jing Hui Tham
Hi all,
 
Intel and WR YP QA is planning for QA execution for YP build yocto-5.0_M1.rc3. 
We are planning to execute following tests for this cycle:
 
OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw
 
Runtime auto test for following platforms:
1. MinnowBoard Turbot - 32bit
2. Kaby Lake (7th Generation Intel(r) Core(tm) Processors)
3. Tiger Lake (11th Generation Intel(r) Core(tm) Processors)
4. Alder Lake-S (12th Generation Intel(r) Core(tm) Processors)
5. Raptor Lake-P (13th Generation Intel(r) Core(tm) Processors)
6. Beaglebone

 
ETA for completion next Wednesday, 27 December.
 
Best regards,
Jing Hui


> -Original Message-
> From: qa-build-notificat...@lists.yoctoproject.org  notificat...@lists.yoctoproject.org> On Behalf Of Pokybuild User
> Sent: Monday, December 18, 2023 10:43 PM
> To: yo...@lists.yoctoproject.org
> Cc: qa-build-notificat...@lists.yoctoproject.org
> Subject: [qa-build-notification] QA notification for completed autobuilder
> build (yocto-5.0_M1.rc3)
> 
> 
> A build flagged for QA (yocto-5.0_M1.rc3) was completed on the
> autobuilder and is available at:
> 
> 
> https://autobuilder.yocto.io/pub/releases/yocto-5.0_M1.rc3
> 
> 
> Build URL:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6345
> 
> Build hash information:
> 
> bitbake: 8295ac1b6672c25bee595cff6e000b2af817f904
> meta-agl: 266ac5373b4458d7fcb78b1e8948eb2b33f18b5d
> meta-arm: e6e7ac4d99f103d26a0ffefd6d0a5d2deef5b17c
> meta-aws: 7915e6bafd876ab3d654a26629dbf501479caae0
> meta-intel: 5cfefd9a8ff1f5a3534c1ba9d7d7f6971ed5d56f
> meta-mingw: e01d47d183945caeaf3c5c086539af0a925ddc32
> meta-openembedded: 0a0ea87b8dda01a2887a525cef78eb6c3f4c2c32
> meta-virtualization: caa14c63f158fdd13382ccf1ff4e20a8ba6ad667
> oecore: 6b729088dce302eb3a967cb6839f00488025be0e
> poky: 33112178d164ddd9ef0b1115c254ad4341ec3ad1
> 
> 
> 
> This is an automated message from the Yocto Project Autobuilder
> Git: git://git.yoctoproject.org/yocto-autobuilder2
> Email: richard.pur...@linuxfoundation.org
> 
> 
> 
> 
> 
> 
> 


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



[OE-core][kirkstone 11/11] testimage: Exclude wtmp from target-dumper commands

2023-12-20 Thread Steve Sakoman
From: Richard Purdie 

wtmp is filled with binary data which the run_serial command can't cope with.
Catting this results in confusion of the serial interface and potentially large
backlogs of data in the buffers which can hang qemu.

Exclude the problematic files from the command.

Signed-off-by: Richard Purdie 
(cherry picked from commit 599ac08a6f6fb3f6a89a897c8e06367c63c2f979)
Signed-off-by: Steve Sakoman 
---
 meta/classes/testimage.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/testimage.bbclass b/meta/classes/testimage.bbclass
index 34173ce68d..6864eeed2f 100644
--- a/meta/classes/testimage.bbclass
+++ b/meta/classes/testimage.bbclass
@@ -112,7 +112,7 @@ testimage_dump_target () {
 netstat -an
 ip address
 # Next command will dump logs from /var/log/
-find /var/log/ -type f 2>/dev/null -exec echo "" \; 
-exec echo {} \; -exec echo "" \; -exec cat {} \; -exec 
echo "" \;
+find /var/log/ -type f -name !wtmp* 2>/dev/null -exec echo 
"" \; -exec echo {} \; -exec echo "" \; 
-exec cat {} \; -exec echo "" \;
 }
 
 testimage_dump_host () {
-- 
2.34.1


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



[OE-core][kirkstone 10/11] python3-ptest: skip test_storlines

2023-12-20 Thread Steve Sakoman
From: Trevor Gamblin 

[YOCTO #14933]

test_storlines is yet another Python ptest that fails intermittently on
the Yocto AB, so disable it during ptests for now.

Signed-off-by: Trevor Gamblin 
Signed-off-by: Alexandre Belloni 
(cherry picked from commit d7b9f8157e6214a83b5495e8a32e11540ae65ff8)
Signed-off-by: Steve Sakoman 
---
 ...orlines-skip-due-to-load-variability.patch | 32 +++
 .../python/python3_3.10.13.bb |  1 +
 2 files changed, 33 insertions(+)
 create mode 100644 
meta/recipes-devtools/python/python3/0001-test_storlines-skip-due-to-load-variability.patch

diff --git 
a/meta/recipes-devtools/python/python3/0001-test_storlines-skip-due-to-load-variability.patch
 
b/meta/recipes-devtools/python/python3/0001-test_storlines-skip-due-to-load-variability.patch
new file mode 100644
index 00..199031d42a
--- /dev/null
+++ 
b/meta/recipes-devtools/python/python3/0001-test_storlines-skip-due-to-load-variability.patch
@@ -0,0 +1,32 @@
+From 013ff01fdf2aa6ca69a7c80a2a2996630877e4ea Mon Sep 17 00:00:00 2001
+From: Trevor Gamblin 
+Date: Fri, 6 Oct 2023 10:59:44 -0400
+Subject: [PATCH] test_storlines: skip due to load variability
+
+This is yet another test that intermittently fails on the Yocto AB when
+a worker is under heavy load, so skip it during testing.
+
+Upstream-Status: Inappropriate [OE-Specific]
+
+[YOCTO #14933]
+
+Signed-off-by: Trevor Gamblin 
+---
+ Lib/test/test_ftplib.py | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/Lib/test/test_ftplib.py b/Lib/test/test_ftplib.py
+index 082a90d46b..508814d56a 100644
+--- a/Lib/test/test_ftplib.py
 b/Lib/test/test_ftplib.py
+@@ -629,6 +629,7 @@ def test_storbinary_rest(self):
+ self.client.storbinary('stor', f, rest=r)
+ self.assertEqual(self.server.handler_instance.rest, str(r))
+ 
++@unittest.skip('timing related test, dependent on load')
+ def test_storlines(self):
+ data = RETR_DATA.replace('\r\n', '\n').encode(self.client.encoding)
+ f = io.BytesIO(data)
+-- 
+2.41.0
+
diff --git a/meta/recipes-devtools/python/python3_3.10.13.bb 
b/meta/recipes-devtools/python/python3_3.10.13.bb
index ba53a09ef5..76e37e42a1 100644
--- a/meta/recipes-devtools/python/python3_3.10.13.bb
+++ b/meta/recipes-devtools/python/python3_3.10.13.bb
@@ -35,6 +35,7 @@ SRC_URI = 
"http://www.python.org/ftp/python/${PV}/Python-${PV}.tar.xz \

file://0001-setup.py-Do-not-detect-multiarch-paths-when-cross-co.patch \
file://deterministic_imports.patch \
file://0001-Avoid-shebang-overflow-on-python-config.py.patch \
+   file://0001-test_storlines-skip-due-to-load-variability.patch \
"
 
 SRC_URI:append:class-native = " \
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192822): 
https://lists.openembedded.org/g/openembedded-core/message/192822
Mute This Topic: https://lists.openembedded.org/mt/103293619/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 09/11] externalsrc: Ensure SRCREV is processed before accessing SRC_URI

2023-12-20 Thread Steve Sakoman
From: Yoann Congal 

When SRCREV is used, call bb.fetch.get_srcrev() before accessing
SRC_URI. Without this new bb.fetch.get_srcrev() call, SRC_URI might be
accessed before SRCREV had a chance to be processed.

In master, this is fixed by 
https://git.yoctoproject.org/poky/commit/?id=62afa02d01794376efab75623f42e7e08af08526
However, this commit is not suited for backport since it is quite invasive.
The part of the commit that fix the bug is:
--- a/meta/classes/externalsrc.bbclass
+++ b/meta/classes/externalsrc.bbclass
@@ -63,6 +63,7 @@ python () {
 else:
 d.setVar('B', '${WORKDIR}/${BPN}-${PV}')

+bb.fetch.get_hashvalue(d)
 local_srcuri = []
 fetch = bb.fetch2.Fetch((d.getVar('SRC_URI') or '').split(), d)
 for url in fetch.urls:

NB: bb.fetch.get_hashvalue() does not exist in kirkstone but is
equivalent to bb.fetch.get_srcrev().

Fixes [YOCTO #14918]

Signed-off-by: Yoann Congal 
Suggested-by: Chris Wyse 
Signed-off-by: Steve Sakoman 
---
 meta/classes/externalsrc.bbclass | 4 
 1 file changed, 4 insertions(+)

diff --git a/meta/classes/externalsrc.bbclass b/meta/classes/externalsrc.bbclass
index 97d7379d9f..a209730240 100644
--- a/meta/classes/externalsrc.bbclass
+++ b/meta/classes/externalsrc.bbclass
@@ -62,6 +62,10 @@ python () {
 else:
 d.setVar('B', '${WORKDIR}/${BPN}-${PV}')
 
+if d.getVar('SRCREV', "INVALID") != "INVALID":
+# Ensure SRCREV has been processed before accessing SRC_URI
+bb.fetch.get_srcrev(d)
+
 local_srcuri = []
 fetch = bb.fetch2.Fetch((d.getVar('SRC_URI') or '').split(), d)
 for url in fetch.urls:
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192821): 
https://lists.openembedded.org/g/openembedded-core/message/192821
Mute This Topic: https://lists.openembedded.org/mt/103293618/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 08/11] perl: update 5.34.1 -> 5.34.3

2023-12-20 Thread Steve Sakoman
From: Soumya Sambu 

This includes security fix for CVE-2023-47038

Changes:
https://metacpan.org/release/PEVANS/perl-5.34.3/changes

Signed-off-by: Soumya Sambu 
Signed-off-by: Steve Sakoman 
---
 .../0001-Makefile-check-the-file-if-patched-or-not.patch  | 4 ++--
 .../perl-cross/{perlcross_1.3.7.bb => perlcross_1.5.2.bb} | 2 +-
 meta/recipes-devtools/perl/{perl_5.34.1.bb => perl_5.34.3.bb} | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)
 rename meta/recipes-devtools/perl-cross/{perlcross_1.3.7.bb => 
perlcross_1.5.2.bb} (92%)
 rename meta/recipes-devtools/perl/{perl_5.34.1.bb => perl_5.34.3.bb} (99%)

diff --git 
a/meta/recipes-devtools/perl-cross/files/0001-Makefile-check-the-file-if-patched-or-not.patch
 
b/meta/recipes-devtools/perl-cross/files/0001-Makefile-check-the-file-if-patched-or-not.patch
index 8c8f3b717c..0ef9b27439 100644
--- 
a/meta/recipes-devtools/perl-cross/files/0001-Makefile-check-the-file-if-patched-or-not.patch
+++ 
b/meta/recipes-devtools/perl-cross/files/0001-Makefile-check-the-file-if-patched-or-not.patch
@@ -21,8 +21,8 @@ index f4a26f5..7bc748e 100644
  # Original versions are not saved anymore; patch generally takes care of this,
  # and if that fails, reaching for the source tarball is the safest option.
  $(CROSSPATCHED): %.applied: %.patch
--  patch -p1 -i $< && touch $@
-+  test ! -f $@ && (patch -p1 -i $< && touch $@) || echo "$@ exist"
+-  $(cpatch) -p1 -i $< && touch $@
++  test ! -f $@ && ($(cpatch) -p1 -i $< && touch $@) || echo "$@ exist"
  
  # ---[ common 
]-
  
diff --git a/meta/recipes-devtools/perl-cross/perlcross_1.3.7.bb 
b/meta/recipes-devtools/perl-cross/perlcross_1.5.2.bb
similarity index 92%
rename from meta/recipes-devtools/perl-cross/perlcross_1.3.7.bb
rename to meta/recipes-devtools/perl-cross/perlcross_1.5.2.bb
index 99a9ca1027..ac4dff33bb 100644
--- a/meta/recipes-devtools/perl-cross/perlcross_1.3.7.bb
+++ b/meta/recipes-devtools/perl-cross/perlcross_1.5.2.bb
@@ -18,7 +18,7 @@ SRC_URI = 
"https://github.com/arsv/perl-cross/releases/download/${PV}/perl-cross
"
 UPSTREAM_CHECK_URI = "https://github.com/arsv/perl-cross/releases/;
 
-SRC_URI[perl-cross.sha256sum] = 
"77f13ca84a63025053852331b72d4046c1f90ded98bd45ccedea738621907335"
+SRC_URI[perl-cross.sha256sum] = 
"584dc54c48dca25e032b676a15bef377c1fed9de318b4fc140292a5dbf326e90"
 
 S = "${WORKDIR}/perl-cross-${PV}"
 
diff --git a/meta/recipes-devtools/perl/perl_5.34.1.bb 
b/meta/recipes-devtools/perl/perl_5.34.3.bb
similarity index 99%
rename from meta/recipes-devtools/perl/perl_5.34.1.bb
rename to meta/recipes-devtools/perl/perl_5.34.3.bb
index db306d0be3..e8b518adc9 100644
--- a/meta/recipes-devtools/perl/perl_5.34.1.bb
+++ b/meta/recipes-devtools/perl/perl_5.34.3.bb
@@ -29,7 +29,7 @@ SRC_URI:append:class-target = " \
file://encodefix.patch \
 "
 
-SRC_URI[perl.sha256sum] = 
"357951a491b0ba1ce3611263922feec78ccd581dddc24a446b033e25acf242a1"
+SRC_URI[perl.sha256sum] = 
"5b12f62863332b2a5f54102af9cdf8c010877e4bf3294911edbd594b2a1e8ede"
 
 S = "${WORKDIR}/perl-${PV}"
 
-- 
2.34.1


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



[OE-core][kirkstone 06/11] go: Fix CVE-2023-39326

2023-12-20 Thread Steve Sakoman
From: Soumya Sambu 

A malicious HTTP sender can use chunk extensions to cause a receiver
reading from a request or response body to read many more bytes from
the network than are in the body. A malicious HTTP client can further
exploit this to cause a server to automatically read a large amount
of data (up to about 1GiB) when a handler fails to read the entire
body of a request. Chunk extensions are a little-used HTTP feature
which permit including additional metadata in a request or response
body sent using the chunked encoding. The net/http chunked encoding
reader discards this metadata. A sender can exploit this by inserting
a large metadata segment with each byte transferred. The chunk reader
now produces an error if the ratio of real body to encoded bytes grows
too small.

References:
https://nvd.nist.gov/vuln/detail/CVE-2023-39326
https://security-tracker.debian.org/tracker/CVE-2023-39326

Signed-off-by: Soumya Sambu 
Signed-off-by: Steve Sakoman 
---
 meta/recipes-devtools/go/go-1.17.13.inc   |   1 +
 .../go/go-1.20/CVE-2023-39326.patch   | 182 ++
 2 files changed, 183 insertions(+)
 create mode 100644 meta/recipes-devtools/go/go-1.20/CVE-2023-39326.patch

diff --git a/meta/recipes-devtools/go/go-1.17.13.inc 
b/meta/recipes-devtools/go/go-1.17.13.inc
index 330f571d22..95c4461d3e 100644
--- a/meta/recipes-devtools/go/go-1.17.13.inc
+++ b/meta/recipes-devtools/go/go-1.17.13.inc
@@ -47,6 +47,7 @@ SRC_URI += "\
 file://CVE-2023-29409.patch \
 file://CVE-2023-39319.patch \
 file://CVE-2023-39318.patch \
+file://CVE-2023-39326.patch \
 "
 SRC_URI[main.sha256sum] = 
"a1a48b23afb206f95e7bbaa9b898d965f90826f6f1d1fc0c1d784ada0cd300fd"
 
diff --git a/meta/recipes-devtools/go/go-1.20/CVE-2023-39326.patch 
b/meta/recipes-devtools/go/go-1.20/CVE-2023-39326.patch
new file mode 100644
index 00..ca78e552c2
--- /dev/null
+++ b/meta/recipes-devtools/go/go-1.20/CVE-2023-39326.patch
@@ -0,0 +1,182 @@
+From 6446af942e2e2b161c4ec1b60d9703a2b55dc4dd Mon Sep 17 00:00:00 2001
+From: Damien Neil 
+Date: Tue, 7 Nov 2023 10:47:56 -0800
+Subject: [PATCH] net/http: limit chunked data overhead
+
+The chunked transfer encoding adds some overhead to
+the content transferred. When writing one byte per
+chunk, for example, there are five bytes of overhead
+per byte of data transferred: "1\r\nX\r\n" to send "X".
+
+Chunks may include "chunk extensions",
+which we skip over and do not use.
+For example: "1;chunk extension here\r\nX\r\n".
+
+A malicious sender can use chunk extensions to add
+about 4k of overhead per byte of data.
+(The maximum chunk header line size we will accept.)
+
+Track the amount of overhead read in chunked data,
+and produce an error if it seems excessive.
+
+Updates #64433
+Fixes #64434
+Fixes CVE-2023-39326
+
+Change-Id: I40f8d70eb6f9575fb43f506eb19132ccedafcf39
+Reviewed-on: 
https://team-review.git.corp.google.com/c/golang/go-private/+/2076135
+Reviewed-by: Tatiana Bradley 
+Reviewed-by: Roland Shoemaker 
+(cherry picked from commit 3473ae72ee66c60744665a24b2fde143e8964d4f)
+Reviewed-on: 
https://team-review.git.corp.google.com/c/golang/go-private/+/2095407
+Run-TryBot: Roland Shoemaker 
+TryBot-Result: Security TryBots 

+Reviewed-by: Damien Neil 
+Reviewed-on: https://go-review.googlesource.com/c/go/+/547355
+Reviewed-by: Dmitri Shuralyov 
+LUCI-TryBot-Result: Go LUCI 

+
+CVE: CVE-2023-39326
+
+Upstream-Status: Backport 
[https://github.com/golang/go/commit/6446af942e2e2b161c4ec1b60d9703a2b55dc4dd]
+
+Signed-off-by: Soumya Sambu 
+---
+ src/net/http/internal/chunked.go  | 36 +---
+ src/net/http/internal/chunked_test.go | 59 +++
+ 2 files changed, 89 insertions(+), 6 deletions(-)
+
+diff --git a/src/net/http/internal/chunked.go 
b/src/net/http/internal/chunked.go
+index f06e572..ddbaacb 100644
+--- a/src/net/http/internal/chunked.go
 b/src/net/http/internal/chunked.go
+@@ -39,7 +39,8 @@ type chunkedReader struct {
+   nuint64 // unread bytes in chunk
+   err  error
+   buf  [2]byte
+-  checkEnd bool // whether need to check for \r\n chunk footer
++  checkEnd bool  // whether need to check for \r\n chunk footer
++  excess   int64 // "excessive" chunk overhead, for malicious sender 
detection
+ }
+
+ func (cr *chunkedReader) beginChunk() {
+@@ -49,10 +50,38 @@ func (cr *chunkedReader) beginChunk() {
+   if cr.err != nil {
+   return
+   }
++  cr.excess += int64(len(line)) + 2 // header, plus \r\n after the chunk 
data
++  line = trimTrailingWhitespace(line)
++  line, cr.err = removeChunkExtension(line)
++  if cr.err != nil {
++  return
++  }
+   cr.n, cr.err = parseHexUint(line)
+   if cr.err != nil {
+   return
+   }
++  // A sender who sends one byte per chunk will send 5 bytes of overhead
++  // for every byte of data. ("1\r\nX\r\n" to send "X".)
++  // We want to allow this, since 

[OE-core][kirkstone 07/11] openssh: backport Debian patch for CVE-2023-48795

2023-12-20 Thread Steve Sakoman
From: Vijay Anusuri 

import patches from ubuntu to fix
 fix-authorized-principals-command
 CVE-2023-48795

Upstream-Status: Backport [import from ubuntu 
https://git.launchpad.net/ubuntu/+source/openssh/tree/debian/patches?h=ubuntu/jammy-security
Upstream commit
https://github.com/openssh/openssh-portable/commit/fcd78e31cdd45a7e69ccfe6d8a3b1037dc1de290
&
https://github.com/openssh/openssh-portable/commit/1edb00c58f8a6875fad6a497aa2bacf37f9e6cd5]

Reference: https://ubuntu.com/security/CVE-2023-48795

Signed-off-by: Vijay Anusuri 
Signed-off-by: Steve Sakoman 
---
 .../openssh/openssh/CVE-2023-48795.patch  | 476 ++
 .../fix-authorized-principals-command.patch   |  30 ++
 .../openssh/openssh_8.9p1.bb  |   2 +
 3 files changed, 508 insertions(+)
 create mode 100644 
meta/recipes-connectivity/openssh/openssh/CVE-2023-48795.patch
 create mode 100644 
meta/recipes-connectivity/openssh/openssh/fix-authorized-principals-command.patch

diff --git a/meta/recipes-connectivity/openssh/openssh/CVE-2023-48795.patch 
b/meta/recipes-connectivity/openssh/openssh/CVE-2023-48795.patch
new file mode 100644
index 00..6b2f927779
--- /dev/null
+++ b/meta/recipes-connectivity/openssh/openssh/CVE-2023-48795.patch
@@ -0,0 +1,476 @@
+(modified to not remove ssh_packet_read_expect() and to add to
+KexAlgorithms in sshd.c and sshconnect2.c as this version pre-dates
+kex_proposal_populate_entries())
+
+Backport of:
+
+From 1edb00c58f8a6875fad6a497aa2bacf37f9e6cd5 Mon Sep 17 00:00:00 2001
+From: "d...@openbsd.org" 
+Date: Mon, 18 Dec 2023 14:45:17 +
+Subject: [PATCH] upstream: implement "strict key exchange" in ssh and sshd
+
+This adds a protocol extension to improve the integrity of the SSH
+transport protocol, particular in and around the initial key exchange
+(KEX) phase.
+
+Full details of the extension are in the PROTOCOL file.
+
+with markus@
+
+OpenBSD-Commit-ID: 2a66ac962f0a630d7945fee54004ed9e9c439f14
+
+Upstream-Status: Backport [import from ubuntu 
https://git.launchpad.net/ubuntu/+source/openssh/tree/debian/patches/CVE-2023-48795.patch?h=ubuntu/jammy-security
+Upstream commit 
https://github.com/openssh/openssh-portable/commit/1edb00c58f8a6875fad6a497aa2bacf37f9e6cd5]
+CVE: CVE-2023-48795
+Signed-off-by: Vijay Anusuri 
+---
+ PROTOCOL  | 26 +
+ kex.c | 72 +++
+ kex.h |  1 +
+ packet.c  | 78 ++-
+ sshconnect2.c | 14 +++--
+ sshd.c|  7 +++--
+ 6 files changed, 142 insertions(+), 56 deletions(-)
+
+diff --git a/PROTOCOL b/PROTOCOL
+index e6a7d60..971f01e 100644
+--- a/PROTOCOL
 b/PROTOCOL
+@@ -102,6 +102,32 @@ OpenSSH supports the use of ECDH in Curve25519 for key 
exchange as
+ described at:
+ 
http://git.libssh.org/users/aris/libssh.git/plain/doc/curve25519-sha...@libssh.org.txt?h=curve25519
+ 
++1.9 transport: strict key exchange extension
++
++OpenSSH supports a number of transport-layer hardening measures under
++a "strict KEX" feature. This feature is signalled similarly to the
++RFC8308 ext-info feature: by including a additional algorithm in the
++initiial SSH2_MSG_KEXINIT kex_algorithms field. The client may append
++"kex-strict-c-...@openssh.com" to its kex_algorithms and the server
++may append "kex-strict-s-...@openssh.com". These pseudo-algorithms
++are only valid in the initial SSH2_MSG_KEXINIT and MUST be ignored
++if they are present in subsequent SSH2_MSG_KEXINIT packets.
++
++When an endpoint that supports this extension observes this algorithm
++name in a peer's KEXINIT packet, it MUST make the following changes to
++the the protocol:
++
++a) During initial KEX, terminate the connection if any unexpected or
++   out-of-sequence packet is received. This includes terminating the
++   connection if the first packet received is not SSH2_MSG_KEXINIT.
++   Unexpected packets for the purpose of strict KEX include messages
++   that are otherwise valid at any time during the connection such as
++   SSH2_MSG_DEBUG and SSH2_MSG_IGNORE.
++b) After sending or receiving a SSH2_MSG_NEWKEYS message, reset the
++   packet sequence number to zero. This behaviour persists for the
++   duration of the connection (i.e. not just the first
++   SSH2_MSG_NEWKEYS).
++
+ 2. Connection protocol changes
+ 
+ 2.1. connection: Channel write close extension "e...@openssh.com"
+diff --git a/kex.c b/kex.c
+index 0bcd27d..e7b2d4d 100644
+--- a/kex.c
 b/kex.c
+@@ -63,7 +63,7 @@
+ #include "digest.h"
+ 
+ /* prototype */
+-static int kex_choose_conf(struct ssh *);
++static int kex_choose_conf(struct ssh *, uint32_t seq);
+ static int kex_input_newkeys(int, u_int32_t, struct ssh *);
+ 
+ static const char * const proposal_names[PROPOSAL_MAX] = {
+@@ -175,6 +175,18 @@ kex_names_valid(const char *names)
+   return 1;
+ }
+ 
++/* returns non-zero if proposal contains any algorithm from algs */
++static int
++has_any_alg(const char *proposal, 

[OE-core][kirkstone 05/11] ffmpeg: fix for CVE-2022-3965

2023-12-20 Thread Steve Sakoman
From: "mark.yang" 

Without a CVE tag, It will be recognised as Unpatched by cve_check task.

Signed-off-by: mark.yang 
Signed-off-by: Steve Sakoman 
---
 .../0001-avcodec-smcenc-stop-accessing-out-of-bounds-frame.patch | 1 +
 1 file changed, 1 insertion(+)

diff --git 
a/meta/recipes-multimedia/ffmpeg/ffmpeg/0001-avcodec-smcenc-stop-accessing-out-of-bounds-frame.patch
 
b/meta/recipes-multimedia/ffmpeg/ffmpeg/0001-avcodec-smcenc-stop-accessing-out-of-bounds-frame.patch
index 6e237fdd52..8ebf1f69c4 100644
--- 
a/meta/recipes-multimedia/ffmpeg/ffmpeg/0001-avcodec-smcenc-stop-accessing-out-of-bounds-frame.patch
+++ 
b/meta/recipes-multimedia/ffmpeg/ffmpeg/0001-avcodec-smcenc-stop-accessing-out-of-bounds-frame.patch
@@ -5,6 +5,7 @@ Subject: [PATCH] avcodec/smcenc: stop accessing out of bounds 
frame
 
 Upstream-Status: Backport 
[https://github.com/FFmpeg/FFmpeg/commit/13c13109759090b7f7182480d075e13b36ed8edd]
 
+CVE: CVE-2022-3965
 Signed-off-by: 
 
 ---
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192817): 
https://lists.openembedded.org/g/openembedded-core/message/192817
Mute This Topic: https://lists.openembedded.org/mt/103293613/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 04/11] ffmpeg: fix for CVE-2022-3964

2023-12-20 Thread Steve Sakoman
From: "mark.yang" 

Without a CVE tag, It will be recognised as Unpatched by cve_check task.

Signed-off-by: mark.yang 
Signed-off-by: Steve Sakoman 
---
 ...001-avcodec-rpzaenc-stop-accessing-out-of-bounds-frame.patch | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/meta/recipes-multimedia/ffmpeg/ffmpeg/0001-avcodec-rpzaenc-stop-accessing-out-of-bounds-frame.patch
 
b/meta/recipes-multimedia/ffmpeg/ffmpeg/0001-avcodec-rpzaenc-stop-accessing-out-of-bounds-frame.patch
index 23573bb6b3..97fcfd993a 100644
--- 
a/meta/recipes-multimedia/ffmpeg/ffmpeg/0001-avcodec-rpzaenc-stop-accessing-out-of-bounds-frame.patch
+++ 
b/meta/recipes-multimedia/ffmpeg/ffmpeg/0001-avcodec-rpzaenc-stop-accessing-out-of-bounds-frame.patch
@@ -4,7 +4,7 @@ Date: Sat, 12 Nov 2022 16:12:00 +0100
 Subject: [PATCH] avcodec/rpzaenc: stop accessing out of bounds frame
 
 Upstream-Status: Backport 
[https://github.com/FFmpeg/FFmpeg/commit/92f9b28ed84a77138105475beba16c146bdaf984]
-
+CVE: CVE-2022-3964
 Signed-off-by: 
 
 ---
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192816): 
https://lists.openembedded.org/g/openembedded-core/message/192816
Mute This Topic: https://lists.openembedded.org/mt/103293612/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 03/11] qemu: Fix CVE-2023-5088

2023-12-20 Thread Steve Sakoman
From: Sourav Pramanik 

A bug in QEMU could cause a guest I/O operation otherwise
addressed to an arbitrary disk offset to be targeted to
offset 0 instead (potentially overwriting the VM's boot code).

This change is to fix CVE-2023-5088.

Link: 
https://gitlab.com/qemu-project/qemu/-/commit/7d7512019fc40c577e2bdd61f114f31a9eb84a8e

Signed-off-by: Sourav Pramanik 
Signed-off-by: Sourav Kumar Pramanik 
Signed-off-by: Steve Sakoman 
---
 meta/recipes-devtools/qemu/qemu.inc   |   1 +
 .../qemu/qemu/CVE-2023-5088.patch | 112 ++
 2 files changed, 113 insertions(+)
 create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2023-5088.patch

diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index c8e4e2e6f3..c5fb9b1eab 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -102,6 +102,7 @@ SRC_URI = "https://download.qemu.org/${BPN}-${PV}.tar.xz \
   file://CVE-2023-3180.patch \
   file://CVE-2021-3638.patch \
   file://CVE-2023-1544.patch \
+  file://CVE-2023-5088.patch \
"
 UPSTREAM_CHECK_REGEX = "qemu-(?P\d+(\.\d+)+)\.tar"
 
diff --git a/meta/recipes-devtools/qemu/qemu/CVE-2023-5088.patch 
b/meta/recipes-devtools/qemu/qemu/CVE-2023-5088.patch
new file mode 100644
index 00..c5ea9d739a
--- /dev/null
+++ b/meta/recipes-devtools/qemu/qemu/CVE-2023-5088.patch
@@ -0,0 +1,112 @@
+From 7d7512019fc40c577e2bdd61f114f31a9eb84a8e Mon Sep 17 00:00:00 2001
+From: Fiona Ebner 
+Date: Wed, 6 Sep 2023 15:09:21 +0200
+Subject: [PATCH] hw/ide: reset: cancel async DMA operation before resetting
+ state
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+If there is a pending DMA operation during ide_bus_reset(), the fact
+that the IDEState is already reset before the operation is canceled
+can be problematic. In particular, ide_dma_cb() might be called and
+then use the reset IDEState which contains the signature after the
+reset. When used to construct the IO operation this leads to
+ide_get_sector() returning 0 and nsector being 1. This is particularly
+bad, because a write command will thus destroy the first sector which
+often contains a partition table or similar.
+
+Traces showing the unsolicited write happening with IDEState
+0x5595af6949d0 being used after reset:
+
+> ahci_port_write ahci(0x5595af6923f0)[0]: port write [reg:PxSCTL] @ 0x2c: 
0x0300
+> ahci_reset_port ahci(0x5595af6923f0)[0]: reset port
+> ide_reset IDEstate 0x5595af6949d0
+> ide_reset IDEstate 0x5595af694da8
+> ide_bus_reset_aio aio_cancel
+> dma_aio_cancel dbs=0x7f64600089a0
+> dma_blk_cb dbs=0x7f64600089a0 ret=0
+> dma_complete dbs=0x7f64600089a0 ret=0 cb=0x5595acd40b30
+> ahci_populate_sglist ahci(0x5595af6923f0)[0]
+> ahci_dma_prepare_buf ahci(0x5595af6923f0)[0]: prepare buf limit=512 
prepared=512
+> ide_dma_cb IDEState 0x5595af6949d0; sector_num=0 n=1 cmd=DMA WRITE
+> dma_blk_io dbs=0x7f6420802010 bs=0x5595ae2c6c30 offset=0 to_dev=1
+> dma_blk_cb dbs=0x7f6420802010 ret=0
+
+> (gdb) p *qiov
+> $11 = {iov = 0x7f647c76d840, niov = 1, {{nalloc = 1, local_iov = {iov_base = 
0x0,
+>   iov_len = 512}}, {__pad = 
"\001\000\000\000\000\000\000\000\000\000\000",
+>   size = 512}}}
+> (gdb) bt
+> #0  blk_aio_pwritev (blk=0x5595ae2c6c30, offset=0, qiov=0x7f6420802070, 
flags=0,
+> cb=0x5595ace6f0b0 , opaque=0x7f6420802010)
+> at ../block/block-backend.c:1682
+> #1  0x5595ace6f185 in dma_blk_cb (opaque=0x7f6420802010, ret=)
+> at ../softmmu/dma-helpers.c:179
+> #2  0x5595ace6f778 in dma_blk_io (ctx=0x5595ae0609f0,
+> sg=sg@entry=0x5595af694d00, offset=offset@entry=0, align=align@entry=512,
+> io_func=io_func@entry=0x5595ace6ee30 ,
+> io_func_opaque=io_func_opaque@entry=0x5595ae2c6c30,
+> cb=0x5595acd40b30 , opaque=0x5595af6949d0,
+> dir=DMA_DIRECTION_TO_DEVICE) at ../softmmu/dma-helpers.c:244
+> #3  0x5595ace6f90a in dma_blk_write (blk=0x5595ae2c6c30,
+> sg=sg@entry=0x5595af694d00, offset=offset@entry=0, align=align@entry=512,
+> cb=cb@entry=0x5595acd40b30 , 
opaque=opaque@entry=0x5595af6949d0)
+> at ../softmmu/dma-helpers.c:280
+> #4  0x5595acd40e18 in ide_dma_cb (opaque=0x5595af6949d0, ret=)
+> at ../hw/ide/core.c:953
+> #5  0x5595ace6f319 in dma_complete (ret=0, dbs=0x7f64600089a0)
+> at ../softmmu/dma-helpers.c:107
+> #6  dma_blk_cb (opaque=0x7f64600089a0, ret=0) at ../softmmu/dma-helpers.c:127
+> #7  0x5595ad12227d in blk_aio_complete (acb=0x7f6460005b10)
+> at ../block/block-backend.c:1527
+> #8  blk_aio_complete (acb=0x7f6460005b10) at ../block/block-backend.c:1524
+> #9  blk_aio_write_entry (opaque=0x7f6460005b10) at 
../block/block-backend.c:1594
+> #10 0x5595ad258cfb in coroutine_trampoline (i0=,
+> i1=) at ../util/coroutine-ucontext.c:177
+
+CVE: CVE-2023-5088
+Upstream-Status: Backport 

[OE-core][kirkstone 02/11] curl: Fix CVE-2023-46218

2023-12-20 Thread Steve Sakoman
From: Poonam Jadhav 

Add patch to fix CVE-2023-46218

Link: 
https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/curl/7.88.1-8ubuntu2.4/curl_7.88.1-8ubuntu2.4.debian.tar.xz
  https://github.com/curl/curl/commit/2b0994c29a721c91c57

Signed-off-by: Poonam Jadhav 
Signed-off-by: Steve Sakoman 
---
 .../curl/curl/CVE-2023-46218.patch| 52 +++
 meta/recipes-support/curl/curl_7.82.0.bb  |  1 +
 2 files changed, 53 insertions(+)
 create mode 100644 meta/recipes-support/curl/curl/CVE-2023-46218.patch

diff --git a/meta/recipes-support/curl/curl/CVE-2023-46218.patch 
b/meta/recipes-support/curl/curl/CVE-2023-46218.patch
new file mode 100644
index 00..d7d7908ea0
--- /dev/null
+++ b/meta/recipes-support/curl/curl/CVE-2023-46218.patch
@@ -0,0 +1,52 @@
+Backport of:
+
+From 2b0994c29a721c91c572cff7808c572a24d251eb Mon Sep 17 00:00:00 2001
+From: Daniel Stenberg 
+Date: Thu, 23 Nov 2023 08:15:47 +0100
+Subject: [PATCH] cookie: lowercase the domain names before PSL checks
+
+Reported-by: Harry Sintonen
+
+Closes #12387
+
+CVE: CVE-2023-46218
+Upstream-Status: Backport 
[https://github.com/curl/curl/commit/2b0994c29a721c91c57]
+Signed-off-by: Poonam Jadhav 
+---
+ lib/cookie.c | 24 
+ 1 file changed, 16 insertions(+), 8 deletions(-)
+
+--- a/lib/cookie.c
 b/lib/cookie.c
+@@ -1044,15 +1044,23 @@ Curl_cookie_add(struct Curl_easy *data,
+* dereference it.
+*/
+   if(data && (domain && co->domain && !Curl_host_is_ipnum(co->domain))) {
+-const psl_ctx_t *psl = Curl_psl_use(data);
+-int acceptable;
+-
+-if(psl) {
+-  acceptable = psl_is_cookie_domain_acceptable(psl, domain, co->domain);
+-  Curl_psl_release(data);
++bool acceptable = FALSE;
++char lcase[256];
++char lcookie[256];
++size_t dlen = strlen(domain);
++size_t clen = strlen(co->domain);
++if((dlen < sizeof(lcase)) && (clen < sizeof(lcookie))) {
++  const psl_ctx_t *psl = Curl_psl_use(data);
++  if(psl) {
++/* the PSL check requires lowercase domain name and pattern */
++Curl_strntolower(lcase, domain, dlen + 1);
++Curl_strntolower(lcookie, co->domain, clen + 1);
++acceptable = psl_is_cookie_domain_acceptable(psl, lcase, lcookie);
++Curl_psl_release(data);
++  }
++  else
++acceptable = !bad_domain(domain);
+ }
+-else
+-  acceptable = !bad_domain(domain);
+ 
+ if(!acceptable) {
+   infof(data, "cookie '%s' dropped, domain '%s' must not "
diff --git a/meta/recipes-support/curl/curl_7.82.0.bb 
b/meta/recipes-support/curl/curl_7.82.0.bb
index 471bc47f34..a36d03f668 100644
--- a/meta/recipes-support/curl/curl_7.82.0.bb
+++ b/meta/recipes-support/curl/curl_7.82.0.bb
@@ -54,6 +54,7 @@ SRC_URI = "https://curl.se/download/${BP}.tar.xz \
file://CVE-2023-32001.patch \
file://CVE-2023-38545.patch \
file://CVE-2023-38546.patch \
+   file://CVE-2023-46218.patch \
"
 SRC_URI[sha256sum] = 
"0aaa12d7bd04b0966254f2703ce80dd5c38dbbd76af0297d3d690cdce58a583c"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192814): 
https://lists.openembedded.org/g/openembedded-core/message/192814
Mute This Topic: https://lists.openembedded.org/mt/103293609/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 01/11] ghostscript: Backport fix for CVE-2023-46751

2023-12-20 Thread Steve Sakoman
From: Vijay Anusuri 

Upstream-Status: Backport 
[https://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=5d2da96e81c7455338302c71a291088a8396245a]

Signed-off-by: Vijay Anusuri 
Signed-off-by: Steve Sakoman 
---
 .../ghostscript/CVE-2023-46751.patch  | 41 +++
 .../ghostscript/ghostscript_9.55.0.bb |  1 +
 2 files changed, 42 insertions(+)
 create mode 100644 
meta/recipes-extended/ghostscript/ghostscript/CVE-2023-46751.patch

diff --git a/meta/recipes-extended/ghostscript/ghostscript/CVE-2023-46751.patch 
b/meta/recipes-extended/ghostscript/ghostscript/CVE-2023-46751.patch
new file mode 100644
index 00..6fe5590892
--- /dev/null
+++ b/meta/recipes-extended/ghostscript/ghostscript/CVE-2023-46751.patch
@@ -0,0 +1,41 @@
+From 5d2da96e81c7455338302c71a291088a8396245a Mon Sep 17 00:00:00 2001
+From: Chris Liddell 
+Date: Mon, 16 Oct 2023 16:49:40 +0100
+Subject: [PATCH] Bug 707264: Fix tiffsep(1) requirement for seekable output
+ files
+
+In the device initialization redesign, tiffsep and tiffsep1 lost the 
requirement
+for the output files to be seekable.
+
+Fixing that highlighted a problem with the error handling in
+gdev_prn_open_printer_seekable() where closing the erroring file would leave a
+dangling pointer, and lead to a crash.
+
+Upstream-Status: Backport 
[https://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=5d2da96e81c7455338302c71a291088a8396245a]
+CVE: CVE-2023-46751
+Signed-off-by: Vijay Anusuri 
+---
+ base/gdevprn.c | 1 +
+ devices/gdevtsep.c | 1 +
+ 2 files changed, 2 insertions(+)
+
+--- a/base/gdevprn.c
 b/base/gdevprn.c
+@@ -1251,6 +1251,7 @@ gdev_prn_open_printer_seekable(gx_device
+   && !IS_LIBCTX_STDERR(pdev->memory, gp_get_file(ppdev->file))) {
+ 
+ code = gx_device_close_output_file(pdev, ppdev->fname, 
ppdev->file);
++ppdev->file = NULL;
+ if (code < 0)
+ return code;
+ }
+--- a/devices/gdevtsep.c
 b/devices/gdevtsep.c
+@@ -738,6 +738,7 @@ tiffsep_initialize_device_procs(gx_devic
+ {
+ gdev_prn_initialize_device_procs(dev);
+ 
++set_dev_proc(dev, output_page, gdev_prn_output_page_seekable);
+ set_dev_proc(dev, open_device, tiffsep_prn_open);
+ set_dev_proc(dev, close_device, tiffsep_prn_close);
+ set_dev_proc(dev, map_color_rgb, tiffsep_decode_color);
diff --git a/meta/recipes-extended/ghostscript/ghostscript_9.55.0.bb 
b/meta/recipes-extended/ghostscript/ghostscript_9.55.0.bb
index 7f4050755c..e0d1e4618f 100644
--- a/meta/recipes-extended/ghostscript/ghostscript_9.55.0.bb
+++ b/meta/recipes-extended/ghostscript/ghostscript_9.55.0.bb
@@ -42,6 +42,7 @@ SRC_URI_BASE = 
"https://github.com/ArtifexSoftware/ghostpdl-downloads/releases/d
 file://CVE-2023-36664-0002.patch \
 file://CVE-2023-38559.patch \
 file://CVE-2023-43115.patch \
+file://CVE-2023-46751.patch \
 "
 
 SRC_URI = "${SRC_URI_BASE} \
-- 
2.34.1


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



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

2023-12-20 Thread Steve Sakoman
Please review this set of changes for kirkstone and have comments back by
end of day Friday, December 22

Passed a-full on autobuilder:

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

The following changes since commit eea685e1caafd8e8121006d3f8b5d0b8a4f2a933:

  build-appliance-image: Update to kirkstone head revision (2023-12-15 04:01:10 
-1000)

are available in the Git repository at:

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

Poonam Jadhav (1):
  curl: Fix CVE-2023-46218

Richard Purdie (1):
  testimage: Exclude wtmp from target-dumper commands

Soumya Sambu (2):
  go: Fix CVE-2023-39326
  perl: update 5.34.1 -> 5.34.3

Sourav Pramanik (1):
  qemu: Fix CVE-2023-5088

Trevor Gamblin (1):
  python3-ptest: skip test_storlines

Vijay Anusuri (2):
  ghostscript: Backport fix for CVE-2023-46751
  openssh: backport Debian patch for CVE-2023-48795

Yoann Congal (1):
  externalsrc: Ensure SRCREV is processed before accessing SRC_URI

mark.yang (2):
  ffmpeg: fix for CVE-2022-3964
  ffmpeg: fix for CVE-2022-3965

 meta/classes/externalsrc.bbclass  |   4 +
 meta/classes/testimage.bbclass|   2 +-
 .../openssh/openssh/CVE-2023-48795.patch  | 476 ++
 .../fix-authorized-principals-command.patch   |  30 ++
 .../openssh/openssh_8.9p1.bb  |   2 +
 meta/recipes-devtools/go/go-1.17.13.inc   |   1 +
 .../go/go-1.20/CVE-2023-39326.patch   | 182 +++
 ...ile-check-the-file-if-patched-or-not.patch |   4 +-
 ...{perlcross_1.3.7.bb => perlcross_1.5.2.bb} |   2 +-
 .../perl/{perl_5.34.1.bb => perl_5.34.3.bb}   |   2 +-
 ...orlines-skip-due-to-load-variability.patch |  32 ++
 .../python/python3_3.10.13.bb |   1 +
 meta/recipes-devtools/qemu/qemu.inc   |   1 +
 .../qemu/qemu/CVE-2023-5088.patch | 112 +
 .../ghostscript/CVE-2023-46751.patch  |  41 ++
 .../ghostscript/ghostscript_9.55.0.bb |   1 +
 ...c-stop-accessing-out-of-bounds-frame.patch |   2 +-
 ...c-stop-accessing-out-of-bounds-frame.patch |   1 +
 .../curl/curl/CVE-2023-46218.patch|  52 ++
 meta/recipes-support/curl/curl_7.82.0.bb  |   1 +
 20 files changed, 943 insertions(+), 6 deletions(-)
 create mode 100644 
meta/recipes-connectivity/openssh/openssh/CVE-2023-48795.patch
 create mode 100644 
meta/recipes-connectivity/openssh/openssh/fix-authorized-principals-command.patch
 create mode 100644 meta/recipes-devtools/go/go-1.20/CVE-2023-39326.patch
 rename meta/recipes-devtools/perl-cross/{perlcross_1.3.7.bb => 
perlcross_1.5.2.bb} (92%)
 rename meta/recipes-devtools/perl/{perl_5.34.1.bb => perl_5.34.3.bb} (99%)
 create mode 100644 
meta/recipes-devtools/python/python3/0001-test_storlines-skip-due-to-load-variability.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2023-5088.patch
 create mode 100644 
meta/recipes-extended/ghostscript/ghostscript/CVE-2023-46751.patch
 create mode 100644 meta/recipes-support/curl/curl/CVE-2023-46218.patch

-- 
2.34.1


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



[OE-core][PATCH v3] ipk: Switch to using zstd compression

2023-12-20 Thread Joshua Watt
Converts IPK package generation to use zstd instead of xz. zstd has a
much larger compression/speed tradeoff range allowing users to choose
what suits them best, and fast decompression speeds. It also continues
to support parallel compression as xz did.

A new variable called ZSTD_DEFAULTS is provided to set the defaults for
places that want to use zstd for compression; the zst image conversion
command is also modified to use this.

Finally, in order for this to function properly, opkg must include zstd
support, so it is enabled all the time with no PACKAGECONFIG to turn it
off.

Signed-off-by: Joshua Watt 
---
 meta/classes-global/package_ipk.bbclass | 4 ++--
 meta/classes-recipe/image_types.bbclass | 4 +---
 meta/conf/bitbake.conf  | 4 
 meta/lib/oe/package_manager/ipk/__init__.py | 4 ++--
 meta/recipes-devtools/opkg/opkg_0.6.2.bb| 6 +++---
 5 files changed, 12 insertions(+), 10 deletions(-)

diff --git a/meta/classes-global/package_ipk.bbclass 
b/meta/classes-global/package_ipk.bbclass
index 71ffdd522ac..209568ae5f1 100644
--- a/meta/classes-global/package_ipk.bbclass
+++ b/meta/classes-global/package_ipk.bbclass
@@ -15,7 +15,7 @@ IPKGCONF_SDK_TARGET = "${WORKDIR}/opkg-sdk-target.conf"
 PKGWRITEDIRIPK = "${WORKDIR}/deploy-ipks"
 
 # Program to be used to build opkg packages
-OPKGBUILDCMD ??= 'opkg-build -Z xz -a "${XZ_DEFAULTS}"'
+OPKGBUILDCMD ??= 'opkg-build -Z zstd -a "${ZSTD_DEFAULTS}"'
 
 OPKG_ARGS += "--force_postinstall --prefer-arch-to-version"
 OPKG_ARGS += "${@['', 
'--no-install-recommends'][d.getVar("NO_RECOMMENDATIONS") == "1"]}"
@@ -277,7 +277,7 @@ addtask do_package_write_ipk_setscene
 
 python () {
 if d.getVar('PACKAGES') != '':
-deps = ' opkg-utils-native:do_populate_sysroot 
virtual/fakeroot-native:do_populate_sysroot xz-native:do_populate_sysroot'
+deps = ' opkg-utils-native:do_populate_sysroot 
virtual/fakeroot-native:do_populate_sysroot zstd-native:do_populate_sysroot'
 d.appendVarFlag('do_package_write_ipk', 'depends', deps)
 d.setVarFlag('do_package_write_ipk', 'fakeroot', "1")
 
diff --git a/meta/classes-recipe/image_types.bbclass 
b/meta/classes-recipe/image_types.bbclass
index d615b41ed1e..3733bdfc20c 100644
--- a/meta/classes-recipe/image_types.bbclass
+++ b/meta/classes-recipe/image_types.bbclass
@@ -63,8 +63,6 @@ ZIP_COMPRESSION_LEVEL ?= "-9"
 7ZIP_COMPRESSION_METHOD ?= "BZip2"
 7ZIP_EXTENSION ?= "7z"
 
-ZSTD_COMPRESSION_LEVEL ?= "-3"
-
 JFFS2_SUM_EXTRA_ARGS ?= ""
 IMAGE_CMD:jffs2 = "mkfs.jffs2 --root=${IMAGE_ROOTFS} --faketime 
--output=${IMGDEPLOYDIR}/${IMAGE_NAME}.jffs2 ${EXTRA_IMAGECMD}"
 
@@ -337,7 +335,7 @@ CONVERSION_CMD:lz4 = "lz4 -9 -z -l ${IMAGE_NAME}.${type} 
${IMAGE_NAME}.${type}.l
 CONVERSION_CMD:lzo = "lzop -9 ${IMAGE_NAME}.${type}"
 CONVERSION_CMD:zip = "zip ${ZIP_COMPRESSION_LEVEL} ${IMAGE_NAME}.${type}.zip 
${IMAGE_NAME}.${type}"
 CONVERSION_CMD:7zip = "7za a -mx=${7ZIP_COMPRESSION_LEVEL} 
-mm=${7ZIP_COMPRESSION_METHOD} ${IMAGE_NAME}.${type}.${7ZIP_EXTENSION} 
${IMAGE_NAME}.${type}"
-CONVERSION_CMD:zst = "zstd -f -k -T0 -c ${ZSTD_COMPRESSION_LEVEL} 
${IMAGE_NAME}.${type} > ${IMAGE_NAME}.${type}.zst"
+CONVERSION_CMD:zst = "zstd -f -k -c ${ZSTD_DEFAULTS} ${IMAGE_NAME}.${type} > 
${IMAGE_NAME}.${type}.zst"
 CONVERSION_CMD:sum = "sumtool -i ${IMAGE_NAME}.${type} -o 
${IMAGE_NAME}.${type}.sum ${JFFS2_SUM_EXTRA_ARGS}"
 CONVERSION_CMD:md5sum = "md5sum ${IMAGE_NAME}.${type} > 
${IMAGE_NAME}.${type}.md5sum"
 CONVERSION_CMD:sha1sum = "sha1sum ${IMAGE_NAME}.${type} > 
${IMAGE_NAME}.${type}.sha1sum"
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 83b12cbc158..b3f1f18a0d7 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -878,6 +878,10 @@ XZ_DEFAULTS[vardepsexclude] += "XZ_MEMLIMIT XZ_THREADS"
 ZSTD_THREADS ?= "${@oe.utils.cpu_count(at_least=2)}"
 ZSTD_THREADS[vardepvalue] = "1"
 
+ZSTD_COMPRESSION_LEVEL ?= "-3"
+ZSTD_DEFAULTS ?= "--threads=${ZSTD_THREADS} ${ZSTD_COMPRESSION_LEVEL}"
+ZSTD_DEFAULTS[vardepsexclude] = "ZSTD_THREADS"
+
 # Limit the number of threads that OpenMP libraries will use. Otherwise they
 # may fallback to using all CPUs
 export OMP_NUM_THREADS = "${BB_NUMBER_THREADS}"
diff --git a/meta/lib/oe/package_manager/ipk/__init__.py 
b/meta/lib/oe/package_manager/ipk/__init__.py
index e6f9c08e2b6..8fcbad56aab 100644
--- a/meta/lib/oe/package_manager/ipk/__init__.py
+++ b/meta/lib/oe/package_manager/ipk/__init__.py
@@ -133,7 +133,7 @@ class OpkgDpkgPM(PackageManager):
 tmp_dir = tempfile.mkdtemp()
 current_dir = os.getcwd()
 os.chdir(tmp_dir)
-data_tar = 'data.tar.xz'
+data_tar = 'data.tar.zst'
 
 try:
 cmd = [ar_cmd, 'x', pkg_path]
@@ -505,6 +505,6 @@ class OpkgPM(OpkgDpkgPM):
  "trying to extract the package."  % pkg)
 
 tmp_dir = super(OpkgPM, self).extract(pkg, pkg_info)
-bb.utils.remove(os.path.join(tmp_dir, "data.tar.xz"))
+

Re: [OE-core] weston/wayland: OpenGL vs GLES2

2023-12-20 Thread Khem Raj
On Wed, Dec 20, 2023 at 10:31 AM Chris Laplante via
lists.openembedded.org
 wrote:
>
> Hi all,
>
>
>
> Just want to check my understanding on something. It seems to me that the 
> Weston having:
>
>
>
> REQUIRED_DISTRO_FEATURES = "wayland opengl 
> ${@oe.utils.conditional('VIRTUAL-RUNTIME_init_manager', 'systemd', 'pam', '', 
> d)}"
>
>
>
> …is overly restrictive because ‘opengl’ implies desktop OpenGL, whereas 
> Weston is perfectly capable of running on gles2. At the very least, some 
> other recipes in the system seem to conflate ‘opengl’ with desktop OpenGL.
>
>
>
> For example, meta-oe/recipes-benchmark/glmark2/glmark2_git.bb.
>
>
>
> Is my understanding correct? Am I missing something?

opengl in OE context is usually not the same as desktop GL, it means
the distro needs OpenGL supported from the platform.
It is then accentuated by other things like egl glesv2, glx etc. I
think we could make it a bit better but this is something
that sits in the middle of distro and machine features.

>
>
>
> Thanks,
>
> Chris
>
>
> 
>

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



[OE-core] weston/wayland: OpenGL vs GLES2

2023-12-20 Thread Chris Laplante via lists.openembedded.org
Hi all,

Just want to check my understanding on something. It seems to me that the 
Weston having:

REQUIRED_DISTRO_FEATURES = "wayland opengl 
${@oe.utils.conditional('VIRTUAL-RUNTIME_init_manager', 'systemd', 'pam', '', 
d)}"

...is overly restrictive because 'opengl' implies desktop OpenGL, whereas 
Weston is perfectly capable of running on gles2. At the very least, some other 
recipes in the system seem to conflate 'opengl' with desktop OpenGL.

For example, meta-oe/recipes-benchmark/glmark2/glmark2_git.bb.

Is my understanding correct? Am I missing something?

Thanks,
Chris

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



[OE-core][RFC 2/2] classes-global/insane: Look up all runtime providers for file-rdeps

2023-12-20 Thread Joshua Watt
Uses the new foreach_runtime_provider_pkgdata() API to look up all
possible runtime providers of a given dependency when resolving
file-rdeps. This allows the check to correctly handle RPROVIDES for
non-virtual dependencies

Signed-off-by: Joshua Watt 
---
 meta/classes-global/insane.bbclass | 30 --
 1 file changed, 12 insertions(+), 18 deletions(-)

diff --git a/meta/classes-global/insane.bbclass 
b/meta/classes-global/insane.bbclass
index 72fcf6b2544..d625fd82f73 100644
--- a/meta/classes-global/insane.bbclass
+++ b/meta/classes-global/insane.bbclass
@@ -904,13 +904,7 @@ def package_qa_check_rdepends(pkg, pkgdest, skip, 
taskdeps, packages, d):
 if rdep_data and 'PN' in rdep_data and rdep_data['PN'] in 
taskdeps:
 continue
 if not rdep_data or not 'PN' in rdep_data:
-pkgdata_dir = d.getVar("PKGDATA_DIR")
-try:
-possibles = os.listdir("%s/runtime-rprovides/%s/" 
% (pkgdata_dir, rdepend))
-except OSError:
-possibles = []
-for p in possibles:
-rdep_data = oe.packagedata.read_subpkgdata(p, d)
+for _, rdep_data in 
oe.packagedata.foreach_runtime_provider_pkgdata(d, rdepend):
 if rdep_data and 'PN' in rdep_data and 
rdep_data['PN'] in taskdeps:
 break
 if rdep_data and 'PN' in rdep_data and rdep_data['PN'] in 
taskdeps:
@@ -958,17 +952,17 @@ def package_qa_check_rdepends(pkg, pkgdest, skip, 
taskdeps, packages, d):
 # perl
 filerdepends.pop(rdep,None)
 
-# For Saving the FILERPROVIDES, RPROVIDES and FILES_INFO
-rdep_data = oe.packagedata.read_subpkgdata(rdep, d)
-for key in rdep_data:
-if key.startswith("FILERPROVIDES:") or 
key.startswith("RPROVIDES:"):
-for subkey in 
bb.utils.explode_deps(rdep_data[key]):
-filerdepends.pop(subkey,None)
-# Add the files list to the rprovides
-if key.startswith("FILES_INFO:"):
-# Use eval() to make it as a dict
-for subkey in eval(rdep_data[key]):
-filerdepends.pop(subkey,None)
+for _, rdep_data in 
oe.packagedata.foreach_runtime_provider_pkgdata(d, rdep, True):
+for key in rdep_data:
+if key.startswith("FILERPROVIDES:") or 
key.startswith("RPROVIDES:"):
+for subkey in 
bb.utils.explode_deps(rdep_data[key]):
+filerdepends.pop(subkey,None)
+# Add the files list to the rprovides
+if key.startswith("FILES_INFO:"):
+# Use eval() to make it as a dict
+for subkey in eval(rdep_data[key]):
+filerdepends.pop(subkey,None)
+
 if not filerdepends:
 # Break if all the file rdepends are met
 break
-- 
2.34.1


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



[OE-core][RFC 1/2] lib/packagedata.py: Add API to iterate over rprovides

2023-12-20 Thread Joshua Watt
Adds an API that makes it easier to iterate over the package data for a
all providers of a runtime dependency.

Signed-off-by: Joshua Watt 
---
 meta/lib/oe/packagedata.py | 15 +++
 1 file changed, 15 insertions(+)

diff --git a/meta/lib/oe/packagedata.py b/meta/lib/oe/packagedata.py
index d59f6f5a569..2d1d6ddeb75 100644
--- a/meta/lib/oe/packagedata.py
+++ b/meta/lib/oe/packagedata.py
@@ -116,6 +116,21 @@ def recipename(pkg, d):
 
 return pkgmap(d).get(pkg)
 
+def foreach_runtime_provider_pkgdata(d, rdep, include_rdep=False):
+pkgdata_dir = d.getVar("PKGDATA_DIR")
+possibles = set()
+try:
+possibles |= set(os.listdir("%s/runtime-rprovides/%s/" % (pkgdata_dir, 
rdep)))
+except OSError:
+pass
+
+if include_rdep:
+possibles.add(rdep)
+
+for p in sorted(list(possibles)):
+rdep_data = read_subpkgdata(p, d)
+yield p, rdep_data
+
 def get_package_mapping(pkg, basepkg, d, depversions=None):
 import oe.packagedata
 
-- 
2.34.1


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



[OE-core][PATCH 2/2] lib/packagedata.py: Fix broken symlinks for providers with a '/'

2023-12-20 Thread Joshua Watt
If a package had a provider with a '/' in it (e.g. "/bin/sh",
"/bin/bash", etc.), the generated symlinks were broken due to being at a
hard coded depth. Use oe.path.relsymlink() instead to make a correct
relative symbolic link

Signed-off-by: Joshua Watt 
---
 meta/lib/oe/packagedata.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/lib/oe/packagedata.py b/meta/lib/oe/packagedata.py
index 162ff60d72f..d59f6f5a569 100644
--- a/meta/lib/oe/packagedata.py
+++ b/meta/lib/oe/packagedata.py
@@ -317,7 +317,7 @@ fi
 for p in bb.utils.explode_deps(rprov):
 subdata_sym = pkgdatadir + "/runtime-rprovides/%s/%s" % (p, 
pkg)
 bb.utils.mkdirhier(os.path.dirname(subdata_sym))
-oe.path.symlink("../../runtime/%s" % pkg, subdata_sym, True)
+oe.path.relsymlink(subdata_file, subdata_sym, True)
 
 allow_empty = d.getVar('ALLOW_EMPTY:%s' % pkg)
 if not allow_empty:
@@ -328,7 +328,7 @@ fi
 if g or allow_empty == "1":
 # Symlinks needed for reverse lookups (from the final package name)
 subdata_sym = pkgdatadir + "/runtime-reverse/%s" % pkgval
-oe.path.symlink("../runtime/%s" % pkg, subdata_sym, True)
+oe.path.relsymlink(subdata_file, subdata_sym, True)
 
 packagedfile = pkgdatadir + '/runtime/%s.packaged' % pkg
 open(packagedfile, 'w').close()
-- 
2.34.1


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



[OE-core][PATCH 1/2] lib/oe/path.py: Add relsymlink()

2023-12-20 Thread Joshua Watt
Adds API to make a relative symbolic link between two directories. The
arguments are the same as oe.path.symlink()

Signed-off-by: Joshua Watt 
---
 meta/lib/oe/path.py | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/lib/oe/path.py b/meta/lib/oe/path.py
index e2f1913a35c..5d21cdcbdff 100644
--- a/meta/lib/oe/path.py
+++ b/meta/lib/oe/path.py
@@ -172,6 +172,9 @@ def symlink(source, destination, force=False):
 if e.errno != errno.EEXIST or os.readlink(destination) != source:
 raise
 
+def relsymlink(target, name, force=False):
+symlink(os.path.relpath(target, os.path.dirname(name)), name, force=force)
+
 def find(dir, **walkoptions):
 """ Given a directory, recurses into that directory,
 returning all files as absolute paths. """
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192805): 
https://lists.openembedded.org/g/openembedded-core/message/192805
Mute This Topic: https://lists.openembedded.org/mt/103285746/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] qemurunner: Impove handling of serial port output blocking

2023-12-20 Thread Richard Purdie
On Wed, 2023-12-20 at 16:28 +, Alex Bennée wrote:
> Richard Purdie  writes:
> 
> > On Wed, 2023-12-20 at 09:53 +, Alex Bennée wrote:
> > > Richard Purdie  writes:
> > > 
> > > > On Tue, 2023-12-19 at 16:44 +, Alex Bennée wrote:
> > > > > Richard Purdie  writes:
> > > > > Yeah I'm only seeing A10/A11:
> > > > > 
> > > > >   o regression_1010.5 Invalid memory access 5
> > > > > regression_1010.5 OK
> > > > >   o regression_1010.6 Invalid memory access 6
> > > > > 
> > > > >   WARNING: here A10
> > > > >   WARNING: here A11
> 
> > > > 
> > > > How long does it take for the test data to "back up" and timeout? The
> > > > logging thread should take a maximum of 2s to notice data not being
> > > > read/handled on the serial port.
> > > 
> > > I don't think it goes around the logging loop more than once. I only
> > > see:
> > > 
> > >   grep "got" 
> > > build/tmp_trs-qemuarm64/work/trs_qemuarm64-trs-linux/trs-image/1.0/temp/log.do_testimage
> > >   DEBUG: got [(12, 1)]
> > > 
> > > from the poll.
> > > 
> 
> > > I'll keep digging.
> > 
> > I've merged the patches into master since they are helping the stdout
> > issue and helped a number of issues others were seeing.
> > 
> > In the final version of the patch I did fix an issue where the
> > exception handling from the thread was not working so well, it does at
> > least print a, exception/traceback properly now (in threadtarget()).
> > 
> > One of the reasons I asked about the warnings was in case that was
> > showing an issue, previously it silently failed.
> > 
> > I can believe there are other issues hiding in here :/.
> 
> So the failure was due to an exception being thrown at:
> 
>   elif self.readsock.fileno() == event[1]:
> 
> when my config hadn't triggered its opening. A bit of defensive coding
> and it works. See:
> 
>   Subject: [PATCH] qemurunner: more cleanups for output blocking
>   Date: Wed, 20 Dec 2023 16:14:50 +
>   Message-Id: <20231220161450.1422484-1-alex.ben...@linaro.org>

Glad it was something relatively simple! The fix looks good to me.

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192804): 
https://lists.openembedded.org/g/openembedded-core/message/192804
Mute This Topic: https://lists.openembedded.org/mt/103244415/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] qemurunner: Impove handling of serial port output blocking

2023-12-20 Thread Alex Bennée
Richard Purdie  writes:

> On Wed, 2023-12-20 at 09:53 +, Alex Bennée wrote:
>> Richard Purdie  writes:
>> 
>> > On Tue, 2023-12-19 at 16:44 +, Alex Bennée wrote:
>> > > Richard Purdie  writes:
>> > > Yeah I'm only seeing A10/A11:
>> > > 
>> > >   o regression_1010.5 Invalid memory access 5
>> > > regression_1010.5 OK
>> > >   o regression_1010.6 Invalid memory access 6
>> > > 
>> > >   WARNING: here A10
>> > >   WARNING: here A11

>> > 
>> > How long does it take for the test data to "back up" and timeout? The
>> > logging thread should take a maximum of 2s to notice data not being
>> > read/handled on the serial port.
>> 
>> I don't think it goes around the logging loop more than once. I only
>> see:
>> 
>>   grep "got" 
>> build/tmp_trs-qemuarm64/work/trs_qemuarm64-trs-linux/trs-image/1.0/temp/log.do_testimage
>>   DEBUG: got [(12, 1)]
>> 
>> from the poll.
>> 

>> I'll keep digging.
>
> I've merged the patches into master since they are helping the stdout
> issue and helped a number of issues others were seeing.
>
> In the final version of the patch I did fix an issue where the
> exception handling from the thread was not working so well, it does at
> least print a, exception/traceback properly now (in threadtarget()).
>
> One of the reasons I asked about the warnings was in case that was
> showing an issue, previously it silently failed.
>
> I can believe there are other issues hiding in here :/.

So the failure was due to an exception being thrown at:

  elif self.readsock.fileno() == event[1]:

when my config hadn't triggered its opening. A bit of defensive coding
and it works. See:

  Subject: [PATCH] qemurunner: more cleanups for output blocking
  Date: Wed, 20 Dec 2023 16:14:50 +
  Message-Id: <20231220161450.1422484-1-alex.ben...@linaro.org>

>
> Cheers,
>
> Richard

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192803): 
https://lists.openembedded.org/g/openembedded-core/message/192803
Mute This Topic: https://lists.openembedded.org/mt/103244415/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] qemurunner: more cleanups for output blocking

2023-12-20 Thread Alex Bennée
If we are only tracking stdout and are not using self.readsock we end
up throwing an exception blocking further action from the thread. Fix
this by checking self.readsock is not None first.

While we are at it split even into fd, event to make things clearer
and handle the fail path of stringify_event by echoing the hex value
of the unknown flag.

Signed-off-by: Alex Bennée 
Cc: Mikko Rapeli 
Cc: Richard Purdie 
---
 meta/lib/oeqa/utils/qemurunner.py | 20 
 1 file changed, 12 insertions(+), 8 deletions(-)

diff --git a/meta/lib/oeqa/utils/qemurunner.py 
b/meta/lib/oeqa/utils/qemurunner.py
index 4a2246733f..7273bbc3db 100644
--- a/meta/lib/oeqa/utils/qemurunner.py
+++ b/meta/lib/oeqa/utils/qemurunner.py
@@ -785,19 +785,20 @@ class LoggingThread(threading.Thread):
 self.logger.debug("Starting thread event loop")
 while not breakout:
 events = poll.poll(2)
-for event in events:
+for fd, event in events:
+
 # An error occurred, bail out
-if event[1] & self.errorevents:
-raise Exception(self.stringify_event(event[1]))
+if event & self.errorevents:
+raise Exception(self.stringify_event(event))
 
 # Event to stop the thread
-if self.readpipe == event[0]:
+if self.readpipe == fd:
 self.logger.debug("Stop event received")
 breakout = True
 break
 
 # A connection request was received
-elif self.serversock and self.serversock.fileno() == event[0]:
+elif self.serversock and self.serversock.fileno() == fd:
 self.logger.debug("Connection request received")
 self.readsock, _ = self.serversock.accept()
 self.readsock.setblocking(0)
@@ -808,14 +809,14 @@ class LoggingThread(threading.Thread):
 self.connection_established.set()
 
 # Actual data to be logged
-elif self.readsock.fileno() == event[0]:
+elif self.readsock and self.readsock.fileno() == fd:
 data = self.recv(1024, self.readsock)
 self.logfunc(data)
-elif self.qemuoutput.fileno() == event[0]:
+elif self.qemuoutput.fileno() == fd:
 data = self.qemuoutput.read()
 self.logger.debug("Data received on qemu stdout %s" % data)
 self.logfunc(data, ".stdout")
-elif self.serialsock and self.serialsock.fileno() == event[0]:
+elif self.serialsock and self.serialsock.fileno() == fd:
 if self.serial_lock.acquire(blocking=False):
 data = self.recv(1024, self.serialsock)
 self.logger.debug("Data received serial thread %s" % 
data.decode('utf-8', 'replace'))
@@ -864,6 +865,9 @@ class LoggingThread(threading.Thread):
 val = 'POLLHUP'
 elif select.POLLNVAL == event:
 val = 'POLLNVAL'
+else:
+val = "0x%x" % (event)
+
 return val
 
 def close_socket(self, sock):
-- 
2.39.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192802): 
https://lists.openembedded.org/g/openembedded-core/message/192802
Mute This Topic: https://lists.openembedded.org/mt/103283432/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] devtool: deploy: provide max_process to strip_execs

2023-12-20 Thread clayc
From: Clay Chang 

Use oe.utils.get_bb_number_threads to get max_process

Signed-off-by: Clay Chang 
---
 scripts/lib/devtool/deploy.py | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/scripts/lib/devtool/deploy.py b/scripts/lib/devtool/deploy.py
index e14a587417..eadf6e1521 100644
--- a/scripts/lib/devtool/deploy.py
+++ b/scripts/lib/devtool/deploy.py
@@ -140,6 +140,7 @@ def deploy(args, config, basepath, workspace):
 import math
 import oe.recipeutils
 import oe.package
+import oe.utils
 
 check_workspace_recipe(workspace, args.recipename, checksrc=False)
 
@@ -174,7 +175,7 @@ def deploy(args, config, basepath, workspace):
 exec_fakeroot(rd, "cp -af %s %s" % (os.path.join(srcdir, '.'), 
recipe_outdir), shell=True)
 os.environ['PATH'] = ':'.join([os.environ['PATH'], 
rd.getVar('PATH') or ''])
 oe.package.strip_execs(args.recipename, recipe_outdir, 
rd.getVar('STRIP'), rd.getVar('libdir'),
-rd.getVar('base_libdir'), rd)
+rd.getVar('base_libdir'), 
oe.utils.get_bb_number_threads(rd), rd)
 
 filelist = []
 inodes = set({})
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192801): 
https://lists.openembedded.org/g/openembedded-core/message/192801
Mute This Topic: https://lists.openembedded.org/mt/103277577/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] nativesdk-sdk-provides-dummy.bb: Update host tools for rust-cross-canadian

2023-12-20 Thread Richard Purdie
On Wed, 2023-12-20 at 13:13 +, Hemraj, Deepthi via lists.openembedded.org 
wrote:
> I tried adding nativesdk-libstdc++ to DEPENDS:append:class-nativesdk
> = " nativesdk-libstdc++" but the issue is still reproducing.
>  
> The nativesdk-libstdc++ is not having the GLIBCXX_3.4.30 symbols.
> Below cmd shows only GLIBCXX_3.4.29.
> "strings /ala-
> lpggp31/dhemraj/kirkstone/5082/poky/build/tmp/work/x86_64-nativesdk-
> pokysdk-linux/rust-cross-canadian-x86-64/1.59.0-r0/recipe-
> sysroot/usr/lib/libstdc++.so.6 | grep GLIBCXX"
>  
> So, I added libstdc++.so.6 as dummy in < core/meta/nativesdk-sdk-provides-dummy.bb>>
>  
> Also in the gcc documentation
> (https://gcc.gnu.org/onlinedocs/libstdc++/manual/abi.html) I see
> that, libstdc++.so.6.0.30 is provided by GCC 12.1.0 but on kirkstone
> the gcc version is 11.4. I think libstdc++.so.6.0.30 is not
> supported.

That suggests that rust-cross-canadian isn't building against our own
libstdc++ but against the one from the host instead. nativesdk-gcc-
runtime (which from memory contains libstdc++) should be being used
rather than any host dependencies.

Cheers,

Richard


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192800): 
https://lists.openembedded.org/g/openembedded-core/message/192800
Mute This Topic: https://lists.openembedded.org/mt/103107487/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] nativesdk-sdk-provides-dummy.bb: Update host tools for rust-cross-canadian

2023-12-20 Thread Hemraj, Deepthi via lists.openembedded.org
Hi Randy,

I tried adding nativesdk-libstdc++ to DEPENDS:append:class-nativesdk = " 
nativesdk-libstdc++" but the issue is still reproducing.

The nativesdk-libstdc++ is not having the GLIBCXX_3.4.30 symbols. Below cmd 
shows only GLIBCXX_3.4.29.
"strings 
/ala-lpggp31/dhemraj/kirkstone/5082/poky/build/tmp/work/x86_64-nativesdk-pokysdk-linux/rust-cross-canadian-x86-64/1.59.0-r0/recipe-sysroot/usr/lib/libstdc++.so.6
 | grep GLIBCXX"

So, I added libstdc++.so.6 as dummy in 
<>

Also in the gcc documentation 
(https://gcc.gnu.org/onlinedocs/libstdc++/manual/abi.html) I see that, 
libstdc++.so.6.0.30 is provided by GCC 12.1.0 but on kirkstone the gcc version 
is 11.4. I think libstdc++.so.6.0.30 is not supported.

Thank you,
Deepthi


From: MacLeod, Randy 
Sent: Monday, December 11, 2023 8:50:32 PM
To: Hemraj, Deepthi ; 
openembedded-core@lists.openembedded.org 

Cc: Gowda, Naveen ; Moodalappa, Shivaprasad 
; Kokkonda, Sundeep 

Subject: Re: [kirkstone][PATCH] nativesdk-sdk-provides-dummy.bb: Update host 
tools for rust-cross-canadian

On 2023-12-11 7:26 a.m., 
deepthi.hem...@windriver.com wrote:

From: Deepthi Hemraj 


[YOCTO #15082]
Packagegroup-rust-cross-canadian package requires rust-cross-canadian, but the 
necessary libstdc++.so.6(GLIBCXX_3.4.30)(64bit) library is missing.
The fix adds the libstdc++.so.6(GLIBCXX_3.4.30)(64bit) library requirement to 
the  SDK dummy package, resolving the dependency conflict.

Signed-off-by: Deepthi Hemraj 

---
 meta/recipes-core/meta/nativesdk-sdk-provides-dummy.bb | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-core/meta/nativesdk-sdk-provides-dummy.bb 
b/meta/recipes-core/meta/nativesdk-sdk-provides-dummy.bb
index 1d71f373a4..dc3ae1edaf 100644
--- a/meta/recipes-core/meta/nativesdk-sdk-provides-dummy.bb
+++ b/meta/recipes-core/meta/nativesdk-sdk-provides-dummy.bb
@@ -10,7 +10,8 @@ DUMMYPROVIDES = "\
 /usr/bin/env \
 libGL.so()(64bit) \
 libGL.so \
-"
+libstdc++.so.6(GLIBCXX_3.4.30)(64bit) \
+"

 require dummy-sdk-package.inc



This doesn't seem right to me...

Does the problem happen on master?

I haven't tried it but I suspect we want to add something like:

nativesdk-libstdc++

to:

DEPENDS:append:class-nativesdk = " nativesdk-rust-llvm"

in the rust bb file.

--
# Randy MacLeod
# Wind River Linux

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



[OE-core] Patchtest results for [PATCH 2/2] qemu: Ensure pip and the python venv aren't used for meson

2023-12-20 Thread Patchtest
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:

---
Testing patch 
/home/patchtest/share/mboxes/2-2-qemu-Ensure-pip-and-the-python-venv-aren-t-used-for-meson.patch

FAIL: test Upstream-Status presence: Upstream-Status is Inappropriate, but no 
reason was provided (test_patch.TestPatch.test_upstream_status_presence_format)

PASS: test CVE tag format (test_patch.TestPatch.test_cve_tag_format)
PASS: test Signed-off-by presence 
(test_mbox.TestMbox.test_signed_off_by_presence)
PASS: test Signed-off-by presence 
(test_patch.TestPatch.test_signed_off_by_presence)
PASS: test author valid (test_mbox.TestMbox.test_author_valid)
PASS: test commit message presence 
(test_mbox.TestMbox.test_commit_message_presence)
PASS: test max line length (test_metadata.TestMetadata.test_max_line_length)
PASS: test mbox format (test_mbox.TestMbox.test_mbox_format)
PASS: test non-AUH upgrade (test_mbox.TestMbox.test_non_auh_upgrade)
PASS: test shortlog format (test_mbox.TestMbox.test_shortlog_format)
PASS: test shortlog length (test_mbox.TestMbox.test_shortlog_length)
PASS: test target mailing list (test_mbox.TestMbox.test_target_mailing_list)

SKIP: pretest pylint: No python related patches, skipping test 
(test_python_pylint.PyLint.pretest_pylint)
SKIP: pretest src uri left files: Patch cannot be merged 
(test_metadata.TestMetadata.pretest_src_uri_left_files)
SKIP: test bugzilla entry format: No bug ID found 
(test_mbox.TestMbox.test_bugzilla_entry_format)
SKIP: test lic files chksum modified not mentioned: No modified recipes, 
skipping test 
(test_metadata.TestMetadata.test_lic_files_chksum_modified_not_mentioned)
SKIP: test lic files chksum presence: No added recipes, skipping test 
(test_metadata.TestMetadata.test_lic_files_chksum_presence)
SKIP: test license presence: No added recipes, skipping test 
(test_metadata.TestMetadata.test_license_presence)
SKIP: test pylint: No python related patches, skipping test 
(test_python_pylint.PyLint.test_pylint)
SKIP: test series merge on head: Merge test is disabled for now 
(test_mbox.TestMbox.test_series_merge_on_head)
SKIP: test src uri left files: Patch cannot be merged 
(test_metadata.TestMetadata.test_src_uri_left_files)
SKIP: test summary presence: No added recipes, skipping test 
(test_metadata.TestMetadata.test_summary_presence)

---

Please address the issues identified and
submit a new revision of the patch, or alternatively, reply to this
email with an explanation of why the patch should be accepted. If you
believe these results are due to an error in patchtest, please submit a
bug at https://bugzilla.yoctoproject.org/ (use the 'Patchtest' category
under 'Yocto Project Subprojects'). For more information on specific
failures, see: https://wiki.yoctoproject.org/wiki/Patchtest. Thank
you!

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



[OE-core] [PATCH 1/2] qemu: Clean up DEPENDS

2023-12-20 Thread Richard Purdie
Move the common dependencies to qemu.inc for cleaner entries in the
various recipes. Remove an unneeded inherit.

Signed-off-by: Richard Purdie 
---
 meta/recipes-devtools/qemu/qemu-native_8.1.2.bb| 2 +-
 meta/recipes-devtools/qemu/qemu-system-native_8.1.2.bb | 4 +---
 meta/recipes-devtools/qemu/qemu.inc| 2 ++
 meta/recipes-devtools/qemu/qemu_8.1.2.bb   | 2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta/recipes-devtools/qemu/qemu-native_8.1.2.bb 
b/meta/recipes-devtools/qemu/qemu-native_8.1.2.bb
index 73a0f63f2b2..a77953529b1 100644
--- a/meta/recipes-devtools/qemu/qemu-native_8.1.2.bb
+++ b/meta/recipes-devtools/qemu/qemu-native_8.1.2.bb
@@ -1,6 +1,6 @@
 BPN = "qemu"
 
-DEPENDS = "glib-2.0-native zlib-native ninja-native meson-native"
+DEPENDS += "glib-2.0-native zlib-native"
 
 require qemu-native.inc
 
diff --git a/meta/recipes-devtools/qemu/qemu-system-native_8.1.2.bb 
b/meta/recipes-devtools/qemu/qemu-system-native_8.1.2.bb
index 558a416f7b4..0634b342429 100644
--- a/meta/recipes-devtools/qemu/qemu-system-native_8.1.2.bb
+++ b/meta/recipes-devtools/qemu/qemu-system-native_8.1.2.bb
@@ -1,13 +1,11 @@
 BPN = "qemu"
 
-inherit python3-dir
-
 require qemu-native.inc
 
 # As some of the files installed by qemu-native and qemu-system-native
 # are the same, we depend on qemu-native to get the full installation set
 # and avoid file clashes
-DEPENDS = "glib-2.0-native zlib-native pixman-native qemu-native bison-native 
meson-native ninja-native"
+DEPENDS += "glib-2.0-native zlib-native pixman-native qemu-native"
 
 EXTRA_OECONF:append = " --target-list=${@get_qemu_system_target_list(d)}"
 
diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index 58284ef9937..9e187a09958 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -6,6 +6,8 @@ a variety of guest operating systems"
 HOMEPAGE = "http://qemu.org;
 LICENSE = "GPL-2.0-only & LGPL-2.1-only"
 
+DEPENDS += "bison-native meson-native ninja-native"
+
 RDEPENDS:${PN}-ptest = "bash"
 
 require qemu-targets.inc
diff --git a/meta/recipes-devtools/qemu/qemu_8.1.2.bb 
b/meta/recipes-devtools/qemu/qemu_8.1.2.bb
index 84ee0bcc492..dc1352232ef 100644
--- a/meta/recipes-devtools/qemu/qemu_8.1.2.bb
+++ b/meta/recipes-devtools/qemu/qemu_8.1.2.bb
@@ -2,7 +2,7 @@ BBCLASSEXTEND = "nativesdk"
 
 require qemu.inc
 
-DEPENDS = "glib-2.0 zlib pixman bison-native ninja-native meson-native"
+DEPENDS += "glib-2.0 zlib pixman"
 
 DEPENDS:append:libc-musl = " libucontext"
 
-- 
2.39.2


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



[OE-core] [PATCH 2/2] qemu: Ensure pip and the python venv aren't used for meson

2023-12-20 Thread Richard Purdie
Qemu wants to use a supported python verison and a specific meson version
to "help" users and uses pip and creates a venv to do this. This is a nightmare
for us. Our versions stay up to date and should be supported so we don't
really need/want this wrapping. Tweak things to disable it.

There was breakage from the wrapper shown by:

bitbake qemu-system-native

bitbake qemu-system-native -c configure

which would crash. The issue is the change in configuration removes pieces
from the sysroot but pyc files remainm as do pieces of pip which causes
problems.

Signed-off-by: Richard Purdie 
---
 meta/recipes-devtools/qemu/qemu.inc  |  1 +
 meta/recipes-devtools/qemu/qemu/no-pip.patch | 45 
 2 files changed, 46 insertions(+)
 create mode 100644 meta/recipes-devtools/qemu/qemu/no-pip.patch

diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index 9e187a09958..70515d980e7 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -34,6 +34,7 @@ SRC_URI = "https://download.qemu.org/${BPN}-${PV}.tar.xz \
file://fixedmeson.patch \
file://fixmips.patch \
file://0001-vfio-Include-libgen.h-for-basename-API.patch \
+   file://no-pip.patch \
file://qemu-guest-agent.init \
file://qemu-guest-agent.udev \
"
diff --git a/meta/recipes-devtools/qemu/qemu/no-pip.patch 
b/meta/recipes-devtools/qemu/qemu/no-pip.patch
new file mode 100644
index 000..64d6c8a77bd
--- /dev/null
+++ b/meta/recipes-devtools/qemu/qemu/no-pip.patch
@@ -0,0 +1,45 @@
+qemu: Ensure pip and the python venv aren't used for meson
+
+Qemu wants to use a supported python verison and a specific meson version
+to "help" users and uses pip and creates a venv to do this. This is a nightmare
+for us. Our versions stay up to date and should be supported so we don't
+really need/want this wrapping. Tweak things to disable it.
+
+There was breakage from the wrapper shown by:
+
+bitbake qemu-system-native
+
+bitbake qemu-system-native -c configure
+
+which would crash. The issue is the change in configuration removes pieces
+from the sysroot but pyc files remainm as do pieces of pip which causes
+problems.
+
+Ideally we'd convince upstream to allow some way to disable the venv on
+the understanding that if/when it breaks, we keep the pieces. The patch
+as it stands is a workaround.
+
+Upstream-Status: Inappropriate
+Signed-off-by: Richard Purdie 
+
+diff --git a/configure b/configure
+index 133f4e3235..e4c144b4e2 100755
+--- a/configure
 b/configure
+@@ -1009,7 +1009,7 @@ python="$(command -v "$python")"
+ echo "python determined to be '$python'"
+ echo "python version: $($python --version)"
+ 
+-python="$($python -B "${source_path}/python/scripts/mkvenv.py" create pyvenv)"
++python=python3
+ if test "$?" -ne 0 ; then
+ error_exit "python venv creation failed"
+ fi
+@@ -1017,6 +1017,7 @@ fi
+ # Suppress writing compiled files
+ python="$python -B"
+ mkvenv="$python ${source_path}/python/scripts/mkvenv.py"
++mkvenv=true
+ 
+ mkvenv_flags=""
+ if test "$download" = "enabled" ; then
-- 
2.39.2


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



[OE-core][PATCH 1/1] ncurses: Fix - tty is hung after reset

2023-12-20 Thread Soumya via lists.openembedded.org
From: Soumya Sambu 

Serial tty is hung after reset command -
$echo "test " >> /dev/ttyS0
test
$stty -a < /dev/ttyS0
speed 115200 baud; rows 34; columns 153; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = ; eol2 = 
; swtch = ;
start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
werase = ^W; lnext = ^V; discard = ^O; min = 1; time = 0;
-parenb -parodd -cmspar cs8 hupcl -cstopb cread clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon ixoff 
-iuclc -ixany -imaxbel iutf8
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig icanon -iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt 
echoctl echoke -flusho -extproc
$reset
$echo "test " >> /dev/ttyS0
^C
$stty -a < /dev/ttyS0
^C

Updating reset_tty_settings API with latest code which fixes tty hung issue

Signed-off-by: Soumya Sambu 
---
 ...eset-code-ncurses-6.4-patch-20231104.patch | 499 ++
 meta/recipes-core/ncurses/ncurses_6.4.bb  |   1 +
 2 files changed, 500 insertions(+)
 create mode 100644 
meta/recipes-core/ncurses/files/0001-Updating-reset-code-ncurses-6.4-patch-20231104.patch

diff --git 
a/meta/recipes-core/ncurses/files/0001-Updating-reset-code-ncurses-6.4-patch-20231104.patch
 
b/meta/recipes-core/ncurses/files/0001-Updating-reset-code-ncurses-6.4-patch-20231104.patch
new file mode 100644
index 00..121db6bffe
--- /dev/null
+++ 
b/meta/recipes-core/ncurses/files/0001-Updating-reset-code-ncurses-6.4-patch-20231104.patch
@@ -0,0 +1,499 @@
+From 135d37072755704b8d018e5de74e62ff3f28c930 Mon Sep 17 00:00:00 2001
+From: Thomas E. Dickey 
+Date: Sun, 5 Nov 2023 05:54:54 +0530
+Subject: [PATCH] Updating reset code - ncurses 6.4 - patch 20231104
+
++ modify reset command to avoid altering clocal if the terminal uses a
+  modem (prompted by discussion with Werner Fink, Michal Suchanek,
+  OpenSUSE #1201384, Debian #60377).
++ build-fixes for --with-caps variations.
++ correct a couple of section-references in INSTALL.
+
+Signed-off-by: Thomas E. Dickey 
+
+Upstream-Status: Backport 
[https://ncurses.scripts.mit.edu/?p=ncurses.git;a=commitdiff;h=135d37072755704b8d018e5de74e62ff3f28c930]
+
+Signed-off-by: Soumya Sambu 
+---
+ INSTALL   |   8 +-
+ include/curses.events |   2 +-
+ ncurses/tinfo/lib_tparm.c |   2 +
+ progs/reset_cmd.c | 281 +-
+ progs/tabs.c  |  10 +-
+ progs/tic.c   |   4 +
+ 6 files changed, 176 insertions(+), 131 deletions(-)
+
+diff --git a/INSTALL b/INSTALL
+index d9c1dd12..d0a39af0 100644
+--- a/INSTALL
 b/INSTALL
+@@ -47,7 +47,7 @@ If you are converting from BSD curses and do not have root 
access, be sure
+ to read the BSD CONVERSION NOTES section below.
+
+ If you are trying to build applications using gpm with ncurses,
+-read the USING NCURSES WITH GPM section below.
++read the USING GPM section below.
+
+ If you are cross-compiling, see the note below on BUILDING WITH A 
CROSS-COMPILER.
+
+@@ -79,7 +79,7 @@ INSTALLATION PROCEDURE:
+ The --prefix option to configure changes the root directory for installing
+ ncurses.  The default is normally in subdirectories of /usr/local, except
+ for systems where ncurses is normally installed as a system library (see
+-"IF YOU ARE A SYSTEM INTEGRATOR").  Use --prefix=/usr to replace your
++"FOR SYSTEM INTEGRATORS").  Use --prefix=/usr to replace your
+ default curses distribution.
+
+ The package gets installed beneath the --prefix directory as follows:
+@@ -176,7 +176,7 @@ INSTALLATION PROCEDURE:
+ You can make curses and terminfo fall back to an existing file of termcap
+ definitions by configuring with --enable-termcap.  If you do this, the
+ library will search /etc/termcap before the terminfo database, and will
+-also interpret the contents of the TERM environment variable.  See the
++also interpret the contents of the $TERM environment variable.  See the
+ section BSD CONVERSION NOTES below.
+
+ 3.  Type `make'.  Ignore any warnings, no error messages should be produced.
+@@ -1231,7 +1231,7 @@ CONFIGURE OPTIONS:
+   Specify a search-list of terminfo directories which will be compiled
+   into the ncurses library (default: DATADIR/terminfo)
+
+-  This is a colon-separated list, like the TERMINFO_DIRS environment
++  This is a colon-separated list, like the $TERMINFO_DIRS environment
+   variable.
+
+ --with-termlib[=XXX]
+diff --git a/include/curses.events b/include/curses.events
+index 25a2583f..468bde18 100644
+--- a/include/curses.events
 b/include/curses.events
+@@ -50,6 +50,6 @@ typedef struct
+ extern NCURSES_EXPORT(int) wgetch_events (WINDOW *, _nc_eventlist *) 
GCC_DEPRECATED(experimental option); /* experimental */
+ extern NCURSES_EXPORT(int) wgetnstr_events (WINDOW *,char *,int,_nc_eventlist 
*) GCC_DEPRECATED(experimental option); /* experimental */
+
+-#define KEY_EVENT 0633   

[OE-core][kirkstone][PATCH 1/1] go: Fix CVE-2023-39326

2023-12-20 Thread Soumya via lists.openembedded.org
From: Soumya Sambu 

A malicious HTTP sender can use chunk extensions to cause a receiver
reading from a request or response body to read many more bytes from
the network than are in the body. A malicious HTTP client can further
exploit this to cause a server to automatically read a large amount
of data (up to about 1GiB) when a handler fails to read the entire
body of a request. Chunk extensions are a little-used HTTP feature
which permit including additional metadata in a request or response
body sent using the chunked encoding. The net/http chunked encoding
reader discards this metadata. A sender can exploit this by inserting
a large metadata segment with each byte transferred. The chunk reader
now produces an error if the ratio of real body to encoded bytes grows
too small.

References:
https://nvd.nist.gov/vuln/detail/CVE-2023-39326
https://security-tracker.debian.org/tracker/CVE-2023-39326

Signed-off-by: Soumya Sambu 
---
 meta/recipes-devtools/go/go-1.17.13.inc   |   1 +
 .../go/go-1.20/CVE-2023-39326.patch   | 182 ++
 2 files changed, 183 insertions(+)
 create mode 100644 meta/recipes-devtools/go/go-1.20/CVE-2023-39326.patch

diff --git a/meta/recipes-devtools/go/go-1.17.13.inc 
b/meta/recipes-devtools/go/go-1.17.13.inc
index 330f571d22..95c4461d3e 100644
--- a/meta/recipes-devtools/go/go-1.17.13.inc
+++ b/meta/recipes-devtools/go/go-1.17.13.inc
@@ -47,6 +47,7 @@ SRC_URI += "\
 file://CVE-2023-29409.patch \
 file://CVE-2023-39319.patch \
 file://CVE-2023-39318.patch \
+file://CVE-2023-39326.patch \
 "
 SRC_URI[main.sha256sum] = 
"a1a48b23afb206f95e7bbaa9b898d965f90826f6f1d1fc0c1d784ada0cd300fd"
 
diff --git a/meta/recipes-devtools/go/go-1.20/CVE-2023-39326.patch 
b/meta/recipes-devtools/go/go-1.20/CVE-2023-39326.patch
new file mode 100644
index 00..ca78e552c2
--- /dev/null
+++ b/meta/recipes-devtools/go/go-1.20/CVE-2023-39326.patch
@@ -0,0 +1,182 @@
+From 6446af942e2e2b161c4ec1b60d9703a2b55dc4dd Mon Sep 17 00:00:00 2001
+From: Damien Neil 
+Date: Tue, 7 Nov 2023 10:47:56 -0800
+Subject: [PATCH] net/http: limit chunked data overhead
+
+The chunked transfer encoding adds some overhead to
+the content transferred. When writing one byte per
+chunk, for example, there are five bytes of overhead
+per byte of data transferred: "1\r\nX\r\n" to send "X".
+
+Chunks may include "chunk extensions",
+which we skip over and do not use.
+For example: "1;chunk extension here\r\nX\r\n".
+
+A malicious sender can use chunk extensions to add
+about 4k of overhead per byte of data.
+(The maximum chunk header line size we will accept.)
+
+Track the amount of overhead read in chunked data,
+and produce an error if it seems excessive.
+
+Updates #64433
+Fixes #64434
+Fixes CVE-2023-39326
+
+Change-Id: I40f8d70eb6f9575fb43f506eb19132ccedafcf39
+Reviewed-on: 
https://team-review.git.corp.google.com/c/golang/go-private/+/2076135
+Reviewed-by: Tatiana Bradley 
+Reviewed-by: Roland Shoemaker 
+(cherry picked from commit 3473ae72ee66c60744665a24b2fde143e8964d4f)
+Reviewed-on: 
https://team-review.git.corp.google.com/c/golang/go-private/+/2095407
+Run-TryBot: Roland Shoemaker 
+TryBot-Result: Security TryBots 

+Reviewed-by: Damien Neil 
+Reviewed-on: https://go-review.googlesource.com/c/go/+/547355
+Reviewed-by: Dmitri Shuralyov 
+LUCI-TryBot-Result: Go LUCI 

+
+CVE: CVE-2023-39326
+
+Upstream-Status: Backport 
[https://github.com/golang/go/commit/6446af942e2e2b161c4ec1b60d9703a2b55dc4dd]
+
+Signed-off-by: Soumya Sambu 
+---
+ src/net/http/internal/chunked.go  | 36 +---
+ src/net/http/internal/chunked_test.go | 59 +++
+ 2 files changed, 89 insertions(+), 6 deletions(-)
+
+diff --git a/src/net/http/internal/chunked.go 
b/src/net/http/internal/chunked.go
+index f06e572..ddbaacb 100644
+--- a/src/net/http/internal/chunked.go
 b/src/net/http/internal/chunked.go
+@@ -39,7 +39,8 @@ type chunkedReader struct {
+   nuint64 // unread bytes in chunk
+   err  error
+   buf  [2]byte
+-  checkEnd bool // whether need to check for \r\n chunk footer
++  checkEnd bool  // whether need to check for \r\n chunk footer
++  excess   int64 // "excessive" chunk overhead, for malicious sender 
detection
+ }
+
+ func (cr *chunkedReader) beginChunk() {
+@@ -49,10 +50,38 @@ func (cr *chunkedReader) beginChunk() {
+   if cr.err != nil {
+   return
+   }
++  cr.excess += int64(len(line)) + 2 // header, plus \r\n after the chunk 
data
++  line = trimTrailingWhitespace(line)
++  line, cr.err = removeChunkExtension(line)
++  if cr.err != nil {
++  return
++  }
+   cr.n, cr.err = parseHexUint(line)
+   if cr.err != nil {
+   return
+   }
++  // A sender who sends one byte per chunk will send 5 bytes of overhead
++  // for every byte of data. ("1\r\nX\r\n" to send "X".)
++  // We want to allow this, since streaming a byte at a time can 

[OE-core] [PATCH] oeqa/selftest/overlayfs: Fix whitespace

2023-12-20 Thread Richard Purdie
My previous fix missed out whitespace with the append, fix that.

Signed-off-by: Richard Purdie 

#
---
 meta/lib/oeqa/selftest/cases/overlayfs.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/lib/oeqa/selftest/cases/overlayfs.py 
b/meta/lib/oeqa/selftest/cases/overlayfs.py
index 19ee228fff5..cd0dc60c640 100644
--- a/meta/lib/oeqa/selftest/cases/overlayfs.py
+++ b/meta/lib/oeqa/selftest/cases/overlayfs.py
@@ -79,7 +79,7 @@ DISTRO_FEATURES:append = " systemd overlayfs usrmerge"
 
 config = """
 IMAGE_INSTALL:append = " overlayfs-user"
-DISTRO_FEATURES:append = "systemd overlayfs usrmerge"
+DISTRO_FEATURES:append = " systemd overlayfs usrmerge"
 OVERLAYFS_QA_SKIP[mnt-overlay] = "mount-configured"
 """
 
-- 
2.39.2


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

2023-12-20 Thread Alexandre Belloni via lists.openembedded.org
Hello,

I already told you that this is breaking webkit on the 23/11/2023...

On 19/12/2023 17:34:24+0800, wangmy wrote:
> From: Wang Mingyu 
> 
> Changelog:
> ==
> - parser: Fix namespaces redefined from default attributes
> - include: Rename XML_EMPTY helper macro
> - include: Move declaration of xmlInitGlobals
> - include: Add missing includes
> - include: Move globals from xmlsave.h to parser.h
> - include: Readd circular dependency between tree.h and parser.h
> 
> install-tests.patch
> refreshed for 2.12.3
> 
> License-Update:
>  hash: Rewrite hash table code
> 
> Signed-off-by: Wang Mingyu 
> ---
>  meta/recipes-core/libxml/libxml2/install-tests.patch | 8 
>  .../libxml/{libxml2_2.11.5.bb => libxml2_2.12.3.bb}  | 9 +
>  2 files changed, 9 insertions(+), 8 deletions(-)
>  rename meta/recipes-core/libxml/{libxml2_2.11.5.bb => libxml2_2.12.3.bb} 
> (92%)
> 
> diff --git a/meta/recipes-core/libxml/libxml2/install-tests.patch 
> b/meta/recipes-core/libxml/libxml2/install-tests.patch
> index 14ccce5873..62988f6bfe 100644
> --- a/meta/recipes-core/libxml/libxml2/install-tests.patch
> +++ b/meta/recipes-core/libxml/libxml2/install-tests.patch
> @@ -1,4 +1,4 @@
> -From 3fc716357ce1372d9418dc86f24315b34d9808de Mon Sep 17 00:00:00 2001
> +From 16b46f8ef89aeebe8eb110ab8ef8e69e3a23c145 Mon Sep 17 00:00:00 2001
>  From: Ross Burton 
>  Date: Mon, 5 Dec 2022 17:02:32 +
>  Subject: [PATCH] add yocto-specific install-ptest target
> @@ -13,11 +13,11 @@ Signed-off-by: Ross Burton 
>   1 file changed, 10 insertions(+)
>  
>  diff --git a/Makefile.am b/Makefile.am
> -index 5bc4018..57d27af 100644
> +index 0a49d37..1097c63 100644
>  --- a/Makefile.am
>  +++ b/Makefile.am
> -@@ -26,6 +26,16 @@ check_PROGRAMS = \
> - testlimits \
> +@@ -27,6 +27,16 @@ check_PROGRAMS = \
> + testparser \
>   testrecurse
>   
>  +ptestdir=$(libexecdir)
> diff --git a/meta/recipes-core/libxml/libxml2_2.11.5.bb 
> b/meta/recipes-core/libxml/libxml2_2.12.3.bb
> similarity index 92%
> rename from meta/recipes-core/libxml/libxml2_2.11.5.bb
> rename to meta/recipes-core/libxml/libxml2_2.12.3.bb
> index 319833f053..8f37a39fe2 100644
> --- a/meta/recipes-core/libxml/libxml2_2.11.5.bb
> +++ b/meta/recipes-core/libxml/libxml2_2.12.3.bb
> @@ -4,10 +4,11 @@ HOMEPAGE = "https://gitlab.gnome.org/GNOME/libxml2;
>  BUGTRACKER = "http://bugzilla.gnome.org/buglist.cgi?product=libxml2;
>  SECTION = "libs"
>  LICENSE = "MIT"
> -LIC_FILES_CHKSUM = "file://Copyright;md5=2044417e2e5006b65a8b9067b683fcf1 \
> -
> file://hash.c;beginline=6;endline=15;md5=e77f77b12cb69e203d8b4090a0eee879 \
> +LIC_FILES_CHKSUM = "file://Copyright;md5=fec7ecfe714722b2bb0aaff7d200c701 \
> +
> file://hash.c;beginline=6;endline=15;md5=9af9349d0ead24569dc332f2116ef5f8 \
>  
> file://list.c;beginline=4;endline=13;md5=b9c25b021ccaf287e50060602d20f3a7 \
> -
> file://trio.c;beginline=5;endline=14;md5=cd4f61e27f88c1d43df112966b1cd28f"
> +
> file://trio.c;beginline=5;endline=14;md5=cd4f61e27f88c1d43df112966b1cd28f \
> +"
>  
>  DEPENDS = "zlib virtual/libiconv"
>  
> @@ -19,7 +20,7 @@ SRC_URI += 
> "http://www.w3.org/XML/Test/xmlts20130923.tar;subdir=${BP};name=testt
> file://install-tests.patch \
> "
>  
> -SRC_URI[archive.sha256sum] = 
> "3727b078c360ec69fa869de14bd6f75d7ee8d36987b071e6928d4720a28df3a6"
> +SRC_URI[archive.sha256sum] = 
> "8c8f1092340a89ff32bc44ad5c9693aff9bc8a7a3e161bb239666e5d15ac9aaa"
>  SRC_URI[testtar.sha256sum] = 
> "c6b2d42ee50b8b236e711a97d68e6c4b5c8d83e69a2be4722379f08702ea7273"
>  
>  # Disputed as a security issue, but fixed in d39f780
> -- 
> 2.34.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 (#192792): 
https://lists.openembedded.org/g/openembedded-core/message/192792
Mute This Topic: https://lists.openembedded.org/mt/103259916/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[OE-core] Patchtest results for [PATCH 2/2] qemu: Ensure pip and the python venv aren't used for meson

2023-12-20 Thread Patchtest
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:

---
Testing patch 
/home/patchtest/share/mboxes/2-2-qemu-Ensure-pip-and-the-python-venv-aren-t-used-for-meson.patch

FAIL: test Upstream-Status presence: Upstream-Status is Inappropriate, but no 
reason was provided (test_patch.TestPatch.test_upstream_status_presence_format)

PASS: test CVE tag format (test_patch.TestPatch.test_cve_tag_format)
PASS: test Signed-off-by presence 
(test_mbox.TestMbox.test_signed_off_by_presence)
PASS: test Signed-off-by presence 
(test_patch.TestPatch.test_signed_off_by_presence)
PASS: test author valid (test_mbox.TestMbox.test_author_valid)
PASS: test commit message presence 
(test_mbox.TestMbox.test_commit_message_presence)
PASS: test max line length (test_metadata.TestMetadata.test_max_line_length)
PASS: test mbox format (test_mbox.TestMbox.test_mbox_format)
PASS: test non-AUH upgrade (test_mbox.TestMbox.test_non_auh_upgrade)
PASS: test shortlog format (test_mbox.TestMbox.test_shortlog_format)
PASS: test shortlog length (test_mbox.TestMbox.test_shortlog_length)
PASS: test target mailing list (test_mbox.TestMbox.test_target_mailing_list)

SKIP: pretest pylint: No python related patches, skipping test 
(test_python_pylint.PyLint.pretest_pylint)
SKIP: pretest src uri left files: Patch cannot be merged 
(test_metadata.TestMetadata.pretest_src_uri_left_files)
SKIP: test bugzilla entry format: No bug ID found 
(test_mbox.TestMbox.test_bugzilla_entry_format)
SKIP: test lic files chksum modified not mentioned: No modified recipes, 
skipping test 
(test_metadata.TestMetadata.test_lic_files_chksum_modified_not_mentioned)
SKIP: test lic files chksum presence: No added recipes, skipping test 
(test_metadata.TestMetadata.test_lic_files_chksum_presence)
SKIP: test license presence: No added recipes, skipping test 
(test_metadata.TestMetadata.test_license_presence)
SKIP: test pylint: No python related patches, skipping test 
(test_python_pylint.PyLint.test_pylint)
SKIP: test series merge on head: Merge test is disabled for now 
(test_mbox.TestMbox.test_series_merge_on_head)
SKIP: test src uri left files: Patch cannot be merged 
(test_metadata.TestMetadata.test_src_uri_left_files)
SKIP: test summary presence: No added recipes, skipping test 
(test_metadata.TestMetadata.test_summary_presence)

---

Please address the issues identified and
submit a new revision of the patch, or alternatively, reply to this
email with an explanation of why the patch should be accepted. If you
believe these results are due to an error in patchtest, please submit a
bug at https://bugzilla.yoctoproject.org/ (use the 'Patchtest' category
under 'Yocto Project Subprojects'). For more information on specific
failures, see: https://wiki.yoctoproject.org/wiki/Patchtest. Thank
you!

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192791): 
https://lists.openembedded.org/g/openembedded-core/message/192791
Mute This Topic: https://lists.openembedded.org/mt/103278997/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] rust: rustdoc reproducibility issue fix

2023-12-20 Thread Sundeep KOKKONDA via lists.openembedded.org
Testing done with arm, arm64, x86 & x86_64 arch's.
Below combinations are tested.
- Tested the issue by reproducing and fixing it with the patch,
- with oe-selftest,
- Builds b/w different commits,
- with shared sstate b/w the builds.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192790): 
https://lists.openembedded.org/g/openembedded-core/message/192790
Mute This Topic: https://lists.openembedded.org/mt/103278939/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] rust: rustdoc reproducibility issue fix

2023-12-20 Thread Sundeep KOKKONDA via lists.openembedded.org
From: Sundeep KOKKONDA 

The PGO (Profile-guided Optimization) collect data about the typical execution 
of a program and then use this data to inform optimizations such as inlining, 
machine-code layout, register allocation, etc.
This optimization is by default disabled in rust sources but enabled in Yocto 
and causing the issue in rustdoc binary. To fix the issue this optimization is 
set to it's default 'false'.
More about the optimization: 
https://doc.rust-lang.org/rustc/profile-guided-optimization.html

Reverted commit #3e50e45917 "rust: Split rustdoc into a separate package"

Signed-off-by: Sundeep KOKKONDA 
---
 meta/lib/oeqa/selftest/cases/reproducible.py | 2 --
 meta/recipes-devtools/rust/rust_1.71.1.bb| 7 +++
 2 files changed, 3 insertions(+), 6 deletions(-)

diff --git a/meta/lib/oeqa/selftest/cases/reproducible.py 
b/meta/lib/oeqa/selftest/cases/reproducible.py
index 14ccb0b24d..80e830136f 100644
--- a/meta/lib/oeqa/selftest/cases/reproducible.py
+++ b/meta/lib/oeqa/selftest/cases/reproducible.py
@@ -16,8 +16,6 @@ import os
 import datetime
 
 exclude_packages = [
-   'rust-rustdoc',
-   'rust-dbg'
]
 
 def is_excluded(package):
diff --git a/meta/recipes-devtools/rust/rust_1.71.1.bb 
b/meta/recipes-devtools/rust/rust_1.71.1.bb
index 3d176e54c1..a0e9316cfd 100644
--- a/meta/recipes-devtools/rust/rust_1.71.1.bb
+++ b/meta/recipes-devtools/rust/rust_1.71.1.bb
@@ -141,13 +141,14 @@ python do_configure() {
 config.add_section("build")
 config.set("build", "submodules", e(False))
 config.set("build", "docs", e(False))
+config.set("build", "tools", ["rust-demangler",])
 
 rustc = d.expand("${WORKDIR}/rust-snapshot/bin/rustc")
 config.set("build", "rustc", e(rustc))
 
 # Support for the profiler runtime to generate e.g. coverage report,
 # PGO etc.
-config.set("build", "profiler", e(True))
+config.set("build", "profiler", e(False))
 
 cargo = d.expand("${WORKDIR}/rust-snapshot/bin/cargo")
 config.set("build", "cargo", e(cargo))
@@ -225,11 +226,9 @@ do_test_compile () {
 
 ALLOW_EMPTY:${PN} = "1"
 
-PACKAGES =+ "${PN}-rustdoc ${PN}-tools-clippy ${PN}-tools-rustfmt"
-FILES:${PN}-rustdoc = "${bindir}/rustdoc"
+PACKAGES =+ "${PN}-tools-clippy ${PN}-tools-rustfmt"
 FILES:${PN}-tools-clippy = "${bindir}/cargo-clippy ${bindir}/clippy-driver"
 FILES:${PN}-tools-rustfmt = "${bindir}/rustfmt"
-RDEPENDS:${PN}-rustdoc = "${PN}"
 RDEPENDS:${PN}-tools-clippy = "${PN}"
 RDEPENDS:${PN}-tools-rustfmt = "${PN}"
 
-- 
2.42.0


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



[OE-core] [PATCH 1/2] qemu: Clean up DEPENDS

2023-12-20 Thread Richard Purdie
Move the common dependencies to qemu.inc for cleaner entries in the
various recipes. Remove an unneeded inherit.

Signed-off-by: Richard Purdie 
---
 meta/recipes-devtools/qemu/qemu-native_8.1.2.bb| 2 +-
 meta/recipes-devtools/qemu/qemu-system-native_8.1.2.bb | 4 +---
 meta/recipes-devtools/qemu/qemu.inc| 2 ++
 meta/recipes-devtools/qemu/qemu_8.1.2.bb   | 2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta/recipes-devtools/qemu/qemu-native_8.1.2.bb 
b/meta/recipes-devtools/qemu/qemu-native_8.1.2.bb
index 73a0f63f2b2..a77953529b1 100644
--- a/meta/recipes-devtools/qemu/qemu-native_8.1.2.bb
+++ b/meta/recipes-devtools/qemu/qemu-native_8.1.2.bb
@@ -1,6 +1,6 @@
 BPN = "qemu"
 
-DEPENDS = "glib-2.0-native zlib-native ninja-native meson-native"
+DEPENDS += "glib-2.0-native zlib-native"
 
 require qemu-native.inc
 
diff --git a/meta/recipes-devtools/qemu/qemu-system-native_8.1.2.bb 
b/meta/recipes-devtools/qemu/qemu-system-native_8.1.2.bb
index 558a416f7b4..0634b342429 100644
--- a/meta/recipes-devtools/qemu/qemu-system-native_8.1.2.bb
+++ b/meta/recipes-devtools/qemu/qemu-system-native_8.1.2.bb
@@ -1,13 +1,11 @@
 BPN = "qemu"
 
-inherit python3-dir
-
 require qemu-native.inc
 
 # As some of the files installed by qemu-native and qemu-system-native
 # are the same, we depend on qemu-native to get the full installation set
 # and avoid file clashes
-DEPENDS = "glib-2.0-native zlib-native pixman-native qemu-native bison-native 
meson-native ninja-native"
+DEPENDS += "glib-2.0-native zlib-native pixman-native qemu-native"
 
 EXTRA_OECONF:append = " --target-list=${@get_qemu_system_target_list(d)}"
 
diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index 58284ef9937..9e187a09958 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -6,6 +6,8 @@ a variety of guest operating systems"
 HOMEPAGE = "http://qemu.org;
 LICENSE = "GPL-2.0-only & LGPL-2.1-only"
 
+DEPENDS += "bison-native meson-native ninja-native"
+
 RDEPENDS:${PN}-ptest = "bash"
 
 require qemu-targets.inc
diff --git a/meta/recipes-devtools/qemu/qemu_8.1.2.bb 
b/meta/recipes-devtools/qemu/qemu_8.1.2.bb
index 84ee0bcc492..6a264b445b5 100644
--- a/meta/recipes-devtools/qemu/qemu_8.1.2.bb
+++ b/meta/recipes-devtools/qemu/qemu_8.1.2.bb
@@ -2,7 +2,7 @@ BBCLASSEXTEND = "nativesdk"
 
 require qemu.inc
 
-DEPENDS = "glib-2.0 zlib pixman bison-native ninja-native meson-native"
+DEPENDS = "glib-2.0 zlib pixman"
 
 DEPENDS:append:libc-musl = " libucontext"
 
-- 
2.39.2


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



[OE-core] [PATCH 2/2] qemu: Ensure pip and the python venv aren't used for meson

2023-12-20 Thread Richard Purdie
Qemu wants to use a supported python verison and a specific meson version
to "help" users and uses pip and creates a venv to do this. This is a nightmare
for us. Our versions stay up to date and should be supported so we don't
really need/want this wrapping. Tweak things to disable it.

There was breakage from the wrapper shown by:

bitbake qemu-system-native

bitbake qemu-system-native -c configure

which would crash. The issue is the change in configuration removes pieces
from the sysroot but pyc files remainm as do pieces of pip which causes
problems.

pip usage is likely accessing the network outside of do_fetch meaning license
manifest issues too.

Signed-off-by: Richard Purdie 
---
 meta/recipes-devtools/qemu/qemu.inc  |  1 +
 meta/recipes-devtools/qemu/qemu/no-pip.patch | 48 
 2 files changed, 49 insertions(+)
 create mode 100644 meta/recipes-devtools/qemu/qemu/no-pip.patch

diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index 9e187a09958..70515d980e7 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -34,6 +34,7 @@ SRC_URI = "https://download.qemu.org/${BPN}-${PV}.tar.xz \
file://fixedmeson.patch \
file://fixmips.patch \
file://0001-vfio-Include-libgen.h-for-basename-API.patch \
+   file://no-pip.patch \
file://qemu-guest-agent.init \
file://qemu-guest-agent.udev \
"
diff --git a/meta/recipes-devtools/qemu/qemu/no-pip.patch 
b/meta/recipes-devtools/qemu/qemu/no-pip.patch
new file mode 100644
index 000..4eaa8dc3092
--- /dev/null
+++ b/meta/recipes-devtools/qemu/qemu/no-pip.patch
@@ -0,0 +1,48 @@
+qemu: Ensure pip and the python venv aren't used for meson
+
+Qemu wants to use a supported python verison and a specific meson version
+to "help" users and uses pip and creates a venv to do this. This is a nightmare
+for us. Our versions stay up to date and should be supported so we don't
+really need/want this wrapping. Tweak things to disable it.
+
+There was breakage from the wrapper shown by:
+
+bitbake qemu-system-native
+
+bitbake qemu-system-native -c configure
+
+which would crash. The issue is the change in configuration removes pieces
+from the sysroot but pyc files remainm as do pieces of pip which causes
+problems.
+
+pip usage is likely accessing the network outside of do_fetch meaning license
+manifest issues too.
+
+Ideally we'd convince upstream to allow some way to disable the venv on
+the understanding that if/when it breaks, we keep the pieces. The patch
+as it stands is a workaround.
+
+Upstream-Status: Inappropriate
+Signed-off-by: Richard Purdie 
+
+diff --git a/configure b/configure
+index 133f4e3235..e4c144b4e2 100755
+--- a/configure
 b/configure
+@@ -1009,7 +1009,7 @@ python="$(command -v "$python")"
+ echo "python determined to be '$python'"
+ echo "python version: $($python --version)"
+ 
+-python="$($python -B "${source_path}/python/scripts/mkvenv.py" create pyvenv)"
++python=python3
+ if test "$?" -ne 0 ; then
+ error_exit "python venv creation failed"
+ fi
+@@ -1017,6 +1017,7 @@ fi
+ # Suppress writing compiled files
+ python="$python -B"
+ mkvenv="$python ${source_path}/python/scripts/mkvenv.py"
++mkvenv=true
+ 
+ mkvenv_flags=""
+ if test "$download" = "enabled" ; then
-- 
2.39.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192788): 
https://lists.openembedded.org/g/openembedded-core/message/192788
Mute This Topic: https://lists.openembedded.org/mt/103278929/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] qemurunner: Impove handling of serial port output blocking

2023-12-20 Thread Richard Purdie
On Wed, 2023-12-20 at 09:53 +, Alex Bennée wrote:
> Richard Purdie  writes:
> 
> > On Tue, 2023-12-19 at 16:44 +, Alex Bennée wrote:
> > > Richard Purdie  writes:
> > > Yeah I'm only seeing A10/A11:
> > > 
> > >   o regression_1010.5 Invalid memory access 5
> > > regression_1010.5 OK
> > >   o regression_1010.6 Invalid memory access 6
> > > 
> > >   WARNING: here A10
> > >   WARNING: here A11
> > >   WARNING: here A10
> > >   WARNING: here A11
> > >   WARNING: here A10
> > >   WARNING: here A11
> > >   WARNING: here A10
> > >   WARNING: here A11
> > >   WARNING: here A10
> > >   WARNING: here A11
> > >   WARNING: here A10
> > >   WARNING: here A11
> > >   WARNING: here A10
> > >   WARNING: here A11
> > >   WARNING: here A10
> > >   WARNING: here A11
> > >   WARNING: here A10
> > >   WARNING: here A11
> > >   WARNING: here A10
> > >   WARNING: here A11
> > >   NOTE:  ... FAIL
> > >   DEBUG: Removed SIGALRM handler
> > >   Traceback (most recent call last):
> > > File 
> > > "/home/alex/lsrc/tests/trs/build/../poky/meta/lib/oeqa/core/decorator/__init__.py",
> > >  line 35, in wrapped_f
> > >   return func(*args, **kwargs)
> > >  ^
> > > File 
> > > "/home/alex/lsrc/tests/trs/build/../poky/meta/lib/oeqa/core/decorator/__init__.py",
> > >  line 35, in wrapped_f
> > >   return func(*args, **kwargs)
> > >  ^
> > > File 
> > > "/home/alex/lsrc/tests/trs/meta-trs/lib/oeqa/runtime/cases/opteetest.py", 
> > > line 27, in test_opteetest_xtest
> > >   self.assertEqual(status, 0, msg='\n'.join([cmd, output]))
> > >   AssertionError: 255 != 0 :  xtest   
> > >   Run test suite with level=0
> > 
> > How long does it take for the test data to "back up" and timeout? The
> > logging thread should take a maximum of 2s to notice data not being
> > read/handled on the serial port.
> 
> I don't think it goes around the logging loop more than once. I only
> see:
> 
>   grep "got" 
> build/tmp_trs-qemuarm64/work/trs_qemuarm64-trs-linux/trs-image/1.0/temp/log.do_testimage
>   DEBUG: got [(12, 1)]
> 
> from the poll.
> 
> > 
> > What the code should be doing is noticing the run_serial function isn't
> > using the port and if there is data there, reading it in the logging
> > thread. You could put further warnings around the code there to see if
> > it ever detects data to read on that port. A warning when it exits the
> > run_serial command may help too to see if it is waiting for data there
> > or not.
> > 
> > I also ended up using:
> > 
> > https://git.yoctoproject.org/poky-contrib/commit/?h=rpurdie/t222=febb0d892e4c3648cd88b8ecb9c0260edc45b68e
> > 
> > to show what was going over the serial interface when I found it wasn't
> > what I expected.
> 
> I'll keep digging.

I've merged the patches into master since they are helping the stdout
issue and helped a number of issues others were seeing.

In the final version of the patch I did fix an issue where the
exception handling from the thread was not working so well, it does at
least print a, exception/traceback properly now (in threadtarget()).

One of the reasons I asked about the warnings was in case that was
showing an issue, previously it silently failed.

I can believe there are other issues hiding in here :/.

Cheers,

Richard



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192786): 
https://lists.openembedded.org/g/openembedded-core/message/192786
Mute This Topic: https://lists.openembedded.org/mt/103244415/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] qemurunner: Impove handling of serial port output blocking

2023-12-20 Thread Alex Bennée
Richard Purdie  writes:

> On Tue, 2023-12-19 at 16:44 +, Alex Bennée wrote:
>> Richard Purdie  writes:
>> 
>> > On Tue, 2023-12-19 at 15:10 +, Alex Bennée wrote:
>> > > "Richard Purdie"  writes:
>> > > 
>> > > > Similar to stdout in the previous commit, we need to ensure serial 
>> > > > output
>> > > > if written is read and put somewhere, else qemu might block on writes 
>> > > > to
>> > > > the serial port leading to hangs in the kernel. Use our existing 
>> > > > logging
>> > > > thread to log data when run_serial is not in use.
>> > > > 
>> > > > Signed-off-by: Richard Purdie 
>> > > 
>> > > I'm still seeing hanging with my test case:
>> > > 
>> > >   o regression_1010.5 Invalid memory access 5
>> > > regression_1010.5 OK
>> > >   o regression_1010.6 Invalid memory access 6
>> > > 
>> > >   Stdout:
>> > >   Tried to dump info from target but serial console failed
>> > >   Failed CMD: top -bn1
>> > >   Tried to dump info from target but serial console failed
>> > >   Failed CMD: ps
>> > >   Tried to dump info from target but serial console failed
>> > >   Failed CMD: free
>> > > 
>> > >   NOTE: test_soafee (soafeetestsuite.SoafeeTestSuite.test_soafee)
>> > >   DEBUG: Checking if at least one of soafee-test-suite is installed
>> > >   DEBUG: Setting up a 400 second(s) timeout
>> > >   DEBUG: [Running]$ ssh -l root -o ServerAliveCountMax=2 -o 
>> > > ServerAliveInterval=30 -o UserKnownHostsFile=/dev/null -o 
>> > > StrictHostKeyChecking=no -o LogLevel=ERROR -p  127.0.0.1 export 
>> > > PATH=/usr/sbin:/sbin:/usr/bin:/bin; sudo -i -u trs soafee-test-suite run 
>> > > -r -t -T ; rm -rf /tmp/soafee-test-suite
>> > >   DEBUG: Waiting for process output: time: 1702998407.0291, endtime: 
>> > > 1702998707.0285847
>> > >   DEBUG: Waiting for process output: time: 1702998412.0338314, endtime: 
>> > > 1702998707.0285847
>> > >   DEBUG: Waiting for process output: time: 1702998417.0378022, endtime: 
>> > > 1702998707.0285847
>> > >   DEBUG: Waiting for process output: time: 1702998422.0417945, endtime: 
>> > > 1702998707.0285847
>> > >   
>> > > 
>> > > The regression tests are hanging because that has triggered output on
>> > > the serial port as the firmware attempted to service the test and the
>> > > port isn't being drained. Then when that times out we start spinning
>> > > waiting for more output.
>> > 
>> > I don't really understand where it might be hanging unfortunately as in
>> > my local tests it is draining stdout and the serial ports. Does it
>> > login to the serial console correctly? Are there any WARNING messages?
>> > 
>> > I did use this debug patch:
>> > 
>> > https://git.yoctoproject.org/poky-contrib/commit/?h=rpurdie/t222=0d9029bad610736c114e0770d2433b53133fa620
>> > 
>> > to prove that it can interleave serial commands with left over output
>> > successfully. A similar patch may help work out where your setup may be
>> > hanging?
>> 
>> Yeah I'm only seeing A10/A11:
>> 
>>   o regression_1010.5 Invalid memory access 5
>> regression_1010.5 OK
>>   o regression_1010.6 Invalid memory access 6
>> 
>>   WARNING: here A10
>>   WARNING: here A11
>>   WARNING: here A10
>>   WARNING: here A11
>>   WARNING: here A10
>>   WARNING: here A11
>>   WARNING: here A10
>>   WARNING: here A11
>>   WARNING: here A10
>>   WARNING: here A11
>>   WARNING: here A10
>>   WARNING: here A11
>>   WARNING: here A10
>>   WARNING: here A11
>>   WARNING: here A10
>>   WARNING: here A11
>>   WARNING: here A10
>>   WARNING: here A11
>>   WARNING: here A10
>>   WARNING: here A11
>>   NOTE:  ... FAIL
>>   DEBUG: Removed SIGALRM handler
>>   Traceback (most recent call last):
>> File 
>> "/home/alex/lsrc/tests/trs/build/../poky/meta/lib/oeqa/core/decorator/__init__.py",
>>  line 35, in wrapped_f
>>   return func(*args, **kwargs)
>>  ^
>> File 
>> "/home/alex/lsrc/tests/trs/build/../poky/meta/lib/oeqa/core/decorator/__init__.py",
>>  line 35, in wrapped_f
>>   return func(*args, **kwargs)
>>  ^
>> File 
>> "/home/alex/lsrc/tests/trs/meta-trs/lib/oeqa/runtime/cases/opteetest.py", 
>> line 27, in test_opteetest_xtest
>>   self.assertEqual(status, 0, msg='\n'.join([cmd, output]))
>>   AssertionError: 255 != 0 :  xtest   
>>   Run test suite with level=0
>
> How long does it take for the test data to "back up" and timeout? The
> logging thread should take a maximum of 2s to notice data not being
> read/handled on the serial port.

I don't think it goes around the logging loop more than once. I only
see:

  grep "got" 
build/tmp_trs-qemuarm64/work/trs_qemuarm64-trs-linux/trs-image/1.0/temp/log.do_testimage
  DEBUG: got [(12, 1)]

from the poll.

>
> What the code should be doing is noticing the run_serial function isn't
> using the port and if there is data there, reading it in the logging
> thread. You could put further warnings around the code there to see if
> it ever detects data to read on that port. A warning 

[OE-core] [PATCH V3] rxvt-unicode: set correct outdir for tic

2023-12-20 Thread Changqing Li
From: Changqing Li 

* tic is from ncurses-native, and set TERMINFO as
${RECIPE_SYSROOT_NATIVE}/${datadir}/terminfo of ncurses-native, so the
rxvt-unicode terminfo will be wrongly installed in there.  set the
outdir explicitly to install them to correct dir.

* Add ncurses-native as DEPENDS to fix reproducible build issue

Signed-off-by: Changqing Li 
---
 .../rxvt-unicode/rxvt-unicode.inc |  9 ++--
 ...ile.in-set-outdir-for-TIC-explicitly.patch | 44 +++
 .../0001-Makefile.in-set-outdir-for-tic.patch | 35 +++
 3 files changed, 84 insertions(+), 4 deletions(-)
 create mode 100644 
meta/recipes-sato/rxvt-unicode/rxvt-unicode/0001-Makefile.in-set-outdir-for-TIC-explicitly.patch
 create mode 100644 
meta/recipes-sato/rxvt-unicode/rxvt-unicode/0001-Makefile.in-set-outdir-for-tic.patch

diff --git a/meta/recipes-sato/rxvt-unicode/rxvt-unicode.inc 
b/meta/recipes-sato/rxvt-unicode/rxvt-unicode.inc
index e7d520ebef..b8ef0d75e5 100644
--- a/meta/recipes-sato/rxvt-unicode/rxvt-unicode.inc
+++ b/meta/recipes-sato/rxvt-unicode/rxvt-unicode.inc
@@ -6,13 +6,14 @@ terminal emulator rxvt, modified to store text in Unicode \
 output. It also supports mixing multiple fonts at the \
 same time, including Xft fonts."
 HOMEPAGE = "https://rxvt.org/;
-DEPENDS = "virtual/libx11 libxt libxft gdk-pixbuf libxmu libptytty"
+DEPENDS = "virtual/libx11 libxt libxft gdk-pixbuf libxmu libptytty 
ncurses-native"
 
 SRC_URI = 
"http://dist.schmorp.de/rxvt-unicode/Attic/rxvt-unicode-${PV}.tar.bz2 \
   file://xwc.patch \
   file://rxvt.desktop \
-  file://rxvt.png"
-
+  file://rxvt.png \
+  file://0001-Makefile.in-set-outdir-for-TIC-explicitly.patch \
+"
 inherit autotools pkgconfig update-alternatives
 
 PROVIDES = "virtual/x-terminal-emulator"
@@ -55,4 +56,4 @@ do_install:append () {
install -m 0644 ${WORKDIR}/rxvt.desktop ${D}/${datadir}/applications
 }
 
-FILES:${PN} += "${datadir}/applications/rxvt.desktop 
${datadir}/pixmaps/rxvt.png"
+FILES:${PN} += "${datadir}/applications/rxvt.desktop 
${datadir}/pixmaps/rxvt.png ${datadir}/terminfo"
diff --git 
a/meta/recipes-sato/rxvt-unicode/rxvt-unicode/0001-Makefile.in-set-outdir-for-TIC-explicitly.patch
 
b/meta/recipes-sato/rxvt-unicode/rxvt-unicode/0001-Makefile.in-set-outdir-for-TIC-explicitly.patch
new file mode 100644
index 00..6c582d288e
--- /dev/null
+++ 
b/meta/recipes-sato/rxvt-unicode/rxvt-unicode/0001-Makefile.in-set-outdir-for-TIC-explicitly.patch
@@ -0,0 +1,44 @@
+From c88c94e629b6aad1609d13f355c52e5a3acc8d2a Mon Sep 17 00:00:00 2001
+From: Changqing Li 
+Date: Thu, 14 Dec 2023 17:33:15 +0800
+Subject: [PATCH] Makefile.in: set outdir for TIC explicitly
+
+When doing cross-compile, native tic's TERMINFO usually
+set as a native dir, which could not the target install dir,
+which will cause rxvt-unicode terminfo will be wrongly installed.
+set the outdir explicitly to install them to correct dir.
+
+Upstream-Status: Submitted [ https://github.com/exg/rxvt-unicode/pull/4 ]
+
+Signed-off-by: Changqing Li 
+---
+ doc/Makefile.in | 6 +++---
+ 1 file changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/doc/Makefile.in b/doc/Makefile.in
+index e3d1fe8b..3477551a 100644
+--- a/doc/Makefile.in
 b/doc/Makefile.in
+@@ -69,7 +69,7 @@ all:
+   sed $(SEDREPLACE) <$< | podselect -section "RXVT-UNICODE\/URXVT 
FREQUENTLY ASKED QUESTIONS" | pod2text >$@
+ 
+ $(srcdir)/etc/rxvt-unicode.termcap: $(srcdir)/etc/rxvt-unicode.terminfo
+-  tic -C $< >$@
++  @TIC@ -C $< >$@
+ 
+ tags allbin:
+ 
+@@ -100,8 +100,8 @@ install: all
+   $(INSTALL_DATA) rxvtd.1.man   
$(DESTDIR)$(man1dir)/$(RXVTNAME)d.$(man1ext)
+   $(INSTALL_DATA) rxvt.7.man
$(DESTDIR)$(man7dir)/$(RXVTNAME).$(man7ext)
+   $(INSTALL_DATA) rclock.1.man  $(DESTDIR)$(man1dir)/urclock.$(man1ext)
+-  @TIC@ -x $(srcdir)/etc/rxvt-unicode.terminfo || \
+-   @TIC@ $(srcdir)/etc/rxvt-unicode.terminfo
++  @TIC@ -x $(srcdir)/etc/rxvt-unicode.terminfo -o 
$(DESTDIR)$(datadir)/terminfo || \
++   @TIC@ $(srcdir)/etc/rxvt-unicode.terminfo -o -o 
$(DESTDIR)$(datadir)/terminfo
+ 
+ distdepend: alldoc
+ 
+-- 
+2.25.1
+
diff --git 
a/meta/recipes-sato/rxvt-unicode/rxvt-unicode/0001-Makefile.in-set-outdir-for-tic.patch
 
b/meta/recipes-sato/rxvt-unicode/rxvt-unicode/0001-Makefile.in-set-outdir-for-tic.patch
new file mode 100644
index 00..8fd782b503
--- /dev/null
+++ 
b/meta/recipes-sato/rxvt-unicode/rxvt-unicode/0001-Makefile.in-set-outdir-for-tic.patch
@@ -0,0 +1,35 @@
+From 1b7d547453fc57806ef86f64c86706530a23e62e Mon Sep 17 00:00:00 2001
+From: Changqing Li 
+Date: Wed, 13 Dec 2023 11:53:18 +0800
+Subject: [PATCH] Makefile.in: set outdir for tic
+
+tic is from ncurses-native, and set TERMINFO as
+${RECIPE_SYSROOT_NATIVE}/${datadir}/terminfo of ncurses-native, so the
+rxvt-unicode terminfo will be wrongly installed in there.  set the
+outdir explicitly to install them to correct dir.
+