From: "Laatz, Kevin" <kevin.laatz@intel.com>
To: Andrius Sirvys <andrius.sirvys@intel.com>, dev@dpdk.org
Cc: stable@dpdk.org, ciara.power@intel.com
Subject: Re: [dpdk-dev] [PATCH] usertools: replace unsafe input function
Date: Wed, 3 Apr 2019 11:31:09 +0100 [thread overview]
Message-ID: <00d20004-b191-51b3-55e3-776ff734b45e@intel.com> (raw)
Message-ID: <20190403103109.WLV5Eo-LAfYQ2CMiaG_5dSqmgng_I_lJh_NB7Sg3OmE@z> (raw)
In-Reply-To: <1553100181-32934-1-git-send-email-andrius.sirvys@intel.com>
On 20/03/2019 16:43, Andrius Sirvys wrote:
> LGTM static code analysis tool reports that the function 'input' is
> unsafe. Changed to use raw_input which then converts it using
> ast.literal_eval() which is safe.
>
> Fixes: d1b94da4a4e0 ("usertools: add client script for telemetry")
> Cc: ciara.power@intel.com
>
> Signed-off-by: Andrius Sirvys <andrius.sirvys@intel.com>
> ---
Looks good to me. Thanks!
Acked-by: Kevin Laatz <kevin.laatz@intel.com>
next prev parent reply other threads:[~2019-04-03 10:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 16:43 Andrius Sirvys
2019-03-20 16:43 ` Andrius Sirvys
2019-04-03 10:31 ` Laatz, Kevin [this message]
2019-04-03 10:31 ` Laatz, Kevin
2019-04-03 10:44 ` Burakov, Anatoly
2019-04-03 10:44 ` Burakov, Anatoly
2019-04-03 13:30 ` Bruce Richardson
2019-04-03 13:30 ` Bruce Richardson
2019-04-03 14:29 ` Burakov, Anatoly
2019-04-03 14:29 ` Burakov, Anatoly
2019-04-03 14:48 ` Burakov, Anatoly
2019-04-03 14:48 ` Burakov, Anatoly
2019-04-03 14:58 ` Burakov, Anatoly
2019-04-03 14:58 ` Burakov, Anatoly
2019-04-03 15:10 ` Richardson, Bruce
2019-04-03 15:10 ` Richardson, Bruce
2019-04-08 13:40 ` [dpdk-dev] [PATCH v2] " Andrius Sirvys
2019-04-08 13:40 ` Andrius Sirvys
2019-04-09 9:10 ` Burakov, Anatoly
2019-04-09 9:10 ` Burakov, Anatoly
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=00d20004-b191-51b3-55e3-776ff734b45e@intel.com \
--to=kevin.laatz@intel.com \
--cc=andrius.sirvys@intel.com \
--cc=ciara.power@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).