From: Jeff Hostetler <email@example.com>
To: Jeff King <firstname.lastname@example.org>,
Jeff Hostetler via GitGitGadget <email@example.com>
Cc: "Jeff Hostetler" <firstname.lastname@example.org>,
"Nguyễn Thái Ngọc Duy" <email@example.com>,
firstname.lastname@example.org, "Junio C Hamano" <email@example.com>
Subject: Re: [PATCH 0/1] trace2: fix tracing when NO_PTHREADS is defined
Date: Wed, 22 May 2019 09:23:39 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 5/21/2019 5:27 PM, Jeff King wrote:
> On Tue, May 21, 2019 at 12:33:58PM -0700, Jeff Hostetler via GitGitGadget wrote:
>> As Duy suggested, pthread_getspecific() just returns NULL when NO_PTHREADS
>> is defined. And pthread_setspecific() silently does not nothing. So this
>> problem was hidden from view.
>> I have to wonder if we should update pthread_*specific() to call BUG() when
>> NO_PTHREADS is defined as a way to catch unguarded usages easier or make
>> this issue more clear.
> I think it should actually store the data asked for by the caller, as if
> we were the single thread running. We discussed this as the time of
> refactoring NO_PTHREADS, but there was only one caller that would have
> benefited. Now there are two. ;)
> Discussion in the subthread of this patch:
I was wondering about that too as the proper long term solution.
We would need (as the discussion suggests ) to properly
respect/represent the pthread_key_t argument.
For now, I've guarded my usage of pthread_getspecific() in the trace2
(similar to what index-pack does), so its not urgent that we update it.
And I'd rather we take this simple trace2 fix now and not try to combine
it with fixes for the pthread macros. Especially now as we're in the RC
cycle for 2.22.
I'll make a note to revisit the pthread code after 2.22.
next prev parent reply other threads:[~2019-05-22 13:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 19:33 [PATCH 0/1] trace2: fix tracing when NO_PTHREADS is defined Jeff Hostetler via GitGitGadget
2019-05-21 19:33 ` [PATCH 1/1] " Jeff Hostetler via GitGitGadget
2019-05-21 21:27 ` [PATCH 0/1] " Jeff King
2019-05-22 13:23 ` Jeff Hostetler [this message]
2019-05-23 5:51 ` Jeff King
2019-05-23 13:55 ` Jeff Hostetler
2019-05-25 10:43 ` Duy Nguyen
2019-05-28 6:28 ` Jeff King
2019-05-28 14:57 ` Jeff Hostetler
2019-05-28 17:14 ` Junio C Hamano
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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).