From: Thomas Monjalon <thomas@monjalon.net>
To: David Hunt <david.hunt@intel.com>
Cc: dev@dpdk.org, "Burakov, Anatoly" <anatoly.burakov@intel.com>,
stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] examples/vm_power_manager: fix string null termination
Date: Fri, 03 May 2019 01:43:41 +0200 [thread overview]
Message-ID: <2238935.MQL5HepLSp@xps> (raw)
Message-ID: <20190502234341.pLT-OkkrPO35i1Ppek9tW0NcGywguOUIpR5n_qfhrSY@z> (raw)
In-Reply-To: <691b68a8-8663-3dcc-72d3-d9c16eda788b@intel.com>
26/04/2019 16:10, Burakov, Anatoly:
> On 26-Apr-19 3:04 PM, David Hunt wrote:
> > coverity complains about a null-termination after a read,
> > so we terminate once we exit the do-while read loop.
> >
> > Coverity issue: 337680
> > Fixes: a63504a90f ("examples/power: add JSON string handling")
> > CC: stable@dpdk.org
> >
> > Signed-off-by: David Hunt <david.hunt@intel.com>
>
> Reviewed-by: Anatoly Burakov <anatoly.burakov@intel.com>
Applied, thanks
PS: replaced "string" with "json" in title to give a bit more context.
next prev parent reply other threads:[~2019-05-02 23:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 8:43 [dpdk-dev] [PATCH v1] " David Hunt
2019-04-26 8:43 ` David Hunt
2019-04-26 10:33 ` Burakov, Anatoly
2019-04-26 10:33 ` Burakov, Anatoly
2019-04-26 11:16 ` Hunt, David
2019-04-26 11:16 ` Hunt, David
2019-04-26 11:24 ` [dpdk-dev] [PATCH v2] " David Hunt
2019-04-26 11:24 ` David Hunt
2019-04-26 11:56 ` Burakov, Anatoly
2019-04-26 11:56 ` Burakov, Anatoly
2019-04-26 12:31 ` Bruce Richardson
2019-04-26 12:31 ` Bruce Richardson
2019-04-26 12:47 ` Burakov, Anatoly
2019-04-26 12:47 ` Burakov, Anatoly
2019-04-26 14:04 ` [dpdk-dev] [PATCH v3] " David Hunt
2019-04-26 14:04 ` David Hunt
2019-04-26 14:10 ` Burakov, Anatoly
2019-04-26 14:10 ` Burakov, Anatoly
2019-05-02 23:43 ` Thomas Monjalon [this message]
2019-05-02 23:43 ` 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=2238935.MQL5HepLSp@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--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).