From: Thomas Monjalon <thomas@monjalon.net>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: dev@dpdk.org, declan.doherty@intel.com
Subject: Re: [dpdk-dev] [PATCH] examples/l2fwd-crypto: fix possible out-of-bounds
Date: Mon, 31 Jul 2017 22:47:32 +0200 [thread overview]
Message-ID: <3962811.70LsA9TyAl@xps> (raw)
In-Reply-To: <20170731044037.70950-1-pablo.de.lara.guarch@intel.com>
31/07/2017 06:40, Pablo de Lara:
> rte_cryptodev_socket_id() returns the socket id of
> a crypto device, unless the device id is not valid,
> in which case, it returns -1.
> This should not happen, as the device id is controlled
> by the application, but just for safety, a check is added.
>
> Coverity issue: 158628, 158638, 158656, 158662
> Fixes: b3bbd9e5f265 ("cryptodev: support device independent sessions")
>
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Applied, thanks
prev parent reply other threads:[~2017-07-31 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 4:40 Pablo de Lara
2017-07-31 20:47 ` 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=3962811.70LsA9TyAl@xps \
--to=thomas@monjalon.net \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--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).