From: Remy Horton <remy.horton@intel.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v1] metrics: fix potential missing NULL termination
Date: Tue, 20 Feb 2018 15:32:50 +0000 [thread overview]
Message-ID: <b3865609-d975-dc0d-00c6-778e6a70e474@intel.com> (raw)
In-Reply-To: <20180220151113.GB14804@bricha3-MOBL3.ger.corp.intel.com>
On 20/02/2018 15:11, Bruce Richardson wrote:
[..]
> Again, I think the better fix is to replace strncpy with snprintf which
> will guarantee the null termination, unlike strncpy which is nasty that
> way.
OK, v2 on way..
next prev parent reply other threads:[~2018-02-20 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 14:50 Remy Horton
2018-02-20 15:11 ` Bruce Richardson
2018-02-20 15:32 ` Remy Horton [this message]
2018-02-20 16:05 ` [dpdk-dev] [PATCH v2] " Remy Horton
2018-03-22 10:33 ` Ferruh Yigit
2018-04-04 14:09 ` 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=b3865609-d975-dc0d-00c6-778e6a70e474@intel.com \
--to=remy.horton@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@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).