From: Tadeusz Struk Subject: Re: [PATCH v13 1/2] crypto: AF_ALG: add AEAD support Date: Thu, 11 Jun 2015 15:59:29 -0700 Message-ID: <557A12D1.90409@intel.com> References: <2180298.gqj58NYuqx@tachyon.chronox.de> <14853152.iudhcNpbrH@tachyon.chronox.de> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: 'Herbert Xu , 'Quentin Gouchet' , Daniel Borkmann , linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-crypto-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Stephan Mueller Return-path: In-Reply-To: <14853152.iudhcNpbrH-PJstQz4BMNNP20K/wil9xYQuADTiUCJX@public.gmane.org> Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-crypto.vger.kernel.org Hi Stephan, On 02/28/2015 11:50 AM, Stephan Mueller wrote: > + err = af_alg_wait_for_completion(ctx->enc ? > + crypto_aead_encrypt(&ctx->aead_req) : > + crypto_aead_decrypt(&ctx->aead_req), > + &ctx->completion); > + > + if (err) { > + /* EBADMSG implies a valid cipher operation took place */ > + if (err == -EBADMSG) > + aead_put_sgl(sk); > + goto unlock; Shouldn't we free the TX sgl regardless of the error was? Or do we expect that the user will try to read again and it will be Ok the second time? Hope you still remember :) > + } > + > + aead_put_sgl(sk); > + > + err = 0; > + > +unlock: > + for (i = 0; i < cnt; i++) > + af_alg_free_sg(&ctx->rsgl[i]); > + > + aead_wmem_wakeup(sk); > + release_sock(sk); > + > + return err ? err : outlen; > +}