From: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
To: "Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Griffin, John" <john.griffin@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
"Jain, Deepak K" <deepak.k.jain@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] crypto/qat: fix possible access to an uninitialized variable
Date: Wed, 16 Dec 2020 06:34:59 +0000 [thread overview]
Message-ID: <CY4PR11MB1830854EDC3C3A07DEF6B6D29FC50@CY4PR11MB1830.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1608056631-400065-1-git-send-email-vladimir.medvedkin@intel.com>
> -----Original Message-----
> From: Medvedkin, Vladimir <vladimir.medvedkin@intel.com>
> Sent: wtorek, 15 grudnia 2020 19:24
> To: dev@dpdk.org
> Cc: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>; Griffin, John
> <john.griffin@intel.com>; Trahe, Fiona <fiona.trahe@intel.com>; Jain, Deepak K
> <deepak.k.jain@intel.com>; stable@dpdk.org
> Subject: [PATCH] crypto/qat: fix possible access to an uninitialized variable
>
> QAT_LOG() has access to the uninitialized variable "name"
>
> Fixes: 21792c443205 ("crypto/qat: add multi-process handling of driver ID")
> Cc: stable@dpdk.org
>
> Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
> ---
> 2.7.4
Acked-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
next prev parent reply other threads:[~2020-12-16 6:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 18:23 Vladimir Medvedkin
2020-12-16 6:34 ` Kusztal, ArkadiuszX [this message]
2021-01-15 16:00 ` Akhil Goyal
2020-12-16 11:47 ` [dpdk-stable] [dpdk-dev] " Doherty, Declan
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=CY4PR11MB1830854EDC3C3A07DEF6B6D29FC50@CY4PR11MB1830.namprd11.prod.outlook.com \
--to=arkadiuszx.kusztal@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=john.griffin@intel.com \
--cc=stable@dpdk.org \
--cc=vladimir.medvedkin@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).