From: "Zhao, XinfengX" <xinfengx.zhao@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] dpdk-dev] [PATCH] cryptodev: fix missing device id range checking
Date: Fri, 20 Mar 2020 00:37:32 +0000 [thread overview]
Message-ID: <99d93b95ec514defb664b15305fe073c@intel.com> (raw)
Tested-by: Zhao, Xinfeng<xinfengx.zhao@intel.com<mailto:xinfengx.zhao@intel.com>>
> -----Original Message-----
> From: Dybkowski, AdamX <adamx.dybkowski at intel.com<https://mails.dpdk.org/listinfo/dev>>
> Sent: Thursday, February 20, 2020 3:04 PM
> To: dev at dpdk.org<https://mails.dpdk.org/listinfo/dev>; Trahe, Fiona <fiona.trahe at intel.com<https://mails.dpdk.org/listinfo/dev>>; akhil.goyal at nxp.com<https://mails.dpdk.org/listinfo/dev>
> Cc: Dybkowski, AdamX <adamx.dybkowski at intel.com<https://mails.dpdk.org/listinfo/dev>>; stable at dpdk.org<https://mails.dpdk.org/listinfo/dev>
> Subject: [PATCH] cryptodev: fix missing device id range checking
>
> This patch adds range-checking of the device id passed from
> the user app code. It prevents out-of-range array accesses
> which in some situations resulted in an
> application crash (segfault).
>
> Fixes: 3dd4435cf473 ("cryptodev: fix checks related to device id")
> Cc: stable at dpdk.org<https://mails.dpdk.org/listinfo/dev>
>
> Signed-off-by: Adam Dybkowski <adamx.dybkowski at intel.com<https://mails.dpdk.org/listinfo/dev>>
reply other threads:[~2020-03-20 0:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=99d93b95ec514defb664b15305fe073c@intel.com \
--to=xinfengx.zhao@intel.com \
--cc=dev@dpdk.org \
/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).