DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jingjing Wu <jingjing.wu@intel.com>
To: david.marchand@6wind.com
Cc: dev@dpdk.org, jingjing.wu@intel.com, ziye.yang@intel.com,
	bruce.richardson@intel.com
Subject: [dpdk-dev] [PATCH] doc: known issue on EAL argv
Date: Fri, 13 May 2016 13:14:49 +0800	[thread overview]
Message-ID: <1463116489-31805-1-git-send-email-jingjing.wu@intel.com> (raw)

This patch docs the issue on EAL argument that the last EAL
argument is replaced by program name in argv[].

Reported-by: Ziye Yang <ziye.yang@intel.com>
Signed-off-by: Jingjing Wu <jingjing.wu@intel.com>
---
 doc/guides/rel_notes/known_issues.rst | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst
index 923a202..9f03733 100644
--- a/doc/guides/rel_notes/known_issues.rst
+++ b/doc/guides/rel_notes/known_issues.rst
@@ -618,3 +618,22 @@ DPDK may not build on some Intel CPUs using clang < 3.7.0
 
 **Driver/Module**:
    Environment Abstraction Layer (EAL).
+
+
+The last EAL argument is replaced by program name in argv[]
+-----------------------------------------------------------
+
+**Description**:
+   The last EAL argument will be replaced by program name in argv[] after eal_parse_args, and it causes the pointer to the last EAL argument lost.
+
+**Implication**:
+  If the last EAL argument in argv is generated by malloc function, changing it will cause memory issues when free the argument.
+
+**Resolution/Workaround**:
+   Application should not consider the value in argv[] as unchanged.
+
+**Affected Environment/Platform**:
+   ALL.
+
+**Driver/Module**:
+   Environment Abstraction Layer (EAL).
-- 
2.4.0

             reply	other threads:[~2016-05-13  5:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-13  5:14 Jingjing Wu [this message]
2016-05-16 13:01 ` Mcnamara, John
2016-05-23 14:24 ` [dpdk-dev] [PATCH v2] doc: add known issue with " Jingjing Wu
2016-06-09  8:58   ` Mcnamara, John
2016-06-14 14:58     ` 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=1463116489-31805-1-git-send-email-jingjing.wu@intel.com \
    --to=jingjing.wu@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@6wind.com \
    --cc=dev@dpdk.org \
    --cc=ziye.yang@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).