From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 824371B7F8; Wed, 31 Jan 2018 19:02:09 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 03AC020C63; Wed, 31 Jan 2018 13:02:09 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 31 Jan 2018 13:02:09 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=xnLz+FtIHC3rQkh2RUL05mZskG +6HlnReZn/keoxSZw=; b=UdRsSlet5U6EMoznTDuFhlhVnLnQuO3aqHw3EFTJFP Qlcpc1V4L+qVRQS7AuwZt4GUGHTGSEU3HOzzDRyfnafnF4oe+M1XPUnq1e2uHLmO 7SJXVqudVR1T7Bs3l7fkHWTU+Do0DKb5ZstfqIFniAEdTkin7MHenHLMe27Vyxhc E= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=xnLz+F tIHC3rQkh2RUL05mZskG+6HlnReZn/keoxSZw=; b=kD3LRT9gPY7zTfwWrlv4GT JZPYZCUEcE6w2l9jgLEiH91+ksBl/gPmqKdeUxHkHEhH2YJB6BvRVpthuUz93y6u PosAKFgt9zHFyfRYLAsAZ4RvKiiO5iMxdGwSFfHJFJEVLb5cQdvzeNqoT/FbA8nx +D4M6PW10/fIH2+aOeQGBeShx6zHxIg9tPhcRnqb6VgPQqSEEpMeZHtRHxd+n+Fc 6uqwiFeZSxwGxSEjCGKMkkargpiKsCoFDho/7jCygCc091SWHcFB02iXSflsFi7n gSrlSi/jbSuBblVNf9zPGRMA/5Aco6o/6Wose2lJ9yJO1rdozzH9u2iB+iGrtGfA == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 860A224803; Wed, 31 Jan 2018 13:02:08 -0500 (EST) From: Thomas Monjalon To: "De Lara Guarch, Pablo" Cc: dev@dpdk.org, "Zhang, Roy Fan" , "Richardson, Bruce" , "stable@dpdk.org" Date: Wed, 31 Jan 2018 19:01:20 +0100 Message-ID: <1807850.sLrRnkPxLN@xps> In-Reply-To: <9F7182E3F746AB4EA17801C148F3C604330AC4E9@IRSMSX101.ger.corp.intel.com> References: <20180126144428.13154-1-pablo.de.lara.guarch@intel.com> <20180129092202.45914-1-pablo.de.lara.guarch@intel.com> <9F7182E3F746AB4EA17801C148F3C604330AC4E9@IRSMSX101.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2] crypto/scheduler: fix strncpy X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 18:02:09 -0000 > > The coverity issue was not completely fixed, since strncpy should not be > > called with max length. > > Instead, snprintf is used as a safer option. > > > > Coverity issue: 143431 > > Fixes: d040aca67170 ("crypto/scheduler: fix strings not null terminated") > > Cc: stable@dpdk.org > > > > Signed-off-by: Pablo de Lara > > --- > > > > v2: > > - Replaced strncpy with snprintf > > Acked-by: Fan Zhang Applied, thanks