From: "Zhao, XinfengX" <xinfengx.zhao@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Dybkowski, AdamX" <adamx.dybkowski@intel.com>
Subject: Re: [dpdk-dev] [PATCH] cryptodev: fix missing device id range checking
Date: Fri, 13 Mar 2020 06:31:12 +0000 [thread overview]
Message-ID: <55eaf4b947074ab682ad3f950f159fe6@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>>
next reply other threads:[~2020-03-13 6:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 6:31 Zhao, XinfengX [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-20 15:04 [dpdk-dev] [PATCH] cryptodev: fix missing device id range checking Adam Dybkowski
2020-02-20 15:39 ` Trahe, Fiona
2020-03-13 7:19 ` Akhil Goyal
2020-03-25 19:11 ` Akhil Goyal
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=55eaf4b947074ab682ad3f950f159fe6@intel.com \
--to=xinfengx.zhao@intel.com \
--cc=adamx.dybkowski@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.