From mboxrd@z Thu Jan 1 00:00:00 1970 From: Akhil Goyal Subject: Re: [PATCH] crypto/dpaa_sec: add check for segmented buffer Date: Fri, 13 Oct 2017 20:13:36 +0530 Message-ID: References: <20171012130726.4332-1-alok.makhariya@nxp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Cc: , To: , Return-path: Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0066.outbound.protection.outlook.com [104.47.36.66]) by dpdk.org (Postfix) with ESMTP id 07E1B1B710 for ; Fri, 13 Oct 2017 16:43:40 +0200 (CEST) In-Reply-To: <20171012130726.4332-1-alok.makhariya@nxp.com> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 10/12/2017 6:37 PM, alok.makhariya@nxp.com wrote: > From: Alok Makhariya > > The code would crash in case of segmented buffer if no check > > Fixes: 89aaf708d44b ("crypto/dpaa_sec: add crypto driver for NXP DPAA platform") > > Signed-off-by: Alok Makhariya > --- > drivers/crypto/dpaa_sec/dpaa_sec.c | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/drivers/crypto/dpaa_sec/dpaa_sec.c b/drivers/crypto/dpaa_sec/dpaa_sec.c > index 7b9a683..8a57b96 100644 > --- a/drivers/crypto/dpaa_sec/dpaa_sec.c > +++ b/drivers/crypto/dpaa_sec/dpaa_sec.c > @@ -893,6 +893,13 @@ dpaa_sec_enqueue_op(struct rte_crypto_op *op, struct dpaa_sec_qp *qp) > return ret; > } > > + /* > + * Segmented buffer is not supported. > + */ > + if (!rte_pktmbuf_is_contiguous(op->sym->m_src)) { > + op->status = RTE_CRYPTO_OP_STATUS_ERROR; > + return -ENOTSUP; > + } > if (is_auth_only(ses)) { > cf = build_auth_only(op, ses); > } else if (is_cipher_only(ses)) { > It looks there are some checkpatch errors.