From: Jeff King <peff@peff.net>
To: Peter Baumann <waste.manager@gmx.de>
Cc: Robert Wruck <wruck@tweerlei.de>, git@vger.kernel.org
Subject: Re: [BUG] git cat-file does not terminate
Date: Fri, 4 Mar 2011 11:00:47 -0500 [thread overview]
Message-ID: <20110304160047.GA9662@sigill.intra.peff.net> (raw)
In-Reply-To: <20110304154014.GE24660@m62s10.vlinux.de>
On Fri, Mar 04, 2011 at 04:40:14PM +0100, Peter Baumann wrote:
> > I "fixed" it by limiting each write to 64k (thus looping in
> > write_in_full) but maybe somebody knows about that cygwin behaviour?
> >
> > This seems to be the cause of the dreaded "No newline found after
> > blob" when running `git svn clone` under cygwin on a repository with
> > large files.
> >
> > You could argue that this is a cygwin bug but maybe limiting each
> > write to a maximum size is a simple workaround.
> >
> Maybe you could post a patch, so everyone can see the technical implications
> and discuss the fix?
It would probably look like the patch below, though it really feels like
the right solution is to fix the cygwin bug.
-Peff
---
diff --git a/Makefile b/Makefile
index 4c31d1a..e7d3285 100644
--- a/Makefile
+++ b/Makefile
@@ -167,6 +167,9 @@ all::
# Define NO_ST_BLOCKS_IN_STRUCT_STAT if your platform does not have st_blocks
# field that counts the on-disk footprint in 512-byte blocks.
#
+# Define MAX_WRITE_SIZE to N if your platform has unpredictable results for
+# write() calls larger than N (e.g., cygwin).
+#
# Define ASCIIDOC7 if you want to format documentation with AsciiDoc 7
#
# Define DOCBOOK_XSL_172 if you want to format man pages with DocBook XSL v1.72
@@ -928,6 +931,7 @@ ifeq ($(uname_O),Cygwin)
NO_FAST_WORKING_DIRECTORY = UnfortunatelyYes
NO_TRUSTABLE_FILEMODE = UnfortunatelyYes
NO_ST_BLOCKS_IN_STRUCT_STAT = YesPlease
+ MAX_WRITE_SIZE=65536
# There are conflicting reports about this.
# On some boxes NO_MMAP is needed, and not so elsewhere.
# Try commenting this out if you suspect MMAP is more efficient
@@ -1495,6 +1499,10 @@ ifdef NO_POSIX_GOODIES
BASIC_CFLAGS += -DNO_POSIX_GOODIES
endif
+ifdef MAX_WRITE_SIZE
+ BASIC_CFLAGS += -DMAX_WRITE_SIZE=$(MAX_WRITE_SIZE)
+endif
+
ifdef BLK_SHA1
SHA1_HEADER = "block-sha1/sha1.h"
LIB_OBJS += block-sha1/sha1.o
diff --git a/wrapper.c b/wrapper.c
index 056e9d6..a7a2437 100644
--- a/wrapper.c
+++ b/wrapper.c
@@ -133,6 +133,10 @@ ssize_t xread(int fd, void *buf, size_t len)
ssize_t xwrite(int fd, const void *buf, size_t len)
{
ssize_t nr;
+#ifdef MAX_WRITE_SIZE
+ if (len > MAX_WRITE_SIZE)
+ len = MAX_WRITE_SIZE;
+#endif
while (1) {
nr = write(fd, buf, len);
if ((nr < 0) && (errno == EAGAIN || errno == EINTR))
next prev parent reply other threads:[~2011-03-04 16:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 13:04 [BUG] git cat-file does not terminate Robert Wruck
2011-03-04 15:40 ` Peter Baumann
2011-03-04 16:00 ` Jeff King [this message]
2011-03-04 17:16 ` Junio C Hamano
2011-03-04 17:29 ` Robert Wruck
2011-03-04 18:26 ` Robert Wruck
2011-03-08 21:14 ` Jeff King
2011-03-08 22:52 ` Junio C Hamano
2011-03-09 14:49 ` Robert Wruck
2011-03-09 19:32 ` Junio C Hamano
2011-03-09 19:51 ` Robert Wruck
2011-03-09 21:43 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110304160047.GA9662@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=waste.manager@gmx.de \
--cc=wruck@tweerlei.de \
/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).