From: Jeff Garzik <jeff@garzik.org>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: hail-devel@vger.kernel.org
Subject: Re: [PATCH 6/6] chunkd: fix PUT/GET for more than 2GB values
Date: Tue, 12 Jan 2010 09:40:43 -0500 [thread overview]
Message-ID: <4B4C89EB.2090000@garzik.org> (raw)
In-Reply-To: <1263212721-11210-6-git-send-email-akinobu.mita@gmail.com>
On 01/11/2010 07:25 AM, Akinobu Mita wrote:
> - Define _FILE_OFFSET_BITS
>
> - Use uint64_t to hold object length and buffer length
>
> - Don't pass too much buffer to writev. writev returns -1 if the sum of
> the iov_len values overflows an ssize_t value
>
> Signed-off-by: Akinobu Mita<akinobu.mita@gmail.com>
> ---
> server/be-fs.c | 1 +
> server/chunkd.h | 6 +++---
> server/object.c | 2 +-
> server/server.c | 9 ++++++++-
> 4 files changed, 13 insertions(+), 5 deletions(-)
applied
next prev parent reply other threads:[~2010-01-12 14:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 12:25 [PATCH 1/6] chunkd: Don't hardcode the prefix length of object pathname Akinobu Mita
2010-01-11 12:25 ` [PATCH 2/6] chunkd: change the prefix length of object pathname from 4 to 3 Akinobu Mita
2010-01-12 2:55 ` Jeff Garzik
2010-01-12 8:28 ` Akinobu Mita
2010-01-12 11:27 ` Jeff Garzik
2010-01-13 3:50 ` Akinobu Mita
2010-01-13 10:52 ` Jeff Garzik
2010-01-11 12:25 ` [PATCH 3/6] chunkd: Don't return positive value on stc_get_recv failure Akinobu Mita
2010-01-11 12:25 ` [PATCH 4/6] chcli: Add -i option to read value from file Akinobu Mita
2010-01-11 12:25 ` [PATCH 5/6] chcli: fix error handling for write() Akinobu Mita
2010-01-11 12:25 ` [PATCH 6/6] chunkd: fix PUT/GET for more than 2GB values Akinobu Mita
2010-01-12 14:40 ` Jeff Garzik [this message]
2010-01-12 14:38 ` [PATCH 1/6] chunkd: Don't hardcode the prefix length of object pathname Jeff Garzik
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=4B4C89EB.2090000@garzik.org \
--to=jeff@garzik.org \
--cc=akinobu.mita@gmail.com \
--cc=hail-devel@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.