unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Monday Patch Queue Review update (2021-09-13)
Date: Mon, 13 Sep 2021 09:54:56 -0400	[thread overview]
Message-ID: <7d4558f7-320a-54db-555d-e86a62e1f5e5@redhat.com> (raw)

Most recent meeting status is always here:
https://sourceware.org/glibc/wiki/PatchworkReviewMeetings#Update

Meeting: 2021-09-13 @ 0900h EST (UTC-5)

Video/Audio: https://bluejeans.com/9093064454

IRC: #glibc on OFTC.

Review new patches and restart review at the top.

 * 334 patches to review.
 * 44860 [v2] nptl: Fix type of pthread_mutexattr_getrobust_np, pthread_mutexattr_setrobust_np (bug 28036)
   * Carlos will review.
 * Florian got feedback on pthread_cancel ESRCH changes.
   * Pushed to master and relase/2.34/master.
 * sysconf revert patches?
   * Florian reviewed the patches.
   * Final patches have some issues in the test case.
   * The rest is OK.
 * Siddhesh has a couple of locale realted patches that need review.
   * 44430 - v2 setlocale needs review (codonell)
   * 44607 - iconvconfig: Fix behaviour with --prefix [BZ #28199] (arjun)
 * Carlos to raise locale source file header review with Mike Frysinger.
   * Attempt to get consensus on default headers to use.
 * Szabolcs: No patches, but regression report of the latest glibc release has dynamic tls fixes.
   * Introduced a new lock in pthread_create.
   * Florian: Can we get a new lock?
   * The problem: Thread A: rtld lock -> user lock, B: user lock -> rtld lock. Deadlock.
   * https://sourceware.org/bugzilla/show_bug.cgi?id=15686
     * Fix for dyanmic tls bug fix regression.
   * Report: https://sourceware.org/bugzilla/show_bug.cgi?id=19329#c39
 * Carlos is looking to review 2767
   * https://patchwork.sourceware.org/project/glibc/list/?series=2767
   * Reports that dotnet runtime is impacted by this on Linux.
 * C.UTF-8 is in master, but will not be backported to release/2.34/master due to distribution impact.
   * Distros can either pick it up manually, or when 2.35 releases.
 * RISC-V looking at extending this to 4K vector.
   * Arm SVE is passing down linked-list kind of structure that links up the extensions.
   * Kernel dumps register states on the stack.
   * Headers point to extra register state.
   * AT_MINSIGSTKSZ is used there.
   * Florian will post a note about the Arm SVE case as an example to review.
 * 44926 - [v9,1/1] Extend struct r_debug to support multiple namespaces [BZ #15971]
   * Florian to review.
 * 44924 - [v2] posix: Fix attribute access mode on getcwd [BZ #27476]
   * Florain to review (since he reviewed v1)
 * 44897 -  Add MADV_POPULATE_READ and MADV_POPULATE_WRITE from Linux 5.14 to bits/mman-linux.h
   * https://patchwork.sourceware.org/project/glibc/patch/alpine.DEB.2.22.394.2109072123510.1731265@digraph.polyomino.org.uk/
   * Asking DJ for review.
 * 32-bit Arm atomic issue.
   * https://sourceware.org/pipermail/libc-help/2021-September/006004.html
   * Needs resolving in atomic.h.
 * Stopped at 44884.

-- 
Cheers,
Carlos.


                 reply	other threads:[~2021-09-13 13:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7d4558f7-320a-54db-555d-e86a62e1f5e5@redhat.com \
    --to=libc-alpha@sourceware.org \
    --cc=carlos@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).