From: "Yoann Congal" <yoann.congal@smile.fr>
To: "Jaipaul Cheernam" <jaipaul.cheernam@est.tech>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [scarthgap][PATCH] glibc: stable 2.39 branch updates
Date: Fri, 17 Jul 2026 18:25:58 +0200 [thread overview]
Message-ID: <DK0ZJ5IO54TT.CA3QAFDIJBI9@smile.fr> (raw)
In-Reply-To: <DU7PPF66507B2D7CF934D9C435C88A84E13F3C62@DU7PPF66507B2D7.EURP189.PROD.OUTLOOK.COM>
On Fri Jul 17, 2026 at 6:01 PM CEST, Jaipaul Cheernam wrote:
>
> Hi Yoann,
>
> May I know did you get a chance to review this patch and another patch for glibc from me ?
Not yet, but it is in the review list, I'll get to it (next week
probably).
FYI, scarthgap merge is directly slowed down by this bug:
15289 – [scarthgap] AB-INT: sstatetests.SStatePrintdiff.test_gcc_runtime_vs_gcc_source failure
https://bugzilla.yoctoproject.org/show_bug.cgi?id=15289#c41
... as an example as to why the project is asking for help fixing the
AB-INT issues.
Regards,
>
> Regards,
> Jaipaul
>
> ________________________________
> From: Jaipaul Cheernam
> Sent: Wednesday, July 8, 2026 2:01 PM
> To: openembedded-core@lists.openembedded.org <openembedded-core@lists.openembedded.org>
> Cc: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
> Subject: [scarthgap][PATCH] glibc: stable 2.39 branch updates
>
> git log --oneline ce65d944e38a20cb70af2a48a4b8aa5d8fabe1cc..be1e627cd72db31161a3b4ce1c8114674f0895eb
> be1e627cd7 Linux: Only define OPEN_TREE_* macros in <sys/mount.h> if undefined (bug 33921)
> 98bc06a361 include: isolate __O_CLOEXEC flag for sys/mount.h and fcntl.h
> 3e13579841 Use pending character state in IBM1390, IBM1399 character sets (CVE-2026-4046)
> 0dc95ae109 elf: parse /proc/self/maps as the last resort to find the gap for tst-link-map-contiguous-ldso
> 9344c796f7 resolv: Check hostname for validity (CVE-2026-4438)
> 5663ab0b83 resolv: Count records correctly (CVE-2026-4437)
> c53cd6e738 posix: Run tst-wordexp-reuse-mem test
> 2760e4c5ed iconvdata: Fix invalid pointer arithmetic in ANSI_X3.110 module
> ba29a36aa3 posix: Fix invalid flags test for p{write,read}v2
> 60b039bf6a socket: Add new test for shutdown
>
> Testing Results:
> Before After Diff
> PASS 4892 4896 +4
> XPASS 4 4 0
> FAIL 371 372 +1
> XFAIL 16 16 0
> UNSUPPORTED 224 224 0
>
> Changes in testcases:
>
> testcase-name before after
> posix/tst-wordexp-reuse-mem(new) - PASS (native)
>
> [Note: posix/tst-wordexp-reuse-mem is a new test added by this uplift
> (c53cd6e738). It fails under QEMU user-mode because the test-wrapper
> cannot support LD_PRELOAD and MALLOC_TRACE needed for mtrace. Running
> natively with LD_PRELOAD=libc_malloc_debug.so confirms the test passes
> with no memory leaks.
>
> nptl/tst-getpid3 is a flaky test under QEMU user-mode (passes 7/10
> re-runs). No nptl code was changed in this uplift.]
>
> Signed-off-by: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
> ---
> meta/recipes-core/glibc/glibc-version.inc | 2 +-
> meta/recipes-core/glibc/glibc_2.39.bb | 3 ++-
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-core/glibc/glibc-version.inc b/meta/recipes-core/glibc/glibc-version.inc
> index 03a8e5d01e..5d57dafed0 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 ?= "ce65d944e38a20cb70af2a48a4b8aa5d8fabe1cc"
> +SRCREV_glibc ?= "be1e627cd72db31161a3b4ce1c8114674f0895eb"
> 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 7958d64eed..f6be1b5fc9 100644
> --- a/meta/recipes-core/glibc/glibc_2.39.bb
> +++ b/meta/recipes-core/glibc/glibc_2.39.bb
> @@ -18,7 +18,8 @@ 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-15281 CVE-2026-0861 CVE-2026-0915"
> + CVE-2025-4802 CVE-2025-5702 CVE-2025-8058 CVE-2025-15281 CVE-2026-0861 CVE-2026-0915 \
> + CVE-2026-4046 CVE-2026-4437 CVE-2026-4438"
> CVE_STATUS_STABLE_BACKPORTS[status] = "cpe-stable-backport: fix available in used git hash"
>
> DEPENDS += "gperf-native bison-native"
> --
> 2.34.1
--
Yoann Congal
Smile ECS
next prev parent reply other threads:[~2026-07-17 16:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 12:01 [scarthgap][PATCH] glibc: stable 2.39 branch updates Jaipaul Cheernam
2026-07-17 16:01 ` Jaipaul Cheernam
2026-07-17 16:25 ` Yoann Congal [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-25 16:16 [OE-core][scarthgap][PATCH] " Peter Marko
2026-02-06 5:24 ` [scarthgap][PATCH] " Hemanth.KumarMD
2025-10-07 6:31 Deepesh.Varatharajan
2025-07-21 12:23 Deepesh.Varatharajan
2025-05-01 3:03 Deepesh.Varatharajan
2024-11-25 8:01 Deepthi.Hemraj
2024-11-25 16:13 ` Khem Raj
2024-09-29 16:18 Deepesh.Varatharajan
2024-07-19 8:28 Deepthi.Hemraj
2024-05-17 16:22 sundeep.kokkonda
2024-05-17 16:33 ` Sundeep KOKKONDA
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=DK0ZJ5IO54TT.CA3QAFDIJBI9@smile.fr \
--to=yoann.congal@smile.fr \
--cc=jaipaul.cheernam@est.tech \
--cc=openembedded-core@lists.openembedded.org \
/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