git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff Hostetler <git@jeffhostetler.com>
To: Rose via GitGitGadget <gitgitgadget@gmail.com>, git@vger.kernel.org
Cc: Rose <83477269+AtariDreams@users.noreply.github.com>,
	Seija <doremylover123@gmail.com>
Subject: Re: [PATCH] maintenance: compare output of pthread functions for inequality with 0
Date: Fri, 2 Dec 2022 13:05:32 -0500	[thread overview]
Message-ID: <34ed06a2-9c67-62d5-7985-4b7379a0cf6c@jeffhostetler.com> (raw)
In-Reply-To: <pull.1389.git.git.1670000578395.gitgitgadget@gmail.com>



On 12/2/22 12:02 PM, 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

Good catch!

LGTM

Thanks,
Jeff


  reply	other threads:[~2022-12-02 18:05 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 [this message]
2022-12-02 18:10 ` Ævar Arnfjörð Bjarmason
2022-12-02 18:44   ` Jeff Hostetler
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=34ed06a2-9c67-62d5-7985-4b7379a0cf6c@jeffhostetler.com \
    --to=git@jeffhostetler.com \
    --cc=83477269+AtariDreams@users.noreply.github.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).