DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: Stephen Hemminger <shemming@brocade.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Coverity policy for upstream (base) drivers.
Date: Thu, 12 Nov 2015 17:55:11 -0500	[thread overview]
Message-ID: <20151112225511.GA10012@mhcomputing.net> (raw)
In-Reply-To: <20151112140508.79489210@xeon-e3>

On Thu, Nov 12, 2015 at 02:05:08PM -0800, Stephen Hemminger wrote:
> Looking at the Coverity scan for DPDK, it looks like all the base
> drivers are marked to be ignored.
> 
> Although the changes to base drivers should not be done directly through
> DPDK list. I think it is still valuable to have these driver scanned and
> notify (badger) the vendors to fix there code.
> 
> Since lots of the bugs could be there, just blindly ignoring warnings
> and issues is being naive.

I am with Stephen. Ignoring base driver vulns is a bad practice.

With these L1-L4 bugs the chances are good somebody could trigger these and 
find 0days using tools as old and simple as this one:

http://isic.sourceforge.net/

Matthew.

  parent reply	other threads:[~2015-11-12 22:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12 22:05 Stephen Hemminger
2015-11-12 22:18 ` Thomas Monjalon
2015-11-13  0:16   ` Mcnamara, John
2015-11-12 22:55 ` Matthew Hall [this message]
2015-11-13  0:12 ` Mcnamara, John
2015-11-13 18:49   ` Matthew Hall
2015-11-13 19:21     ` Mcnamara, John
2015-11-13 19:23       ` Matthew Hall
2015-11-13 19:38       ` Stephen Hemminger
2015-11-13 20:20         ` Matthew Hall

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=20151112225511.GA10012@mhcomputing.net \
    --to=mhall@mhcomputing.net \
    --cc=dev@dpdk.org \
    --cc=shemming@brocade.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).