> -----Original Message-----
> From: Randy MacLeod <[email protected]>
> Sent: Monday, May 11, 2026 6:40 PM
> To: Marko, Peter (FT D EU SK BFS1) <[email protected]>;
> [email protected]; Kokkonda, Sundeep
> <[email protected]>
> Subject: Re: [OE-core] [PATCH] glibc: stable 2.43 branch updates
> 
> On 2026-05-07 18:48, Peter Marko via lists.openembedded.org wrote:
> 
> 
>       From: Peter Marko <[email protected]>
> <mailto:[email protected]>
> 
>       $ git log --oneline
> ce1013a197eb4a3b8ff2b07e0672f4d0b976ce7c..e9517114acc77c0b8af9da6700107df
> 16882b701
>       e9517114ac (origin/release/2.43/master) abilist.awk: Handle weak
> unversioned defined symbols
>       1634cc11a5 Linux: Only define OPEN_TREE_* macros in <sys/mount.h> if
> undefined (bug 33921)
>       d1d8d27164 include: isolate __O_CLOEXEC flag for sys/mount.h and fcntl.h
>       8362e8ce10 Use pending character state in IBM1390, IBM1399 character
> sets (CVE-2026-4046)
> 
>       Testing Results:
>       +--------------+--------+--------+------+
>       | Result       | Before | After  | Diff |
>       +--------------+--------+--------+------+
>       | PASS         | 6629   | 6632   | +3   |
>       | XPASS        | 4      | 4      |  0   |
>       | FAIL         | 105    | 103    | -2   |
>       | XFAIL        | 16     | 16     |  0   |
>       | UNSUPPORTED  | 559    | 559    |  0   |
>       +--------------+--------+--------+------+
> 
>       Changes in failed testcases:
>       malloc/tst-malloc-fork-deadlock-malloc-check  FAIL  PASS
>       malloc/tst-malloc-too-large-malloc-check      PASS  FAIL
> 
> From patch review meeting, we're going to merge this but I have the following
> question:
> 
> It's a little odd that his failed.
> 
> Is the failure reproducible?
> 
> Sundeep, can someone on the team reproduce these results
> and if the failure also happens for them explain and fix the issue?

These tests are randomly failing.
If you check some previous glibc update commits from me, some contain the same 
testcase names.
Strange is that when I do a local build, then the failures are sticky, not 
changing anymore.

I tend to not upgrade glibc because of this weirdness but is it's too long 
since last update and CVEs are getting fixed, I just go for it and hope it goes 
through the system.
I guess I'll stop sending these updates as I always get back the same questions 
and wait until someone with better testing infrastructure does that.

Peter

> 
> Thanks for the update Peter.
> 
> ../Randy
> 
> 
>       nptl/tst-getpid3                              FAIL  PASS
>       stdlib/tst-qsort3                             FAIL  PASS
> 
>       Signed-off-by: Peter Marko <[email protected]>
> <mailto:[email protected]>
>       ---
>        meta/recipes-core/glibc/glibc-version.inc | 2 +-
>        meta/recipes-core/glibc/glibc_2.43.bb     | 4 +++-
>        2 files changed, 4 insertions(+), 2 deletions(-)
> 
>       diff --git a/meta/recipes-core/glibc/glibc-version.inc b/meta/recipes-
> core/glibc/glibc-version.inc
>       index 015e7943c5..af3db54cee 100644
>       --- a/meta/recipes-core/glibc/glibc-version.inc
>       +++ b/meta/recipes-core/glibc/glibc-version.inc
>       @@ -1,6 +1,6 @@
>        SRCBRANCH ?= "release/2.43/master"
>        PV = "2.43+git"
>       -SRCREV_glibc ?= "ce1013a197eb4a3b8ff2b07e0672f4d0b976ce7c"
>       +SRCREV_glibc ?= "e9517114acc77c0b8af9da6700107df16882b701"
>        SRCREV_localedef ?= "cba02c503d7c853a38ccfb83c57e343ca5ecd7e5"
> 
>        GLIBC_GIT_URI ?= "git://sourceware.org/git/glibc.git;protocol=https"
>       diff --git a/meta/recipes-core/glibc/glibc_2.43.bb b/meta/recipes-
> core/glibc/glibc_2.43.bb
>       index ffc17eb072..b84c55ca17 100644
>       --- a/meta/recipes-core/glibc/glibc_2.43.bb
>       +++ b/meta/recipes-core/glibc/glibc_2.43.bb
>       @@ -17,7 +17,9 @@ Allows for ASLR bypass so can bypass some
> hardening, not an exploit in itself, m
>        easier access for another. 'ASLR bypass itself is not a 
> vulnerability.'"
> <mailto:diff--gita/meta/recipes-core/glibc/glibc_2.43.bbb/meta/recipes-
> core/glibc/glibc_2.43.bbindexffc17eb072..b84c55ca17100644---a/meta/recipes-
> core/glibc/glibc_2.43.bb+++b/meta/recipes-core/glibc/glibc_2.43.bb@@-
> 17,7+17,9@@AllowsforASLRbypasssocanbypasssomehardening,notanexploitinitself
> ,measieraccessforanother.'ASLRbypassitselfisnotavulnerability.'>
> 
>        CVE_STATUS_GROUPS += "CVE_STATUS_STABLE_BACKPORTS"
>       -CVE_STATUS_STABLE_BACKPORTS = "CVE-2025-15281 CVE-2026-
> 0861 CVE-2026-0915 CVE-2026-4437 CVE-2026-4438"
>       +CVE_STATUS_STABLE_BACKPORTS = "CVE-2025-15281 CVE-2026-
> 0861 CVE-2026-0915 CVE-2026-4437 CVE-2026-4438 \
>       +    CVE-2026-4046 \
>       +"
>        CVE_STATUS_STABLE_BACKPORTS[status] = "cpe-stable-backport: fix
> available in used git hash"
> 
>        DEPENDS += "gperf-native bison-native"
> 
> 
>       
> 
> 
> 
> 
> 
> --
> # Randy MacLeod
> # Wind River Linux
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#236824): 
https://lists.openembedded.org/g/openembedded-core/message/236824
Mute This Topic: https://lists.openembedded.org/mt/119206065/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to