From: "Yoann Congal" <yoann.congal@smile.fr>
To: <peter.marko@siemens.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][scarthgap][PATCH] glibc: stable 2.39 branch updates
Date: Thu, 05 Feb 2026 18:08:44 +0100 [thread overview]
Message-ID: <DG76ZND24N16.1FFJG987M3ZUU@smile.fr> (raw)
In-Reply-To: <20260125161623.729884-1-peter.marko@siemens.com>
On Sun Jan 25, 2026 at 5:16 PM CET, Peter Marko via lists.openembedded.org wrote:
> From: Peter Marko <peter.marko@siemens.com>
>
> git log --oneline 58cbbd43fe82910cf8ae9008351b0b0665104500..ce65d944e38a20cb70af2a48a4b8aa5d8fabe1cc
> ce65d944e3 (HEAD -> release/2.39/master, origin/release/2.39/master) posix: Reset wordexp_t fields with WRDE_REUSE (CVE-2025-15281 / BZ 33814)
> 831f63b94c resolv: Fix NSS DNS backend for getnetbyaddr (CVE-2026-0915)
> fb22fd3f5b memalign: reinstate alignment overflow check (CVE-2026-0861)
> 10c0bcb3d3 support: Exit on consistency check failure in resolv_response_add_name
> f47dd22366 support: Fix FILE * leak in check_for_unshare_hints in test-container
> 4a53354eaf sprof: fix -Wformat warnings on 32-bit hosts
> beb8267909 sprof: check pread size and offset for overflow
> c07002038f getaddrinfo.c: Avoid uninitialized pointer access [BZ #32465]
> ae5fb93559 nptl: Optimize trylock for high cache contention workloads (BZ #33704)
> efff7cb659 ppc64le: Power 10 rawmemchr clobbers v20 (bug #33091)
> f6becd8ae8 ppc64le: Restore optimized strncmp for power10
> 0daa4e46b8 ppc64le: Restore optimized strcmp for power10
> 28c1de6580 AArch64: Fix instability in AdvSIMD tan
> 03d0393343 AArch64: Optimise SVE scalar callbacks
> 0d05a895f1 aarch64: fix includes in SME tests
> c1dc4412f8 aarch64: fix cfi directives around __libc_arm_za_disable
> d60f15dc89 aarch64: tests for SME
> d1d0d09e9e aarch64: clear ZA state of SME before clone and clone3 syscalls
> dbe1904b7c aarch64: define macro for calling __libc_arm_za_disable
> 58cf4aa421 aarch64: update tests for SME
> 1b3bd9a9a6 aarch64: Disable ZA state of SME in setjmp and sigsetjmp
> 38942a336b linux: Also check pkey_get for ENOSYS on tst-pkey (BZ 31996)
> c74d59a656 aarch64: Do not link conform tests with -Wl,-z,force-bti (bug 33601)
> 323ad087a1 x86: fix wmemset ifunc stray '!' (bug 33542)
>
> Testing Results:
> Before After Diff
> PASS 4926 4921 -5
> XPASS 4 4 0
> FAIL 223 229 +6
> XFAIL 16 16 0
> UNSUPPORTED 224 224 0
>
> Changes in failed testcases:
>
> testcase-name before after
> elf/tst-audit21 PASS FAIL
> malloc/tst-malloc-too-large PASS FAIL
> malloc/tst-malloc-too-large-malloc-check PASS FAIL
> malloc/tst-malloc-too-large-malloc-hugetlb1 PASS FAIL
> malloc/tst-malloc-too-large-malloc-hugetlb2 PASS FAIL
> malloc/tst-malloc-too-large-mcheck PASS FAIL
Hello Peter,
Those test results show a clear regression (6 PASS->FAIL
transistions).
I noticed that the same tests have been fixed with the whinlatter
upgrade:
https://lore.kernel.org/openembedded-core/c5401d89c51fe73d93afc73d73cb0f93c00bbca7.1769845858.git.yoann.congal@smile.fr/
I'm not familiar with the glibc stable policy but shouldn't we wait the
next cycle to get the fix for those tests and avoid triggering this
regression in the meantime?
What do you think?
> Signed-off-by: Peter Marko <peter.marko@siemens.com>
> ---
> meta/recipes-core/glibc/glibc-version.inc | 2 +-
> meta/recipes-core/glibc/glibc_2.39.bb | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-core/glibc/glibc-version.inc b/meta/recipes-core/glibc/glibc-version.inc
> index 2ca15711587..03a8e5d01e3 100644
> --- a/meta/recipes-core/glibc/glibc-version.inc
> +++ b/meta/recipes-core/glibc/glibc-version.inc
> @@ -1,6 +1,6 @@
> SRCBRANCH ?= "release/2.39/master"
> PV = "2.39+git"
> -SRCREV_glibc ?= "58cbbd43fe82910cf8ae9008351b0b0665104500"
> +SRCREV_glibc ?= "ce65d944e38a20cb70af2a48a4b8aa5d8fabe1cc"
> SRCREV_localedef ?= "cba02c503d7c853a38ccfb83c57e343ca5ecd7e5"
>
> GLIBC_GIT_URI ?= "git://sourceware.org/git/glibc.git;protocol=https"
> diff --git a/meta/recipes-core/glibc/glibc_2.39.bb b/meta/recipes-core/glibc/glibc_2.39.bb
> index ff6c8f3b437..7958d64eed1 100644
> --- a/meta/recipes-core/glibc/glibc_2.39.bb
> +++ b/meta/recipes-core/glibc/glibc_2.39.bb
> @@ -18,7 +18,7 @@ easier access for another. 'ASLR bypass itself is not a vulnerability.'"
>
> CVE_STATUS_GROUPS += "CVE_STATUS_STABLE_BACKPORTS"
> CVE_STATUS_STABLE_BACKPORTS = "CVE-2024-2961 CVE-2024-33599 CVE-2024-33600 CVE-2024-33601 CVE-2024-33602 CVE-2025-0395 \
> - CVE-2025-4802 CVE-2025-5702 CVE-2025-8058"
> + CVE-2025-4802 CVE-2025-5702 CVE-2025-8058 CVE-2025-15281 CVE-2026-0861 CVE-2026-0915"
> CVE_STATUS_STABLE_BACKPORTS[status] = "cpe-stable-backport: fix available in used git hash"
>
> DEPENDS += "gperf-native bison-native"
--
Yoann Congal
Smile ECS
next prev parent reply other threads:[~2026-02-05 17:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 16:16 [OE-core][scarthgap][PATCH] glibc: stable 2.39 branch updates Peter Marko
2026-02-05 17:08 ` Yoann Congal [this message]
2026-02-08 15:18 ` Marko, Peter
2026-02-06 5:24 ` [scarthgap][PATCH] " Hemanth.KumarMD
2026-02-06 6:47 ` [OE-core] " Yoann Congal
2026-02-06 7:42 ` Marko, Peter
2026-02-06 10:19 ` Richard Purdie
2026-02-06 8:19 ` Hemanth Kumar M D
2026-02-06 9:43 ` Yoann Congal
-- strict thread matches above, loose matches on Subject: below --
2025-10-07 6:31 Deepesh.Varatharajan
2025-10-07 21:30 ` [OE-core] " Khem Raj
2025-10-13 5:43 ` Deepesh Varatharajan
2025-10-13 6:11 ` Khem Raj
2025-07-21 12:23 Deepesh.Varatharajan
2025-07-22 1:38 ` [OE-core] " Khem Raj
2025-06-17 21:11 [OE-core][scarthgap][PATCH] " Peter Marko
2025-05-01 3:03 [scarthgap][PATCH] " Deepesh.Varatharajan
2025-05-01 5:54 ` [OE-core] " Khem Raj
2025-05-02 3:15 ` Deepesh Varatharajan
2025-05-02 3:25 ` Khem Raj
2025-05-02 10:34 ` Randy MacLeod
2025-05-05 4:06 ` Deepesh Varatharajan
2025-02-02 15:52 [OE-core][scarthgap][PATCH] " Peter Marko
2024-09-29 16:18 [scarthgap][PATCH] " Deepesh.Varatharajan
2024-09-29 16:59 ` [OE-core] " Khem Raj
2024-05-17 16:22 sundeep.kokkonda
2024-05-17 16:33 ` Sundeep KOKKONDA
2024-05-17 16:48 ` [OE-core] " Khem Raj
2024-05-17 16:53 ` Marko, Peter
2024-05-17 21:09 ` Steve Sakoman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DG76ZND24N16.1FFJG987M3ZUU@smile.fr \
--to=yoann.congal@smile.fr \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.marko@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox