From: Luca Boccassi <bluca@debian.org>
To: dpdk-dev <dev@dpdk.org>
Cc: John McNamara <john.mcnamara@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 21/2/2019
Date: Wed, 06 Mar 2019 15:27:32 +0000 [thread overview]
Message-ID: <a82d2d1bed9e1250b2afd5ba643781487131447b.camel@debian.org> (raw)
In-Reply-To: <3eff7705bf6958382a727d35f786469a83479b1c.camel@debian.org>
On Thu, 2019-02-21 at 17:43 +0000, Luca Boccassi wrote:
> On Thu, 2019-02-21 at 16:09 +0000, Ferruh Yigit wrote:
> > Minutes 21 February 2019
> > ------------------------
>
> cut
>
> > * Coverity is partially back, but new analyses aren't running
> > * Looking for suggestions from the community for a better or more
> > stable
> > solutions
>
> The clang-based alternative I mentioned that can be used from
> Travis/Github is sonarcloud.io:
>
> https://sonarcloud.io/
>
> Here's an example implementation:
>
> https://github.com/zeromq/libzmq/commit/4d3516f634a4a5e3f522f5cb277da38b188d32eb
I've tested Sonarcloud, they are saying DPDK stinks (22000 code smells
flagged) :-)
https://sonarcloud.io/dashboard?id=bluca_dpdk
It seems the main "security" issues it highlights are the usage of
sprintf, strcpy and strcat. They can probably be easily filtered out.
The job on Travis takes about half an hour, so perhaps it's better as a
weekly run.
Integration is quite simple, based on the yet unmerged Travis patch:
https://github.com/bluca/dpdk/commit/ef4f3c8bdc1b044e19d466efb9ba6fc0a3af4220
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2019-03-06 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 16:09 Ferruh Yigit
2019-02-21 16:19 ` Thomas Monjalon
2019-02-21 17:43 ` Luca Boccassi
2019-02-21 18:16 ` Thomas Monjalon
2019-03-06 15:27 ` Luca Boccassi [this message]
2019-03-06 15:45 ` Richardson, Bruce
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=a82d2d1bed9e1250b2afd5ba643781487131447b.camel@debian.org \
--to=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--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).