public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dilfridge at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/29039] Corrupt DTV after reuse of a TLS module ID following dlclose with unused TLS
Date: Fri, 22 Dec 2023 14:57:25 +0000 [thread overview]
Message-ID: <bug-29039-131-qRPGsB2Iig@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29039-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29039
Andreas K. Huettel <dilfridge at gentoo dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dilfridge at gentoo dot org
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-12-22 14:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 5:36 [Bug dynamic-link/29039] New: _dl_tlsdesc_dynamic (sometimes) returns garbage offsets alex_y_xu at yahoo dot ca
2022-04-10 9:46 ` [Bug dynamic-link/29039] " evangelos at foutrelis dot com
2022-04-10 14:34 ` alex_y_xu at yahoo dot ca
2022-04-12 11:27 ` fweimer at redhat dot com
2022-04-12 15:18 ` alex_y_xu at yahoo dot ca
2022-05-17 20:20 ` j at bitron dot ch
2023-11-26 14:16 ` sam at gentoo dot org
2023-11-26 14:17 ` sam at gentoo dot org
2023-11-28 10:12 ` [Bug dynamic-link/29039] Corrupt DTV after reuse of a TLS module ID following dlclose with unused TLS fweimer at redhat dot com
2023-11-28 17:29 ` cvs-commit at gcc dot gnu.org
2023-12-20 8:46 ` cvs-commit at gcc dot gnu.org
2023-12-22 14:43 ` sam at gentoo dot org
2023-12-22 14:57 ` dilfridge at gentoo dot org [this message]
2023-12-22 16:58 ` cvs-commit at gcc dot gnu.org
2023-12-22 16:58 ` cvs-commit at gcc dot gnu.org
2023-12-22 16:59 ` cvs-commit at gcc dot gnu.org
2023-12-22 16:59 ` cvs-commit at gcc dot gnu.org
2023-12-22 17:00 ` cvs-commit at gcc dot gnu.org
2023-12-22 17:00 ` cvs-commit at gcc dot gnu.org
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=bug-29039-131-qRPGsB2Iig@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).