From: Junio C Hamano <gitster@pobox.com>
To: "Li Linchao via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, "Jonathan Tan" <jonathantanmy@google.com>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Li Linchao" <lilinchao@oschina.cn>
Subject: Re: [PATCH v3] remote-curl: send Accept-Language header to server
Date: Mon, 13 Jun 2022 15:08:47 -0700 [thread overview]
Message-ID: <xmqqedzs43o0.fsf@gitster.g> (raw)
In-Reply-To: <xmqq1qvs5jx4.fsf@gitster.g> (Junio C. Hamano's message of "Mon, 13 Jun 2022 14:32:23 -0700")
Junio C Hamano <gitster@pobox.com> writes:
>> + accept_language = http_get_accept_language_header();
>> + if (accept_language)
>> + rpc.hdr_accept_language = xstrfmt("%s", accept_language);
>
> Isn't rpc.hdr_accept_language left uninitialized garbage if
> accept_language is NULL? It is the same bug I pointed out earlier,
> whose fix may have to be different.
>
> Has this been tested? I got immediate segfault with this patch in
> 'seen'.
Having said all that, I wonder if we want to use something like this
to make it hard to use an uninitialized data.
The smart-http is quite outside of my area of expertise, and I do
not know what Shawn was thinking when de1a2fdd (Smart push over
HTTP: client side, 2009-10-30) was written (it could be that filling
all members explicitly was the more prevalent stype back then?).
I'd appreciate input from folks who regularly deal with smart-http
on the approach.
Thanks.
remote-curl.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git i/remote-curl.c w/remote-curl.c
index 251d4ee64f..ba6f76a0c1 100644
--- i/remote-curl.c
+++ w/remote-curl.c
@@ -608,6 +608,8 @@ struct rpc_state {
unsigned flush_read_but_not_sent : 1;
};
+#define RPC_STATE_INIT { 0, }
+
/*
* Appends the result of reading from rpc->out to the string represented by
* rpc->buf and rpc->len if there is enough space. Returns 1 if there was
@@ -1161,7 +1163,7 @@ static int fetch_dumb(int nr_heads, struct ref **to_fetch)
static int fetch_git(struct discovery *heads,
int nr_heads, struct ref **to_fetch)
{
- struct rpc_state rpc;
+ struct rpc_state rpc = RPC_STATE_INIT;
struct strbuf preamble = STRBUF_INIT;
int i, err;
struct strvec args = STRVEC_INIT;
@@ -1307,7 +1309,7 @@ static int push_dav(int nr_spec, const char **specs)
static int push_git(struct discovery *heads, int nr_spec, const char **specs)
{
- struct rpc_state rpc;
+ struct rpc_state rpc = RPC_STATE_INIT;
int i, err;
struct strvec args;
struct string_list_item *cas_option;
@@ -1406,7 +1408,7 @@ static void parse_push(struct strbuf *buf)
static int stateless_connect(const char *service_name)
{
struct discovery *discover;
- struct rpc_state rpc;
+ struct rpc_state rpc = RPC_STATE_INIT;
struct strbuf buf = STRBUF_INIT;
const char *accept_language;
next prev parent reply other threads:[~2022-06-13 22:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 8:53 [PATCH] remote-curl: send Accept-Language header to server Li Linchao via GitGitGadget
2022-06-08 23:32 ` Junio C Hamano
2022-06-09 6:35 ` [PATCH v2] " Li Linchao via GitGitGadget
2022-06-09 23:55 ` Junio C Hamano
2022-06-10 3:49 ` lilinchao
2022-06-10 4:22 ` lilinchao
2022-06-12 17:20 ` [PATCH v3] " Li Linchao via GitGitGadget
2022-06-13 18:15 ` Junio C Hamano
2022-06-13 21:32 ` Junio C Hamano
2022-06-13 22:08 ` Junio C Hamano [this message]
2022-06-13 22:15 ` Junio C Hamano
2022-07-11 5:58 ` [PATCH v4] " Li Linchao via GitGitGadget
2022-06-09 7:30 ` [PATCH] " Ævar Arnfjörð Bjarmason
2022-06-09 17:34 ` Junio C Hamano
2022-06-10 2:38 ` lilinchao
2022-07-03 0:57 ` Junio C Hamano
2022-07-05 10:06 ` lilinchao
2022-07-05 10:15 ` Ævar Arnfjörð Bjarmason
2022-07-05 18:06 ` Junio C Hamano
2022-07-05 17:53 ` Junio C Hamano
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=xmqqedzs43o0.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=jonathantanmy@google.com \
--cc=lilinchao@oschina.cn \
/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).