git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff Hostetler <git@jeffhostetler.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Rose via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Seija <doremylover123@gmail.com>
Subject: Re: [PATCH] maintenance: compare output of pthread functions for inequality with 0
Date: Fri, 2 Dec 2022 13:44:30 -0500	[thread overview]
Message-ID: <d4a5bd6e-77bd-eb63-5c7f-8f3d46cc0418@jeffhostetler.com> (raw)
In-Reply-To: <221202.86k039fz7x.gmgdl@evledraar.gmail.com>



On 12/2/22 1:10 PM, Ævar Arnfjörð Bjarmason wrote:
> 
> On Fri, Dec 02 2022, Rose via GitGitGadget wrote:
> 
>> From: Seija <doremylover123@gmail.com>
>>
>> The documentation for pthread_create and pthread_sigmask state that:
>>
>> "On success, pthread_create() returns 0;
>> on error, it returns an error number"
>>
>> As such, we ought to check for an error
>> by seeing if the output is not 0.
>>
>> Checking for "less than" is a mistake
>> as the error code numbers can be greater than 0.
>>
>> Signed-off-by: Seija <doremylover123@gmail.com>
>> ---
>>      maintenance: compare output of pthread functions for inequality with 0
>>      
>>      The documentation for pthread_create and pthread_sigmask state that "On
>>      success, pthread_create() returns 0; on error, it returns an error
>>      number, and the contents of *thread are undefined."
>>      
>>      As such, we ought to check for an error by seeing if the output is not
>>      0, rather than being less than 0, since nothing stops these functions
>>      from returning a positive number.
>>      
>>      Signed-off by: Seija doremylover123@gmail.com
>>
>> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1389%2FAtariDreams%2Faddress-v1
>> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1389/AtariDreams/address-v1
>> Pull-Request: https://github.com/git/git/pull/1389
>>
>>   builtin/fsmonitor--daemon.c | 4 ++--
>>   run-command.c               | 2 +-
>>   2 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/builtin/fsmonitor--daemon.c b/builtin/fsmonitor--daemon.c
>> index 6f30a4f93a7..52a08bb3b57 100644
>> --- a/builtin/fsmonitor--daemon.c
>> +++ b/builtin/fsmonitor--daemon.c
>> @@ -1209,7 +1209,7 @@ static int fsmonitor_run_daemon_1(struct fsmonitor_daemon_state *state)
>>   	 * events.
>>   	 */
>>   	if (pthread_create(&state->listener_thread, NULL,
>> -			   fsm_listen__thread_proc, state) < 0) {
>> +			   fsm_listen__thread_proc, state)) {
>>   		ipc_server_stop_async(state->ipc_server_data);
>>   		err = error(_("could not start fsmonitor listener thread"));
>>   		goto cleanup;
>> @@ -1220,7 +1220,7 @@ static int fsmonitor_run_daemon_1(struct fsmonitor_daemon_state *state)
>>   	 * Start the health thread to watch over our process.
>>   	 */
>>   	if (pthread_create(&state->health_thread, NULL,
>> -			   fsm_health__thread_proc, state) < 0) {
>> +			   fsm_health__thread_proc, state)) {
>>   		ipc_server_stop_async(state->ipc_server_data);
>>   		err = error(_("could not start fsmonitor health thread"));
>>   		goto cleanup;
>> diff --git a/run-command.c b/run-command.c
>> index 48b9ba6d6f0..756f1839aab 100644
>> --- a/run-command.c
>> +++ b/run-command.c
>> @@ -1019,7 +1019,7 @@ static void *run_thread(void *data)
>>   		sigset_t mask;
>>   		sigemptyset(&mask);
>>   		sigaddset(&mask, SIGPIPE);
>> -		if (pthread_sigmask(SIG_BLOCK, &mask, NULL) < 0) {
>> +		if (pthread_sigmask(SIG_BLOCK, &mask, NULL)) {
>>   			ret = error("unable to block SIGPIPE in async thread");
>>   			return (void *)ret;
>>   		}
>>
>> base-commit: 805265fcf7a737664a8321aaf4a0587b78435184
> 
> This looks good to me, and skimming through the rest of the
> pthread_create() it seems the rest of the code in-tree is correct.
> 
> But (and especially if you're interested) we really should follow-up
> here and fix the "error()" etc. part of this. After this we have cases
> in-tree where we on failure:

But to be clear, the pthread_ changes are good by themselves and can
be considered a single task that could be advanced without any
extra stuff.

All of the following, if of interest to you or anyone else, should
be done in one or more separate/later and independent series.

> 
>   * Call die_errno() (good)
>   * Call die(), error() etc., but with a manual strerror() argument,
>     these should just use the *_errno() helper.
>   * Don't report on the errno at all, e.g. in this case shown here.
> 
> It seems to me that all of these should be using die_errno(),
> error_errno() etc.
> 
> Or maybe it's the other way around, and we should not rely on the global
> "errno", but always capture the return value, and give that to
> strerror() (or set "errno = ret", and call {die,error,warning}_errno()).
> 
> In any case, some low-hanging #leftoverbits there...
> 

  reply	other threads:[~2022-12-02 18:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 17:02 [PATCH] maintenance: compare output of pthread functions for inequality with 0 Rose via GitGitGadget
2022-12-02 18:05 ` Jeff Hostetler
2022-12-02 18:10 ` Ævar Arnfjörð Bjarmason
2022-12-02 18:44   ` Jeff Hostetler [this message]
2022-12-02 20:55   ` brian m. carlson
2022-12-02 22:46     ` Ævar Arnfjörð Bjarmason
2022-12-03  0:26       ` brian m. carlson

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

  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 \
    --in-reply-to=d4a5bd6e-77bd-eb63-5c7f-8f3d46cc0418@jeffhostetler.com \
    --to=git@jeffhostetler.com \
    --cc=avarab@gmail.com \
    --cc=doremylover123@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).