patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Keith Wiles <keith.wiles@intel.com>, dev@dpdk.org
Cc: dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v4] net/tap: fix coverity warning on strncpy
Date: Fri, 17 Feb 2017 16:21:53 +0000	[thread overview]
Message-ID: <37245ce5-de84-27fb-14a7-36ad8934a8d6@intel.com> (raw)
In-Reply-To: <20170217154304.50214-1-keith.wiles@intel.com>

On 2/17/2017 3:43 PM, Keith Wiles wrote:
> Calling strncpy with a maximum size argument of 16 bytes on destination
> array "ifr.ifr_ifrn.ifrn_name" of size 16 bytes might leave the
> destination string unterminated.
> 
> Signed-off-by: Keith Wiles <keith.wiles@intel.com>

    net/tap: fix possibly unterminated string

    Coverity issue: 1407499
    Fixes: 6b38b2725cdb ("net/tap: fix multi-queue support")
    Cc: stable@dpdk.org

Applied to dpdk-next-net/master, thanks.


(Updates:
- patch title:
It is preferred to mention from problem solved instead of the tool that
found it.

- Added coverity tag:
This helps to trace coverity issues, defined syntax is:

    Coverity issue: xxx
    Fixes: yyyy

- Added Cc: tag for stable tree:
In case stable tree wants get this patch, to make patch visible.
)

       reply	other threads:[~2017-02-17 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170217154304.50214-1-keith.wiles@intel.com>
2017-02-17 16:21 ` Ferruh Yigit [this message]
2017-02-17 16:34   ` Wiles, Keith
2017-02-17 16:48     ` Ferruh Yigit
2017-02-17 16:53       ` Wiles, Keith

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=37245ce5-de84-27fb-14a7-36ad8934a8d6@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=keith.wiles@intel.com \
    --cc=stable@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).