DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: dev@dpdk.org, declan.doherty@intel.com, Min Cao <min.cao@intel.com>
Subject: Re: [dpdk-dev] [PATCH] l2fwd-crypto: fix supported key size check
Date: Tue, 07 Jun 2016 22:23:02 +0200	[thread overview]
Message-ID: <3165538.0Ecj1rrkI9@xps13> (raw)
In-Reply-To: <1460455443-11130-1-git-send-email-pablo.de.lara.guarch@intel.com>

> 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 <pablo.de.lara.guarch@intel.com>

Tested-by: Min Cao <min.cao@intel.com>

Applied, thanks

      parent reply	other threads:[~2016-06-07 20:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12 10:04 Pablo de Lara
2016-04-19  8:41 ` Cao, Min
2016-06-07 20:23 ` Thomas Monjalon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3165538.0Ecj1rrkI9@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=min.cao@intel.com \
    --cc=pablo.de.lara.guarch@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).