DPDK patches and discussions
 help / color / mirror / Atom feed
From: Julien Cretin <julien.cretin@trust-in-soft.com>
To: "Wiles, Roger Keith" <keith.wiles@windriver.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Clang Scan build results
Date: Wed, 27 Aug 2014 17:55:07 +0000	[thread overview]
Message-ID: <40c32658a4b240f7a4745f95a317df21@S1688.EX1688.lan> (raw)
In-Reply-To: <CAG8AbRVgdnxeB9VEucY28KMX_a_v16hgBFBbqq_NgFoTBfcwcA@mail.gmail.com>

Hi all!

I took a look at the scan-results from Keith to compare with my analysis. My analysis is on test-pmd (called with a specific command-line and with start tx_first at the prompt) and scans exhaustively for all undefined behaviors (overflow, division by zero, invalid pointer dereference or comparison, etc.). The result (on the last revision of master) is that test-pmd is free from these kind of bugs in the perimeter of the analysis. This result comes from the fact that TrustInSoft Analyzer relies on formal methods and is sound: it does not remain silent about an undefined behavior. Of course there are false positives, but in my test-pmd analysis it happens that there is no alarms at all (neither false nor true).

Although the scan-build report contains false-positives (I found some related to my analysis) and is not exhaustive (false-negatives), it scans more code than my analysis (I don't look at drivers since I use a generic driver to exhaustively emulate all network behaviors, and I don't look at app/test which seems to contain also a lot of alarms).

I will soon make my analysis public and I regularly replay it on new versions of the master branch. Anyone interested can already contact me for more information.

Cheers,
Julien

  reply	other threads:[~2014-08-27 17:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27 15:13 Wiles, Roger Keith
2014-08-27 15:24 ` Jay Rolette
2014-08-27 15:52   ` Wiles, Roger Keith
2014-08-27 15:58     ` Jay Rolette
2014-08-27 16:09     ` Thomas Monjalon
2014-08-27 16:19       ` Wiles, Roger Keith
2014-08-27 17:02         ` Vincent JARDIN
2014-08-27 17:55           ` Julien Cretin [this message]
2014-08-28  3:00 ` Matthew Hall
2014-08-28  5:29   ` Wiles, Roger 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=40c32658a4b240f7a4745f95a317df21@S1688.EX1688.lan \
    --to=julien.cretin@trust-in-soft.com \
    --cc=dev@dpdk.org \
    --cc=keith.wiles@windriver.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).