From: Junio C Hamano <gitster@pobox.com>
To: Michael J Gruber <git@grubix.eu>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] http.c: avoid gcc warning
Date: Fri, 06 May 2022 13:22:59 -0700 [thread overview]
Message-ID: <xmqqtua2jtr0.fsf@gitster.g> (raw)
In-Reply-To: <3f0e462e86625a3c253653e4a4eefabcd8590bf9.1651859773.git.git@grubix.eu> (Michael J. Gruber's message of "Fri, 6 May 2022 20:04:06 +0200")
Michael J Gruber <git@grubix.eu> writes:
See previous discussion on the topic and help clarify it for me,
thanks.
https://lore.kernel.org/git/xmqqo8131tr8.fsf@gitster.g/
> Related to -Wdangling-pointer.
>
> In fact, this use of the pointer looks scary and has not created
> problems so far only because the pointer in the struct is not used when
> execution is out of the scope of the local function (and the pointer
> invalid).
>
> Signed-off-by: Michael J Gruber <git@grubix.eu>
> ---
> http.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/http.c b/http.c
> index 229da4d148..2f67fbb33c 100644
> --- a/http.c
> +++ b/http.c
> @@ -1367,6 +1367,7 @@ void run_active_slot(struct active_request_slot *slot)
> select(max_fd+1, &readfds, &writefds, &excfds, &select_timeout);
> }
> }
> + slot->finished = NULL;
> }
>
> static void release_active_slot(struct active_request_slot *slot)
next prev parent reply other threads:[~2022-05-06 20:23 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 18:04 [PATCH 0/2] quell a few gcc warnings Michael J Gruber
2022-05-06 18:04 ` [PATCH 1/2] dir.c: avoid gcc warning Michael J Gruber
2022-05-06 20:21 ` Junio C Hamano
2022-05-09 15:58 ` Taylor Blau
2022-05-07 6:14 ` Carlo Marcelo Arenas Belón
2022-05-06 18:04 ` [PATCH 2/2] http.c: " Michael J Gruber
2022-05-06 20:22 ` Junio C Hamano [this message]
2022-05-06 21:17 ` [PATCH] http.c: clear the 'finished' member once we are done with it Junio C Hamano
2022-05-07 5:40 ` Carlo Marcelo Arenas Belón
2022-05-07 18:42 ` Junio C Hamano
2022-05-07 19:11 ` Carlo Arenas
2022-05-23 21:58 ` Johannes Schindelin
2022-05-23 22:58 ` Junio C Hamano
2022-05-23 23:36 ` Junio C Hamano
2022-05-23 23:41 ` Johannes Schindelin
2022-05-24 0:02 ` Junio C Hamano
2022-05-24 6:31 ` Daniel Stenberg
2022-05-24 10:57 ` Johannes Schindelin
2022-05-24 17:45 ` Junio C Hamano
2022-05-26 14:15 ` Daniel Stenberg
2022-05-24 11:03 ` Johannes Schindelin
2022-05-24 17:15 ` Junio C Hamano
2022-05-24 20:16 ` Carlo Marcelo Arenas Belón
2022-05-24 20:45 ` Ævar Arnfjörð Bjarmason
2022-05-24 22:34 ` Junio C Hamano
2022-05-25 9:08 ` Michael J Gruber
2022-05-25 13:27 ` Ævar Arnfjörð Bjarmason
2022-05-24 22:16 ` Junio C Hamano
2022-05-24 23:19 ` Junio C Hamano
2022-05-25 2:02 ` Carlo Arenas
2022-05-24 20:38 ` Ævar Arnfjörð Bjarmason
2022-05-24 22:28 ` Junio C Hamano
2022-05-25 10:07 ` Johannes Schindelin
2022-05-25 16:40 ` Junio C Hamano
2022-05-06 20:41 ` [PATCH 2/2] http.c: avoid gcc warning Carlo Marcelo Arenas Belón
2022-05-09 11:22 ` [PATCH] detect-compiler: make detection independent of locale Michael J Gruber
2022-05-09 15:52 ` Junio C Hamano
2022-05-09 15:59 ` rsbecker
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=xmqqtua2jtr0.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@grubix.eu \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.