From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Daniel Mrzyglod <danielx.t.mrzyglod@intel.com>
Cc: huawei.xie@intel.com, przemyslaw.czesnowicz@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] vhost: fix buffer not null terminated
Date: Tue, 10 May 2016 11:27:13 -0700 [thread overview]
Message-ID: <20160510182713.GU5641@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <1462896678-40929-1-git-send-email-danielx.t.mrzyglod@intel.com>
On Tue, May 10, 2016 at 06:11:18PM +0200, Daniel Mrzyglod wrote:
> Fix issue reported by Coverity.
> Coverity ID 124556
>
> If the buffer is treated as a null terminated string in later operations,
> a buffer overflow or over-read may occur.
>
> In vhost_set_ifname: The string buffer may not have a null terminator if
> the source string's length is equal to the buffer size
>
> Fixes: 54292e9520e0 ("vhost: support ifname for vhost-user")
>
> Signed-off-by: Daniel Mrzyglod <danielx.t.mrzyglod@intel.com>
Applied to dpdk-next-virtio.
Thanks.
--yliu
prev parent reply other threads:[~2016-05-10 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 16:11 Daniel Mrzyglod
2016-05-10 18:27 ` 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=20160510182713.GU5641@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=danielx.t.mrzyglod@intel.com \
--cc=dev@dpdk.org \
--cc=huawei.xie@intel.com \
--cc=przemyslaw.czesnowicz@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).