From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Monday Patch Queue Review update (2023-03-06)
Date: Mon, 6 Mar 2023 09:58:31 -0500 [thread overview]
Message-ID: <35eaeca3-25e7-ff03-13f2-468c84d83678@redhat.com> (raw)
Most recent meeting status is always here:
https://sourceware.org/glibc/wiki/PatchworkReviewMeetings#Update
Meeting: 2023-03-06 @ 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 is at 214 patches.
- Carlos' SLI at 161 days.
- Discussed "[v3,2/4] libio: Remove the usage of __libc_IO_vtables"
- Decision is to rely on existing regression test suite.
- Concerned with static link issues that don't bring in everything.
- v4 needed to fix the typo in "_IO_file_jumps_alia"
- What about "pragma weak" for _IO_default_* functions?
- libio_static_fn_required (defined at libio/libioP.h)
- Carlos: What pulls in libio/genops.c? Pulled in by _IO_un_link?
- Florian's suggestion is to remove pragma weak for _IO_default.
- Why does LD_PRELOAD not work with RTLD_DEEPBIND?
- Already had a WONTFIX bug for that.
- https://sourceware.org/bugzilla/show_bug.cgi?id=25533
- https://sourceware.org/bugzilla/show_bug.cgi?id=30186
- Carlos raised the issue of Message-ID's with slashes in them.
- Siddhesh: Yes we do have the fix in patchwork, but it looks incomplete.
- https://github.com/getpatchwork/patchwork/issues/518
- [v3] elf: Fix slow tls access after dlopen [BZ #19924] (Szabolcs)
- Needs review for P&C issues.
--
Cheers,
Carlos.
reply other threads:[~2023-03-06 14:58 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=35eaeca3-25e7-ff03-13f2-468c84d83678@redhat.com \
--to=carlos@redhat.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).