All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Meyering <jim@meyering.net>
To: git@vger.kernel.org
Subject: [PATCH] detect dup failure
Date: Wed, 27 Jun 2007 13:59:47 +0200	[thread overview]
Message-ID: <87wsxpobf0.fsf@rho.meyering.net> (raw)

Without this, if you ever run out of file descriptors, dup will
fail (silently), fdopen will return NULL, and fprintf will
try to dereference NULL (i.e., usually segfault).

Signed-off-by: Jim Meyering <jim@meyering.net>
---
 builtin-log.c |    8 ++++++--
 1 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/builtin-log.c b/builtin-log.c
index 073a2a1..ca54387 100644
--- a/builtin-log.c
+++ b/builtin-log.c
@@ -588,8 +588,12 @@ int cmd_format_patch(int argc, const char **argv, const char *prefix)
 	if (ignore_if_in_upstream)
 		get_patch_ids(&rev, &ids, prefix);

-	if (!use_stdout)
-		realstdout = fdopen(dup(1), "w");
+	if (!use_stdout) {
+		int fd = dup(1);
+		if (fd < 0)
+			die("failed to duplicate standard output");
+		realstdout = fdopen(fd, "w");
+	}

 	prepare_revision_walk(&rev);
 	while ((commit = get_revision(&rev)) != NULL) {

             reply	other threads:[~2007-06-27 11:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-27 11:59 Jim Meyering [this message]
2007-06-27 12:48 ` [PATCH] detect dup failure Alex Riesen
2007-06-27 13:02   ` [PATCH] git-log: detect dup and fdopen failure Jim Meyering
2007-06-27 13:18     ` Alex Riesen
2007-06-27 13:32       ` Jim Meyering
2007-06-27 14:04         ` Alex Riesen
2007-06-27 14:14           ` Jim Meyering
2007-06-27 15:57             ` Alex Riesen
2007-06-27 16:34               ` Jim Meyering
2007-06-27 13:54     ` Geert Bosch
2007-06-27 14:06       ` Jim Meyering
2007-06-27 14:28       ` Jim Meyering
2007-06-27 16:49         ` Linus Torvalds
2007-06-28  2:46           ` Josh Triplett
2007-06-28  5:02             ` Shawn O. Pearce

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=87wsxpobf0.fsf@rho.meyering.net \
    --to=jim@meyering.net \
    --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.