From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephan Mueller Subject: Re: [PATCH v11 1/2] crypto: AF_ALG: add AEAD support Date: Mon, 26 Jan 2015 05:39:27 +0100 Message-ID: <1793732.EQDAUxrRn5@tachyon.chronox.de> References: <1923793.K38mGRD6eo@tachyon.chronox.de> <1526868.qaVuSjCOn7@tachyon.chronox.de> <20150126043218.GA20911@gondor.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: Daniel Borkmann , 'Quentin Gouchet' , 'LKML' , linux-crypto@vger.kernel.org, linux-api@vger.kernel.org, Neil Horman To: Herbert Xu Return-path: Received: from mail.eperm.de ([89.247.134.16]:60135 "EHLO mail.eperm.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752087AbbAZEjc (ORCPT ); Sun, 25 Jan 2015 23:39:32 -0500 Received: from tachyon.chronox.de by mail.eperm.de with [XMail 1.27 ESMTP Server] id for from ; Mon, 26 Jan 2015 05:39:28 +0100 In-Reply-To: <20150126043218.GA20911@gondor.apana.org.au> Sender: linux-crypto-owner@vger.kernel.org List-ID: Am Montag, 26. Januar 2015, 15:32:18 schrieb Herbert Xu: Hi Herbert, > On Mon, Jan 26, 2015 at 05:26:33AM +0100, Stephan Mueller wrote: > > Am Montag, 26. Januar 2015, 10:55:50 schrieb Herbert Xu: > > > > Hi Herbert, > > > > > On Wed, Jan 21, 2015 at 02:19:17AM +0100, Stephan Mueller wrote: > > > > + /* use the existing memory in an allocated page */ > > > > + if (ctx->merge) { > > > > + sg = sgl->sg + sgl->cur - 1; > > > > + len = min_t(unsigned long, len, > > > > + PAGE_SIZE - sg->offset - sg- >length); > > > > + err = memcpy_from_msg(page_address(sg_page(sg)) + > > > > + sg->offset + sg->length, > > > > + msg, len); > > > > + if (err) > > > > + goto unlock; > > > > + > > > > + sg->length += len; > > > > + ctx->merge = (sg->offset + sg->length) & > > > > + (PAGE_SIZE - 1); > > > > + > > > > + ctx->used += len; > > > > + copied += len; > > > > + size -= len; > > > > > > Need to add a continue here to recheck size != 0. > > > > Why would that be needed? > > > > When size is still != 0 (i.e. the existing buffer is completely filled, we > > have still some remaining data), we fall through to the while loop that > > generates a new buffer. > > Because when size == 0 you should exit the loop. IOW if the new > data is completely merged you should get out and not continue. But does it really matter if we consider size == 0 or != at this point? In case size == 0, the len calculation before the inner while loop will return 0. Thus the inner while loop will not start. Thus, the current code will not run the inner loop and exit the outer loop in the next round. So, I am not sure I see the benefit from another check here. -- Ciao Stephan