Linux Driver Verification

h1. Benchmarking C Software Verifiers With LDV Tools

The core component of Linux Driver Verification tools is a verification tool for C language.  Static analysis of driver sources, instrumented with environment models and rules, are eventually passed to such verifier, which performs the most important part of the whole work.

No wonder that the speed and quality of the overall analysis heavily depends on how well and fast the verifier performs.  But the best verifier is yet to be found!  There are several static C verifiers, which perform differently, and without experimenting it''s not clear which one is the best for our purpose.  Moreover, verifiers usually contain a number of tweaks and configuration opportunities, which also are to explore.  

So one of the goals of LDV program is to build a framework that helps us in answering such questions, as:

* Which configuration of a verifier works faster on a test driver set?

* Which verifier checks more drivers within a given time limit?

* How would it affect verification, if we supply verifier with more memory?

We developed special components that gather, analyze, visualize and compare statistics of verification of a lot of different drivers.  The drivers can either be automatically fetched from a pre-assembled test set, or could be automatically extracted from the Linux Kernel.

h2. Visualization and comparison

Here''s a sample experiment.  We used a test set with some interesting drivers (fixed and unfixed versions of those, in which we used to find bugs), which is included in default shipment of LDV tools (it''s called @general@) to run compare SBE and LBE in "CPAchecker":http://cpachecker.sosy-lab.org/.  Here are the results:

!http://forge.ispras.ru/attachments/524/bench1.png!

From this table we could see that LBE is generally faster than SBE.  LBE verified more drivers (@Ok@ columnt), and nevertheless it spent less time to do it (see @Time OK@ column).  Also you can see that SBE version ran out of memory more often.

Now let''s see the improvements of LBE over SBE in detail.  We click radio button to set the task we compare against (we pick the "worse" one), and check box near the task we want to compare, and press the "Compare tasks" button at the top of the page.

!http://forge.ispras.ru/attachments/525/bench1a.png!

We get to a comparison page.  We see that some drivers that were Unknown to SBE, are detected as Safe or Unsafe in LBE, so LBE surpasses SBE.  However, we notice, that there were degradations: a driver with an error in it is detected by SBE, but is not by LBE (see the red circle):

!http://forge.ispras.ru/attachments/526/bench2.png!

We click the number to see what the driver was that:

!http://forge.ispras.ru/attachments/529/bench3.png!

Then we click the "left-hand" (LBE) ellipsis to see what the problem there is:

!http://forge.ispras.ru/attachments/528/bench4.png!

So it seems that LBE verification of that particular driver exceeds the memory limit for CPAchecker.  We searched  in the logs for a "message.ko", that had numbers "68_1" and 2.6.31.6 near it (see file @test_logs@ in your working dir), and found the command line for CPAchecker verifying this driver.

We could also click the ellipsis at the other side and then proceed to error trace, which would show us where SBE CPAchecker found the bug.  This would help in debugging.

h2. How to use LDV for benchmarking

To use this benchmarking system you should first "download sources":/projects/ldv/wiki/Downloading_and_Building_LDV of LDV tools (we recommend downloading the master branch).  After downloading we recommend you to refer to file @VerifierDevelopersHowTo@ (see source:VerifierDevelopersHowTo).  It will tell you how you should install and use LDV tools in order to specifically address benchmarking verification tools.  You will be able to easily change command line options, configuration files, vary time and memory limits.

Currently, only BLAST and CPAchecker verifiers are supported.  However, developing a convenient way to plug in other verifiers is on our roadmap.