From: Thomas Monjalon <thomas@monjalon.net>
To: Andrius Sirvys <andrius.sirvys@intel.com>
Cc: stable@dpdk.org, dev@dpdk.org, kevin.laatz@intel.com,
ciara.power@intel.com
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v3] usertools: replace unsafe input function
Date: Wed, 31 Jul 2019 00:10:00 +0200 [thread overview]
Message-ID: <2451801.hgv5LbryIF@xps> (raw)
In-Reply-To: <1554731681-98256-1-git-send-email-andrius.sirvys@intel.com>
08/04/2019 15:54, Andrius Sirvys:
> 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>
> Acked-by: Kevin Laatz <kevin.laatz@intel.com>
This patch was forgotten.
Applied, thanks
prev parent reply other threads:[~2019-07-30 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11554730848-97709-1-git-send-email-andrius.sirvys@intel.com>
2019-04-08 13:54 ` [dpdk-dev] " Andrius Sirvys
2019-04-08 13:54 ` Andrius Sirvys
2019-07-30 22:10 ` 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=2451801.hgv5LbryIF@xps \
--to=thomas@monjalon.net \
--cc=andrius.sirvys@intel.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=kevin.laatz@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).