From: "René Scharfe" <email@example.com> To: Chris Torek <firstname.lastname@example.org> Cc: Git Mailing List <email@example.com>, Junio C Hamano <firstname.lastname@example.org> Subject: Re: [PATCH] upload-pack: use buffered I/O to talk to rev-list Date: Mon, 3 Aug 2020 16:00:34 +0200 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <CAPx1GvdJ-4Yyf7Vm1OdhaW2TZp77HOfGxoGw0R2fKfEuHQkqOg@mail.gmail.com> Am 02.08.20 um 18:03 schrieb Chris Torek: > One suggestion here: > > On Sun, Aug 2, 2020 at 7:41 AM René Scharfe <firstname.lastname@example.org> wrote: >> Like f0bca72dc77 (send-pack: use buffered I/O to talk to pack-objects, >> 2016-06-08), significantly reduce the number of system calls and >> simplify the code for sending object IDs to rev-list by using stdio's >> buffering and handling errors after the loops. >> >> Signed-off-by: René Scharfe <email@example.com> >> --- >> upload-pack.c | 21 +++++++-------------- >> 1 file changed, 7 insertions(+), 14 deletions(-) >> >> diff --git a/upload-pack.c b/upload-pack.c >> index 86737410709..9f616c2c6a6 100644 >> --- a/upload-pack.c >> +++ b/upload-pack.c > > [snip] > >> @@ -640,12 +636,11 @@ static int do_reachable_revlist(struct child_process *cmd, >> } >> if (reachable && o->type == OBJ_COMMIT) >> o->flags |= TMP_MARK; >> - memcpy(namebuf, oid_to_hex(&o->oid), hexsz); >> - if (write_in_full(cmd->in, namebuf, hexsz + 1) < 0) >> - goto error; >> + fprintf(cmd_in, "%s\n", oid_to_hex(&o->oid)); > > The fprintf() call here *can* return an error, e.g., if the > connection has died. If it does, it should set things up so that > a later ferror(cmd_in) returns true. > >> } >> - close(cmd->in); >> cmd->in = -1; >> + if (fclose(cmd_in)) >> + goto error; > > The fclose() call doesn't necessarily check ferror(). (The > FreeBSD stdio in particular definitely does not.) It might > be better to use: > > failure = ferror(cmd_in); > failure |= fclose(cmd_in); > if (failure) ... > > here, or similar. (The temporary variable is not needed, > but someone might assume `if (ferror(fp) | fclose(fp))` is > a typo for `if (ferror(fp) || fclose(fp))`.) Thanks, didn't know that. That's awful. So the sentence "The fclose() and fdclose() functions may also fail and set errno for any of the errors specified for fflush(3)." from the FreeBSD manpage for fclose(3) actually means that while it will flush, it is free to ignore any flush errors? Or do you mean that fflush() can succeed on a stream that has its error indicator set? In any case, we'd then better add a function that flushes the buffer, closes the stream and reports errors in its return code and errno -- i.e. a sane fclose(). René
next prev parent reply other threads:[~2020-08-03 14:01 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-02 14:38 René Scharfe 2020-08-02 16:03 ` Chris Torek 2020-08-03 14:00 ` René Scharfe [this message] 2020-08-03 15:54 ` Chris Torek 2020-08-03 18:15 ` Johannes Sixt 2020-08-12 16:52 ` [PATCH v2] " René Scharfe 2020-08-13 5:17 ` Christian Couder 2020-08-13 5:57 ` René Scharfe 2020-08-13 9:01 ` Jeff King
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH] upload-pack: use buffered I/O to talk to rev-list' \ /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
Code repositories for project(s) associated with this 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).