From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>,
Joe Simmons-Talbott <josimmon@redhat.com>,
Stefan Liebler <stli@linux.ibm.com>
Subject: Monday Patch Queue Review update (2023-10-02)
Date: Mon, 2 Oct 2023 10:03:35 -0400 [thread overview]
Message-ID: <96ce5fdf-8965-a6a2-be79-2fa7294b519d@redhat.com> (raw)
Most recent meeting status is always here:
https://sourceware.org/glibc/wiki/PatchworkReviewMeetings#Update
Meeting: 2023-10-02 @ 0900h EST5EDT
Video/Audio: https://bbb.linuxfoundation.org/room/adm-alk-1uu-7fu
IRC: #glibc on OFTC.
Review new patches and restart review at the top.
* State NEW delegate NOBODY at 486 patches.
* Carlos's SLI at 187.46138211382114 days average patch age in queue and 92231 accumulated patch days.
* Starting at 76972
* Consolidate NSS functionality into nss subdir (Arjun)
* Arjun: Couldn't measure any specific improvements.
* Arjun: All of the NSS entry points will go into a static archive for static applications to avoid dlopen().
* From a review perspective it's all Makefile changes.
* Arjun: Looking for broader consensus.
* Adhemerval: The idea is to remove the dlopen in the static case?
* Adhemerval: If you apply this, what is the missing link?
* Arjun: To create a whole set of static built entry points and to conceptually make the nss/ subdirectory have all those entry points.
* Cover letter: https://sourceware.org/pipermail/libc-alpha/2023-October/151854.html
* files and dns are part of libc.a, and we use those already.
* Looking for others to review the concept and provide feedback.
* 76941: Remove libcrypt support (Adhemerval)
* Carlos to review for removal.
* 76885: elf: Get rid of alloca usage in _dl_start_profile (Joe)
* Needs review. How did you test this?
* Need to build with profiling on and test LD_PROFILE?
* Did you test the scratch buffer triggering malloc()?
* 76855: [RFC] linux: Use fchmodat2 on fchmod for flags different than 0 (BZ 26401) (Adhemerval)
* CI failure related to old seccomp failure (or AppArmor).
* Florian sees this is good. Need to wait for 6.6.
* 76847: [v2] nss: Get rid of alloca usage in makedb's write_output. (Joe)
* Should be straight forward for makedb writing output.
* 76835: [v3] nss: Get rid of alloca usage in db-XXX (Joe)
* Should also be straight forward to review.
* 76831: Fix WAIT_FOR_DEBUGGER for container tests. (Stefan)
* Carlos to review.
* 76816: [v3] Linux: add ST_NOSYMFOLLOW (Kir)
* Adhemerval to push commit.
* 76811: [RFC] pthread_create: Name stacks in /proc/<pid>/maps (Ian)
* What are the performance implications?
* Carlos to ask Ian to post a versioned RFC.
* Stopping 76764.
* Carlos noted we should commit 59588.
* Adhemerval: Need review for pthread cancellation fixes.
--
Cheers,
Carlos.
reply other threads:[~2023-10-02 14:05 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=96ce5fdf-8965-a6a2-be79-2fa7294b519d@redhat.com \
--to=carlos@redhat.com \
--cc=josimmon@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=stli@linux.ibm.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).