From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Alejandro Lucero <alejandro.lucero@netronome.com>
Cc: Pallantla Poornima <pallantlax.poornima@intel.com>,
dev <dev@dpdk.org>,
reshma.pattan@intel.com, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v2] net/nfp: fix possible buffer overflow
Date: Thu, 21 Mar 2019 17:03:57 +0000 [thread overview]
Message-ID: <264796ee-11e8-f665-0177-3974169ed6ba@intel.com> (raw)
In-Reply-To: <CAD+H992aDFZNGRYpk1eTc16juhr+CC1aanA8mm6Q45UD96GNtQ@mail.gmail.com>
On 3/21/2019 10:10 AM, Alejandro Lucero wrote:
>
>
> On Tue, Mar 19, 2019 at 5:43 PM Ferruh Yigit <ferruh.yigit@intel.com
> <mailto:ferruh.yigit@intel.com>> wrote:
>
> On 3/12/2019 9:56 AM, Alejandro Lucero wrote:
> > On Fri, Mar 8, 2019 at 10:28 AM Pallantla Poornima <
> > pallantlax.poornima@intel.com <mailto:pallantlax.poornima@intel.com>> wrote:
> >
> >> sprintf function is not secure as it doesn't check the length of string.
> >> More secure function snprintf is used.
> >>
> >> Fixes: 896c265ef9 ("net/nfp: use new CPP interface")
> >> Fixes: c4171b520b ("net/nfp: support PF multiport")
> >> Cc: stable@dpdk.org <mailto:stable@dpdk.org>
> >>
> >> Signed-off-by: Pallantla Poornima <pallantlax.poornima@intel.com>
>
> Acked-by: Alejandro Lucero <alejandro.lucero@netronome.com>
> Tested-by: Alejandro Lucero <alejandro.lucero@netronome.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2019-03-21 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 10:28 Pallantla Poornima
2019-03-12 9:56 ` Alejandro Lucero
2019-03-19 17:43 ` Ferruh Yigit
2019-03-21 10:10 ` Alejandro Lucero
2019-03-21 17:03 ` Ferruh Yigit [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=264796ee-11e8-f665-0177-3974169ed6ba@intel.com \
--to=ferruh.yigit@intel.com \
--cc=alejandro.lucero@netronome.com \
--cc=dev@dpdk.org \
--cc=pallantlax.poornima@intel.com \
--cc=reshma.pattan@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).