public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "robin at gareus dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/29214] pthread_setcanceltype fails to set type
Date: Wed, 01 Jun 2022 01:41:19 +0000 [thread overview]
Message-ID: <bug-29214-131-FgP9ZcBrGP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29214-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29214
--- Comment #5 from Robin Gareus <robin at gareus dot org> ---
> The problem seems not to be on pthread_setcanceltype, but rather on nptl/libc-clenaup.c that implements handlers used by printf.
The issue is also present with a direct call, without printf() or checking the
return value.
Regardless, the patch fixes this as well.
> Well, I was the one that actually messed up the revert ;)
No shame in that, it happens to the best.
404656009b459658138ed1bd18f3c6cf3863e6a6 is a large complex commit as well.
It's really distros who are to blame for shipping somewhat random git non
tagged git revision. Then again arch users asked for it :)
debian/sid, ubuntu use 2.35 tagged release and are not affected.
Keep up the good work!
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-06-01 1:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 17:19 [Bug nptl/29214] New: " robin at gareus dot org
2022-05-31 18:45 ` [Bug nptl/29214] " adhemerval.zanella at linaro dot org
2022-05-31 18:56 ` adhemerval.zanella at linaro dot org
2022-05-31 19:12 ` robin at gareus dot org
2022-05-31 19:16 ` adhemerval.zanella at linaro dot org
2022-06-01 1:41 ` robin at gareus dot org [this message]
2022-06-08 12:36 ` adhemerval.zanella at linaro dot 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-29214-131-FgP9ZcBrGP@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).