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

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-06 @ 0900h EST5EDT

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

IRC: #glibc on OFTC.

​ * Release planning is in effect and we are reviewing blockers and desirables.
  * Discussed entering Freeze and machine testing.
  * Carlos: I'm going to be testing x86_64, i686, s390x, aarch64, and ppc64le.
  * Andreas: ppc64le (POWER9, BE/LE), SPARC, and others.
  * Adehemerval: Need to check if I have machine access to SPARC boxes.
  * Carlos: Note cfarm has loognarch64 and mips64 for testing too.
  * Andreas: For hppa there is https://static.matoro.tk/isa-sandbox-faq.html
  * s390: Prevent hoisting the thread-pointer read in THREAD_SET_STACK_GUARD (BZ 34297) (Adhemerval)
   * Accepted by Stefan Liebler (IBM) as machine maintainer.
   * Please push.
  * [v2] posix: Fix wordexp WRDE_APPEND to preserve state on non-NOSPACE errors (BZ 34090, CVE-2026-6368) (Adhemerval)
   * Needs review.
  * elf: Remove dead l_need_tls_init static-TLS init path (Adhemerval)
   * Still under review by Florian.
  * Discussed malloc ifunc issues.
  * Yury: We have two options, one to define USE_MULTIARCH_MALLOC to allow distributions to disable.
  * Andreas: We apply the revert patch now, and undo it immediately after the release?
  * Adhemerval: Does Valgrind work?
  * Carlos: https://bugs.kde.org/show_bug.cgi?id=522497
  * Agreed to revert the malloc ifunc and then put it back after the patch.
  * linux: Inline syscall cancellation to keep wrapper frames observable (BZ 34338) (Adhemerval)
   * Discussed the pros and cons.
   * Andreas: Add this in after the release?
   * Reviewer Pool: Wilco

-- 
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.