From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH v4] elf: Avoid deadlock between pthread_create and ctors [BZ #28357]
Date: Fri, 1 Oct 2021 13:43:07 -0300 [thread overview]
Message-ID: <9b12d672-64c2-5d3d-367d-1b85503dce37@linaro.org> (raw)
In-Reply-To: <20211001163326.3423517-1-szabolcs.nagy@arm.com>
On 01/10/2021 13:33, Szabolcs Nagy wrote:
> Fixes bug 28357.
>
> Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
> ---
> i will commit this next week if there are no further comments.
>
> v4:
> - fix the test too (except use 1 instead of STDOUT_FILENO
> that would need another header and more verbose).
Does it really matter to be more verbose and require another
header? This is not really a blocker, but I am not seeing
why being so condensed is really a goal here.
next prev parent reply other threads:[~2021-10-01 16:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 16:33 Szabolcs Nagy
2021-10-01 16:43 ` Adhemerval Zanella [this message]
2021-10-04 13:00 ` Szabolcs Nagy
2022-02-02 14:31 ` Andreas Schwab
2022-02-02 14:41 ` Szabolcs Nagy
2022-02-02 15:13 ` Andreas Schwab
2022-02-02 15:17 ` Andreas Schwab
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=9b12d672-64c2-5d3d-367d-1b85503dce37@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=szabolcs.nagy@arm.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).