DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: RE: Lgtm scan of DPDK
Date: Wed, 8 Jun 2022 08:35:45 +0000	[thread overview]
Message-ID: <DM6PR11MB32273B3A40B7777BE6280609FCA49@DM6PR11MB3227.namprd11.prod.outlook.com> (raw)
In-Reply-To: <5572850.DvuYhMxLoT@thomas>

> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, June 8, 2022 9:23 AM
> To: Stephen Hemminger <stephen@networkplumber.org>
> Cc: dev@dpdk.org; Mcnamara, John <john.mcnamara@intel.com>;
> david.marchand@redhat.com
> Subject: Re: Lgtm scan of DPDK
> 
> 28/05/2022 01:12, Stephen Hemminger:
> > I just discovered that there is another tool similar to Coverity for
> scanning.
> > It gives different results, and might be useful.
> > The scans of github open source projects is already done.
> >
> > See: https://lgtm.com/projects/g/DPDK/dpdk
> >
> > Shows 19 errors, 263 warnings and 111 recommendations.
> >
> > Of course, some of these are bogus. For example, tool thinks are scripts
> are Python 2.
> 
> The problem is that we already invest some time in Coverity triage to mark
> false positives.
> Can you check whether this tool has some false positives?

We looked at this tool a few years ago. 

Some of the good points were:

  * It is automatic and runs independently 
  * It did find some genuine issues
  * Issues have the commit ID associated with them so you could assign them to 

One of the main disadvantages was:

  * False positives can only be marked with a comment in the code

Nevertheless it is probably worth folks evaluating the issues in their own areas of code and in particular any of the Errors.

John





  reply	other threads:[~2022-06-08  8:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 23:12 Stephen Hemminger
2022-06-08  8:22 ` Thomas Monjalon
2022-06-08  8:35   ` Mcnamara, John [this message]
2022-06-09  2:36     ` Stephen Hemminger
2022-06-09 12:21       ` Mcnamara, John

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=DM6PR11MB32273B3A40B7777BE6280609FCA49@DM6PR11MB3227.namprd11.prod.outlook.com \
    --to=john.mcnamara@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    /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).