From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
Stephen Hemminger <shemming@brocade.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Coverity policy for upstream (base) drivers.
Date: Fri, 13 Nov 2015 00:16:10 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2023BAF48@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <3288160.AgV0ATSvM7@xps13>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Thursday, November 12, 2015 10:19 PM
> To: Stephen Hemminger
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] Coverity policy for upstream (base) drivers.
>
> 2015-11-12 14:05, Stephen Hemminger:
> > 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 think the Coverity setup is outdated:
> ignore_driver_1 /lib/librte_pmd_e1000/e1000/.* Yes Remove
> ignore_driver_2 /lib/librte_pmd_fm10k/base/.* Yes Remove
> ignore_driver_3 /lib/librte_pmd_i40e/i40e/.* Yes Remove
> ignore_driver_4 /lib/librte_pmd_ixgbe/ixgbe/.* Yes Remove
>
> These directories don't exist anymore.
Hi Thomas,
The directories don't exist anymore but code from those directories is still in the Coverity database from prior to the restructuring.
There is a new rule to ignore the new base drivers:
ignore_base_code /drivers/net/*/base/* Yes
John
--
next prev parent reply other threads:[~2015-11-13 0:16 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 [this message]
2015-11-12 22:55 ` Matthew Hall
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=B27915DBBA3421428155699D51E4CFE2023BAF48@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=shemming@brocade.com \
--cc=thomas.monjalon@6wind.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).