From: Thomas Monjalon <thomas@monjalon.net>
To: Pallantla Poornima <pallantlax.poornima@intel.com>
Cc: stable@dpdk.org, Akhil Goyal <akhil.goyal@nxp.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"reshma.pattan@intel.com" <reshma.pattan@intel.com>,
"rosen.xu@intel.com" <rosen.xu@intel.com>,
Nipun Gupta <nipun.gupta@nxp.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Gagandeep Singh <G.Singh@nxp.com>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] drivers: fix sprintf with snprintf
Date: Mon, 14 Jan 2019 23:20:36 +0100 [thread overview]
Message-ID: <2042298.Yq3qeJguyr@xps> (raw)
In-Reply-To: <e4bc508f-faac-99c2-a098-511668beb3b0@nxp.com>
09/01/2019 15:47, Akhil Goyal:
> On 1/7/2019 4:16 PM, Pallantla Poornima wrote:
> > sprintf function is not secure as it doesn't check the length of string.
> > More secure function snprintf is used
> >
> > Fixes: 828d51d8fc ("bus/fslmc: refactor scan and probe functions")
> > Fixes: c22fab9a6c ("raw/dpaa2_qdma: support configuration APIs")
> > Fixes: e5cbdfc537 ("crypto/dpaa2_sec: add basic operations")
> > Fixes: b23d4e898a ("crypto/dpaa2_sec: add per dev mempool to store FLE")
> > Fixes: 623326dded ("crypto/dpaa2_sec: introduce poll mode driver")
> > Fixes: e7a45f3cc2 ("crypto/caam_jr: add UIO specific operations")
> > Fixes: f44bccadd8 ("crypto/caam_jr: add device basic operations")
> > Fixes: 7e3e2954e0 ("crypto/dpaa_sec: move mempool allocation to config")
> > Fixes: c3e85bdcc6 ("crypto/dpaa_sec: add crypto driver for NXP DPAA platform")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Pallantla Poornima <pallantlax.poornima@intel.com>
> > ---
> >
> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
Applied, thanks
prev parent reply other threads:[~2019-01-14 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 10:46 [dpdk-stable] " Pallantla Poornima
2019-01-09 14:47 ` [dpdk-stable] [dpdk-dev] " Akhil Goyal
2019-01-14 22:20 ` 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=2042298.Yq3qeJguyr@xps \
--to=thomas@monjalon.net \
--cc=G.Singh@nxp.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=nipun.gupta@nxp.com \
--cc=pallantlax.poornima@intel.com \
--cc=reshma.pattan@intel.com \
--cc=rosen.xu@intel.com \
--cc=stable@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).