From: Junio C Hamano <gitster@pobox.com>
To: "AZero13 via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, AZero13 <gfunni234@gmail.com>
Subject: Re: [PATCH] open: check fd_flags value before calling fcntl
Date: Thu, 18 Dec 2025 12:45:29 +0900 [thread overview]
Message-ID: <xmqqldj0xxk6.fsf@gitster.g> (raw)
In-Reply-To: <pull.2131.git.git.1766027643744.gitgitgadget@gmail.com> (AZero's message of "Thu, 18 Dec 2025 03:14:03 +0000")
"AZero13 via GitGitGadget" <gitgitgadget@gmail.com> writes:
> From: AZero13 <gfunni234@gmail.com>
>
> Otherwise, fcntl can be called with invalid fd_flags.
This somehow feels mischaracterised. The intent of the code is
already to check the current flags value using getfd and or-in the
cloexec bit to call setfd. What this patch fixes is to handle
a failed getfd case correctly.
Subject: git_open_cloexec(): handle failing F_GETFD
Before using F_SETFD to add in fd_cloexec bit, the code uses
F_GETFD to see the current set of flags. As it does not pay
attention to potential failures, F_SETFD may be called with a
set of invalid fcntl bits.
Continue without calling F_SETFD and behave the same way as the
case where F_SETFD failed, when the initial F_GETFD failed.
or something like that, perhaps?
> Signed-off-by: Greg Funni <gfunni234@gmail.com>
The in-body "From: AZer..." line we see above should say "From: Greg..."
instead. Set "git config set user.name 'Greg Funni'" in the repository
you use to contribute to this project, amend the commit so that it will
record "Greg..." instead of "AZer..." as its author, and force push
to GGG and tell GGG to send out the email, perhaps?
> ---
> open: check fd_flags value before calling fcntl
>
> Otherwise, fcntl can be called with invalid fd_flags.
>
> Signed-off-by:Greg Funni gfunni234@gmail.com
>
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2131%2FAZero13%2Ffixopen-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2131/AZero13/fixopen-v1
> Pull-Request: https://github.com/git/git/pull/2131
>
> compat/open.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/compat/open.c b/compat/open.c
> index 37ae2b1aeb..b313bcd364 100644
> --- a/compat/open.c
> +++ b/compat/open.c
> @@ -44,8 +44,8 @@ int git_open_cloexec(const char *name, int flags)
>
> if (!o_cloexec && 0 <= fd && fd_cloexec) {
> /* Opened w/o O_CLOEXEC? try with fcntl(2) to add it */
> - int flags = fcntl(fd, F_GETFD);
> - if (fcntl(fd, F_SETFD, flags | fd_cloexec))
> + int fd_flags = fcntl(fd, F_GETFD);
> + if (fd_flags < 0 || fcntl(fd, F_SETFD, fd_flags | fd_cloexec))
> fd_cloexec = 0;
> }
> }
>
> base-commit: c4a0c8845e2426375ad257b6c221a3a7d92ecfda
prev parent reply other threads:[~2025-12-18 3:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 3:14 [PATCH] open: check fd_flags value before calling fcntl AZero13 via GitGitGadget
2025-12-18 3:45 ` Junio C Hamano [this message]
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=xmqqldj0xxk6.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=gfunni234@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.
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 NNTP newsgroup(s).