From: Thomas Monjalon <thomas@monjalon.net>
To: Reshma Pattan <reshma.pattan@intel.com>
Cc: stable@dpdk.org, "Hunt, David" <david.hunt@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] examples/vm_power_manager: fix string overflow
Date: Mon, 22 Apr 2019 23:09:58 +0200 [thread overview]
Message-ID: <1853067.ZkMTqVCtyj@xps> (raw)
Message-ID: <20190422210958.PWjeeOqpuoFiMO8XlgWU-dhFweuOq3wNMMgVSm1nmsY@z> (raw)
In-Reply-To: <bd0104b3-53c1-56b5-e0f9-3f7566c45f26@intel.com>
15/04/2019 16:45, Hunt, David:
> On 10/4/2019 3:54 PM, Reshma Pattan wrote:
> > Use strlcpy instead of strcpy to fix string overflow.
> >
> > Coverity issue: 337671
> > Fixes: a63504a90f ("examples/power: add JSON string handling")
> > CC: david.hunt@intel.com
> > CC: stable@dpdk.org
> >
> > Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>
>
> Acked-by: David Hunt <david.hunt@intel.com>
Applied, thanks
next prev parent reply other threads:[~2019-04-22 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 14:54 [dpdk-dev] " Reshma Pattan
2019-04-10 14:54 ` Reshma Pattan
2019-04-15 14:45 ` Hunt, David
2019-04-15 14:45 ` Hunt, David
2019-04-22 21:09 ` Thomas Monjalon [this message]
2019-04-22 21:09 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
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=1853067.ZkMTqVCtyj@xps \
--to=thomas@monjalon.net \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--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).