Monday Patch Queue Review update (2026-07-13)

Carlos O'Donell <[email protected]>
Newsgroups gmane.comp.lib.glibc.alpha
Organization Red Hat, LLC.
Message-ID <[email protected]>
Most recent meeting status is always here:
https://sourceware.org/glibc/wiki/PatchworkReviewMeetings#Update

Meeting: 2026-07-13 @ 0900h EST5EDT

Video/Audio: https://bbb.linuxfoundation.org/room/adm-alk-1uu-7fu

IRC: #glibc on OFTC.

​ * Upstream glibc 2.44 release.
  * Review release blockers.
  * [v2] posix: Fix wordexp WRDE_APPEND to preserve state on non-NOSPACE errors (BZ 34090, CVE-2026-6368) (Adhemerval)
   * Changes requested (reviewed by DJ).
  * Discussed 3 CVEs to fix for the release.
  * One is fixed. One is under review. The last one needs some final work.
  * This issue has security+ https://sourceware.org/bugzilla/show_bug.cgi?id=31026
  * elf: Remove dead l_need_tls_init static-TLS init path (Adhemerval)
   * Postponed to next release.
  * linux: Inline syscall cancellation to keep wrapper frames observable (BZ 34338) (Adhmerval)
   * Still under review by Wilco. Carlos reached out to check on review.
  * Fixes for the system-wide tunables support (Adhemerval)
   * Preparing to push to the branch.
  * benchtests: Build benchmarks in parallel (Adhemerval)
   * Accepted by RM (Andreas)
  * sparc: Fix static (non-PIE) executables when PIE is enabled by default (Adhemveral)
   * Accepted by RM (Andreas)
  * [v2] Add RWF_NOSIGNAL from Linux 6.18 to bits/uio-ext.h (Adhemerval)
   * Reviewer Pool: Carlos O'Donell
  * [v2] Use correct type for glibc.malloc.perturb in tst-tunconf1.c (Stefan)
   * Reviewer: Andreas Huettel
  * Made it through blockers and desirable for the release.
  * Made it through a review of the current machine failures.
  * Noted that https://sourceware.org/glibc/wiki/Testing/Tests/resolv/tst-resolv-res_init-failure is an odd failure with xaccept failing EMFILE but depends on system limits. Not clera why the test would hit the limits.

-- 
Cheers,
Carlos.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.