From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ming Zhao <mzhao@luminatewireless.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] Fix buffer overflow issue in app/test/commands.c(we add 1 extra byte for trailing \0).
Date: Sat, 05 Mar 2016 23:09:52 +0100 [thread overview]
Message-ID: <1495521.iYHtmlEZSL@xps13> (raw)
In-Reply-To: <1456470671-18425-1-git-send-email-mzhao@luminatewireless.com>
Hi,
2016-02-25 23:11, Ming Zhao:
> Fix memleak of cmdline in app/test/test.c
It looks to be two different fixes:
- an overflow
- a memleak
Please send 2 patches,
with Fixes lines (even if is there since the first commit),
with Signed-off-by line.
See http://dpdk.org/doc/guides/contributing/patches.html#commit-messages-subject-line
prev parent reply other threads:[~2016-03-05 22:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 7:11 Ming Zhao
2016-03-05 22:09 ` 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=1495521.iYHtmlEZSL@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=mzhao@luminatewireless.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).