From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] l2fwd-crypto: fix supported key size check Date: Tue, 07 Jun 2016 22:23:02 +0200 Message-ID: <3165538.0Ecj1rrkI9@xps13> References: <1460455443-11130-1-git-send-email-pablo.de.lara.guarch@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, declan.doherty@intel.com, Min Cao To: Pablo de Lara Return-path: Received: from mail-wm0-f41.google.com (mail-wm0-f41.google.com [74.125.82.41]) by dpdk.org (Postfix) with ESMTP id DA9679AD5 for ; Tue, 7 Jun 2016 22:23:04 +0200 (CEST) Received: by mail-wm0-f41.google.com with SMTP id k204so84510864wmk.0 for ; Tue, 07 Jun 2016 13:23:04 -0700 (PDT) In-Reply-To: <1460455443-11130-1-git-send-email-pablo.de.lara.guarch@intel.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" > When initializing crypto devices within the app, > the provided key sizes are checked against the supported > sizes from the crypto device capabilities. > > When the supported sizes are not a range, but a single value, > the check may become an infinite loop (when size is not supported). > > Fixes: a061e50a0d97 ("examples/l2fwd-crypto: fix ambiguous input key size") > > Signed-off-by: Pablo de Lara Tested-by: Min Cao Applied, thanks