From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH v9 01/15] tools/libxc: Implement writev_exact() in the same style as write_exact() Date: Wed, 15 Apr 2015 11:44:26 +0100 Message-ID: <1429094666.15516.188.camel@citrix.com> References: <1428686167-8279-1-git-send-email-andrew.cooper3@citrix.com> <1428686167-8279-2-git-send-email-andrew.cooper3@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1428686167-8279-2-git-send-email-andrew.cooper3@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andrew Cooper Cc: Wei Liu , Ian Jackson , Xen-devel List-Id: xen-devel@lists.xenproject.org On Fri, 2015-04-10 at 18:15 +0100, Andrew Cooper wrote: > This implementation of writev_exact() will cope with an iovcnt greater than > IOV_MAX because glibc will actually let this work anyway, and it is very > useful not to have to work about this in the caller of writev_exact(). The > caller is still required to ensure that the sum of iov_len's doesn't overflow > a ssize_t. > > Signed-off-by: Andrew Cooper > CC: Ian Campbell > CC: Ian Jackson > CC: Wei Liu Acked-by: Ian Campbell