From: Thomas Monjalon <thomas@monjalon.net>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, yuwei1.zhang@intel.com, bruce.richardson@intel.com,
stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] eal: check string parameter lengths
Date: Thu, 17 Jan 2019 17:41:57 +0100 [thread overview]
Message-ID: <2838296.dFoSHF3S7s@xps> (raw)
In-Reply-To: <e749b4c6e38c0f87bbef130aabdf1d1aa6b90d2c.1547640738.git.anatoly.burakov@intel.com>
16/01/2019 13:12, Anatoly Burakov:
> When specifying parameters such as hugefile prefix from the
> command-line, it is possibly to supply an empty string. This may
> lead to various problems: for example, if hugefile prefix is
> empty, the runtime config path construction may end up
> looking like "/var/run/dpdk//_config", which will technically
> work, but is wrong and places files in the wrong place.
>
> To fix it, check lengths of such user-specified parameters for
> hugefile prefix, as well as hugepage dir and user-specified
> mbuf pool ops string.
>
> Cc: stable@dpdk.org
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
Applied, thanks
prev parent reply other threads:[~2019-01-17 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 12:12 [dpdk-stable] " Anatoly Burakov
2019-01-17 16:41 ` 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=2838296.dFoSHF3S7s@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=yuwei1.zhang@intel.com \
/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).