From: Yuanhan Liu <yliu@fridaylinux.org>
To: SebastianX Basierski <sebastianx.basierski@intel.com>
Cc: skhare@vmware.com, jianfeng.tan@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] pmd_virtio: Buffer not null terminated
Date: Mon, 9 Oct 2017 11:07:02 +0800 [thread overview]
Message-ID: <20171009030701.GK1545@yliu-home> (raw)
In-Reply-To: <1505821264-33518-1-git-send-email-sebastianx.basierski@intel.com>
On Tue, Sep 19, 2017 at 01:41:04PM +0200, SebastianX Basierski wrote:
> Fix calling strncpy with the a maximum size equal of destination
> array size.
>
> Coverity issue: 140732
>
> Fixes: e3b434818bbb ("net/virtio-user: support kernel vhost")
> Cc: jianfeng.tan@intel.com
> cc: dev@dpdk.org
>
> Signed-off-by: SebastianX Basierski <sebastianx.basierski@intel.com>
Applied to dpdk-next-virtio.
Thanks.
--yliu
prev parent reply other threads:[~2017-10-09 3:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 11:41 SebastianX Basierski
2017-09-20 0:52 ` Tan, Jianfeng
2017-09-20 9:19 ` Basierski, SebastianX
2017-09-20 9:41 ` Tan, Jianfeng
2017-10-09 3:07 ` Yuanhan Liu [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=20171009030701.GK1545@yliu-home \
--to=yliu@fridaylinux.org \
--cc=dev@dpdk.org \
--cc=jianfeng.tan@intel.com \
--cc=sebastianx.basierski@intel.com \
--cc=skhare@vmware.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).