From: Filipe Cabecinhas <filcab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: write() _will_ fail on Mac OS X/XNU if nbytes > INT_MAX
Date: Fri, 10 May 2013 16:19:48 -0700 [thread overview]
Message-ID: <CAEDE853WiuoPenuuBgPehTg89_cLfBckr3CD=fEMuXTXwVv5kQ@mail.gmail.com> (raw)
In-Reply-To: <CAEDE851rRw24Dpxugt3_qJBtROdfcv4c6kskaizXnVy=gYVCBg@mail.gmail.com>
Hi Junio,
It compiles cleanly and runs. I'm running the test suite anyway, but
don't expect any change from your latest patch.
Thank you,
Filipe
F
On Fri, May 10, 2013 at 4:13 PM, Filipe Cabecinhas <filcab@gmail.com> wrote:
> Hi Junio,
>
> Thanks for helping. Your text is correct and only diffs from my patch
> in the #define write(...) part, where I suppose you stripped the
> spaced in the arglist.
>
> Thank you,
>
> Filipe
>
> F
>
>
> On Fri, May 10, 2013 at 4:05 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> Filipe Cabecinhas <filcab@gmail.com> writes:
>>
>>> Due to a bug in the Darwin kernel, write() calls have a maximum size of
>>> INT_MAX bytes.
>>>
>>> This patch introduces a new compat function: clipped_write
>>> This function behaves the same as write() but will write, at most, INT_MAX
>>> characters.
>>> It may be necessary to include this function on Windows, too.
>>>
>>> Signed-off-by: Filipe Cabecinhas <filcab+git@gmail.com>
>>> ---
>>
>> Somehow your MUA seems to have lost _all_ tabs, not just in the new
>> lines in your patch but also in the existing context lines.
>>
>>> diff --git a/Makefile b/Makefile
>>> index 0f931a2..ccb8f3f 100644
>>> --- a/Makefile
>>> +++ b/Makefile
>>> @@ -1466,6 +1466,11 @@ ifndef NO_MSGFMT_EXTENDED_OPTIONS
>>> MSGFMT += --check --statistics
>>> endif
>>>
>>> +ifdef NEEDS_CLIPPED_WRITE
>>> + BASIC_CFLAGS += -DNEEDS_CLIPPED_WRITE
>>> + COMPAT_OBJS += compat/clipped-write.o
>>> +endif
>>> +
>>> ...
>>
>> Here is what I resurrected and queued. I _think_ I did not make any
>> silly mistake while transcribing from your whitespace-mangled patch,
>> but please double check; I do not have any Darwin, so this hasn't
>> even been compile tested.
>>
>> Also I have a small suggestion I'd like you to try on top of it,
>> which I'll be sending in a separate message.
>>
>> Thanks.
>>
>> -- >8 --
>> From: Filipe Cabecinhas <filcab@gmail.com>
>> Date: Fri, 10 May 2013 15:24:57 -0700
>> Subject: [PATCH] compate/clipped-write.c: large write(2) fails on Mac OS X/XNU
>>
>> Due to a bug in the Darwin kernel, write(2) calls have a maximum size
>> of INT_MAX bytes.
>>
>> Introduce a new compat function, clipped_write(), that only writes
>> at most INT_MAX bytes and returns the number of bytes written, as
>> a substitute for write(2), and allow platforms that need this to
>> enable it from the build mechanism with NEEDS_CLIPPED_WRITE.
>>
>> Set it for Mac OS X by default. It may be necessary to include this
>> function on Windows, too.
>>
>> Signed-off-by: Filipe Cabecinhas <filcab+git@gmail.com>
>> Signed-off-by: Junio C Hamano <gitster@pobox.com>
>> ---
>> Makefile | 5 +++++
>> compat/clipped-write.c | 13 +++++++++++++
>> config.mak.uname | 1 +
>> git-compat-util.h | 5 +++++
>> 4 files changed, 24 insertions(+)
>> create mode 100644 compat/clipped-write.c
>>
>> diff --git a/Makefile b/Makefile
>> index 26d3332..7076b15 100644
>> --- a/Makefile
>> +++ b/Makefile
>> @@ -1463,6 +1463,11 @@ ifndef NO_MSGFMT_EXTENDED_OPTIONS
>> MSGFMT += --check --statistics
>> endif
>>
>> +ifdef NEEDS_CLIPPED_WRITE
>> + BASIC_CFLAGS += -DNEEDS_CLIPPED_WRITE
>> + COMPAT_OBJS += compat/clipped-write.o
>> +endif
>> +
>> ifneq (,$(XDL_FAST_HASH))
>> BASIC_CFLAGS += -DXDL_FAST_HASH
>> endif
>> diff --git a/compat/clipped-write.c b/compat/clipped-write.c
>> new file mode 100644
>> index 0000000..9183698
>> --- /dev/null
>> +++ b/compat/clipped-write.c
>> @@ -0,0 +1,13 @@
>> +#include <limits.h>
>> +#include <unistd.h>
>> +
>> +/*
>> + * Version of write that will write at most INT_MAX bytes.
>> + * Workaround a xnu bug on Mac OS X
>> + */
>> +ssize_t clipped_write(int fildes, const void *buf, size_t nbyte)
>> +{
>> + if (nbyte > INT_MAX)
>> + nbyte = INT_MAX;
>> + return write(fildes, buf, nbyte);
>> +}
>> diff --git a/config.mak.uname b/config.mak.uname
>> index e09af8f..e689a9a 100644
>> --- a/config.mak.uname
>> +++ b/config.mak.uname
>> @@ -95,6 +95,7 @@ ifeq ($(uname_S),Darwin)
>> NO_MEMMEM = YesPlease
>> USE_ST_TIMESPEC = YesPlease
>> HAVE_DEV_TTY = YesPlease
>> + NEEDS_CLIPPED_WRITE = YesPlease
>> COMPAT_OBJS += compat/precompose_utf8.o
>> BASIC_CFLAGS += -DPRECOMPOSE_UNICODE
>> endif
>> diff --git a/git-compat-util.h b/git-compat-util.h
>> index b636e0d..3144b8d 100644
>> --- a/git-compat-util.h
>> +++ b/git-compat-util.h
>> @@ -181,6 +181,11 @@ typedef unsigned long uintptr_t;
>> #define probe_utf8_pathname_composition(a,b)
>> #endif
>>
>> +#ifdef NEEDS_CLIPPED_WRITE
>> +ssize_t clipped_write(int fildes, const void *buf, size_t nbyte);
>> +#define write(x,y,z) clipped_write((x),(y),(z))
>> +#endif
>> +
>> #ifdef MKDIR_WO_TRAILING_SLASH
>> #define mkdir(a,b) compat_mkdir_wo_trailing_slash((a),(b))
>> extern int compat_mkdir_wo_trailing_slash(const char*, mode_t);
>> --
>> 1.8.3-rc1-268-g30389da
>>
next prev parent reply other threads:[~2013-05-10 23:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 22:31 write() _will_ fail on Mac OS X/XNU if nbytes > INT_MAX Filipe Cabecinhas
2013-04-09 22:50 ` Junio C Hamano
2013-05-09 22:58 ` Filipe Cabecinhas
2013-05-10 2:28 ` Junio C Hamano
2013-05-10 22:24 ` Filipe Cabecinhas
2013-05-10 23:05 ` Junio C Hamano
2013-05-10 23:10 ` Junio C Hamano
2013-05-10 23:13 ` Filipe Cabecinhas
2013-05-10 23:19 ` Filipe Cabecinhas [this message]
2013-05-10 23:36 ` Junio C Hamano
2013-11-20 10:15 ` Erik Faye-Lund
2013-11-20 13:03 ` Torsten Bögershausen
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='CAEDE853WiuoPenuuBgPehTg89_cLfBckr3CD=fEMuXTXwVv5kQ@mail.gmail.com' \
--to=filcab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).