diff options
| author | Sanjeev Gupta <ghane0@gmail.com> | 2014-09-01 16:48:17 +0800 |
|---|---|---|
| committer | Eric S. Raymond <esr@thyrsus.com> | 2014-09-04 14:43:53 -0400 |
| commit | 844ea0d830d87743f11993780e5a895e4118cef0 (patch) | |
| tree | e204574627201dd60fbffee679a1b8967f9cb954 | |
| parent | d8a3634921a8f1ff4e8261e6b3795d66bd769f21 (diff) | |
| download | gpsd-844ea0d830d87743f11993780e5a895e4118cef0.tar.gz | |
Minor reformatting
| -rw-r--r-- | www/reliability.html | 14 |
1 files changed, 10 insertions, 4 deletions
diff --git a/www/reliability.html b/www/reliability.html index 70dc2916..b00b8adf 100644 --- a/www/reliability.html +++ b/www/reliability.html @@ -88,10 +88,16 @@ often. This makes it actively difficult for random code changes to break our device drivers without somebody noticing.</p> <p>Which isn't to say those drivers can't be wrong, just that the ways -they can be wrong are constrained to be through either (a) a -protocol-spec-level misunderstanding of what the driver is supposed to -be doing, or (b) an implementation bug somewhere in the program's -state space that is obscure and difficult to reach. Coverity only +they can be wrong are constrained to be through either +<ol> +<li> a protocol-spec-level misunderstanding of what the driver is +supposed to be doing, or </li> +<li> an implementation bug somewhere in the program's +state space that is obscure and difficult to reach. </li> +</ol> +</p> + +<p>Coverity only turned up two driver bugs - static buffer overruns in methods for changing the device's reporting protocol and line speed that escaped notice because they can't be checked in our test harnesses but only on |