From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
Alexandr Miloslavskiy <alexandr.miloslavskiy@syntevo.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 1/1] vreportf(): avoid buffered write in favor of unbuffered one
Date: Tue, 29 Oct 2019 11:38:42 +0100 [thread overview]
Message-ID: <20191029103842.GV4348@szeder.dev> (raw)
In-Reply-To: <455026ce3ef2b2d7cfecfc4b4bf5b588eebddcfe.1572274859.git.gitgitgadget@gmail.com>
On Mon, Oct 28, 2019 at 03:00:59PM +0000, Johannes Schindelin via GitGitGadget wrote:
> From: Johannes Schindelin <johannes.schindelin@gmx.de>
>
> The MSVC runtime behavior differs from glibc's with respect to
> `fprintf(stderr, ...)` in that the former writes out the message
> character by character.
>
> In t5516, this leads to a funny problem where a `git fetch` process as
> well as the `git upload-pack` process spawned by it _both_ call `die()`
> at the same time. The output can look like this:
>
> fatal: git uploadfata-lp: raemcokte :error: upload-pnot our arcef k6: n4ot our ea4cr1e3f 36d45ea94fca1398e86a771eda009872d63adb28598f6a9
> 8e86a771eda009872d6ab2886
Heh.
> Let's avoid this predicament altogether by rendering the entire message,
> including the prefix and the trailing newline, into the buffer we
> already have (and which is still fixed size) and then write it out via
> `write_in_full()`.
s/write_in_full/xwrite/ perhaps? Both the cover letter and the patch
below use xwrite().
> The history of `vreportf()` with regard to this issue includes the
> following commits:
>
> d048a96e (2007-11-09) - 'char msg[256]' is introduced to avoid interleaving
> 389d1767 (2009-03-25) - Buffer size increased to 1024 to avoid truncation
> 625a860c (2009-11-22) - Buffer size increased to 4096 to avoid truncation
> f4c3edc0 (2015-08-11) - Buffer removed to avoid truncation
> b5a9e435 (2017-01-11) - Reverts f4c3edc0 to be able to replace control
> chars before sending to stderr
> 9ac13ec9 (2006-10-11) - Another attempt to solve interleaving.
> This is seemingly related to d048a96e.
> 137a0d0e (2007-11-19) - Addresses out-of-order for display()
> 34df8aba (2009-03-10) - Switches xwrite() to fprintf() in recv_sideband()
> to support UTF-8 emulation
> eac14f89 (2012-01-14) - Removes the need for fprintf() for UTF-8 emulation,
> so it's safe to use xwrite() again
> 5e5be9e2 (2016-06-28) - recv_sideband() uses xwrite() again
>
> Note that we need to be careful to handle the return value of
> `vsnprintf()` that indicates the _desired_ byte count.
>
> Also please note that we `fflush(stderr)` here to help when running in a
> Git Bash on Windows: in this case, `stderr` is not actually truly
> unbuffered, and needs the extra help.
>
> Co-authored-by: Alexandr Miloslavskiy <alexandr.miloslavskiy@syntevo.com>
> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
> ---
> usage.c | 12 +++++++++---
> 1 file changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/usage.c b/usage.c
> index 2fdb20086b..4328894dce 100644
> --- a/usage.c
> +++ b/usage.c
> @@ -10,13 +10,19 @@ void vreportf(const char *prefix, const char *err, va_list params)
> {
> char msg[4096];
> char *p;
> -
> - vsnprintf(msg, sizeof(msg), err, params);
> + size_t off = strlcpy(msg, prefix, sizeof(msg));
> + int ret = vsnprintf(msg + off, sizeof(msg) - off, err, params);
> for (p = msg; *p; p++) {
> if (iscntrl(*p) && *p != '\t' && *p != '\n')
> *p = '?';
> }
> - fprintf(stderr, "%s%s\n", prefix, msg);
> + if (ret > 0) {
> + if (off + ret > sizeof(msg) - 1)
> + ret = sizeof(msg) - 1 - off;
> + msg[off + ret] = '\n'; /* we no longer need a NUL */
> + fflush(stderr);
> + xwrite(2, msg, off + ret + 1);
> + }
> }
>
> static NORETURN void usage_builtin(const char *err, va_list params)
> --
> gitgitgadget
next prev parent reply other threads:[~2019-10-29 10:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 15:00 [PATCH 0/1] Fix t5516 flakiness in Visual Studio builds Johannes Schindelin via GitGitGadget
2019-10-28 15:00 ` [PATCH 1/1] vreportf(): avoid buffered write in favor of unbuffered one Johannes Schindelin via GitGitGadget
2019-10-29 3:18 ` Junio C Hamano
2019-10-29 12:30 ` Johannes Schindelin
2019-10-29 13:49 ` Jeff King
2019-10-29 14:13 ` Johannes Schindelin
2019-10-29 14:32 ` Jeff King
2019-10-29 20:09 ` Johannes Schindelin
2019-10-30 1:43 ` Junio C Hamano
2019-10-29 16:44 ` Junio C Hamano
2019-10-29 10:38 ` SZEDER Gábor [this message]
2019-10-29 12:38 ` Johannes Schindelin
2019-10-29 13:52 ` Jeff King
2019-10-29 14:18 ` Johannes Schindelin
2019-10-29 13:37 ` [PATCH v2 0/1] Fix t5516 flakiness in Visual Studio builds Johannes Schindelin via GitGitGadget
2019-10-29 13:37 ` [PATCH v2 1/1] vreportf(): avoid relying on stdio buffering Johannes Schindelin via GitGitGadget
2019-10-29 14:21 ` Alexandr Miloslavskiy
2019-10-29 19:57 ` Johannes Schindelin
2019-10-29 20:09 ` Jeff King
2019-10-29 20:24 ` Alexandr Miloslavskiy
2019-10-29 20:11 ` Alexandr Miloslavskiy
2019-10-29 20:01 ` [PATCH v3 0/1] Fix t5516 flakiness in Visual Studio builds Johannes Schindelin via GitGitGadget
2019-10-29 20:01 ` [PATCH v3 1/1] vreportf(): avoid relying on stdio buffering Johannes Schindelin via GitGitGadget
2019-10-29 20:32 ` Jeff King
2019-10-30 8:54 ` Johannes Schindelin
2019-10-31 6:24 ` Jeff King
2019-10-31 10:26 ` Johannes Schindelin
2019-10-31 15:48 ` Jeff King
2019-11-01 18:41 ` Johannes Schindelin
2019-10-30 2:01 ` Junio C Hamano
2019-10-30 9:13 ` Johannes Schindelin
2019-10-30 10:44 ` [PATCH v4 0/1] Fix t5516 flakiness in Visual Studio builds Johannes Schindelin via GitGitGadget
2019-10-30 10:44 ` [PATCH v4 1/1] vreportf(): avoid relying on stdio buffering Johannes Schindelin via GitGitGadget
2019-11-02 4:05 ` 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=20191029103842.GV4348@szeder.dev \
--to=szeder.dev@gmail.com \
--cc=alexandr.miloslavskiy@syntevo.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=peff@peff.net \
/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).