From: "dan carpenter" <error27@email.com>
To: kernel-janitor-discuss@lists.sourceforge.net
Cc: smatch-discuss@lists.sf.net, linux-kernel@vger.kernel.org
Subject: smatch results for 2.5.66
Date: Fri, 28 Mar 2003 04:17:07 -0500 [thread overview]
Message-ID: <20030328091707.27905.qmail@email.com> (raw)
The 2.5.66 results for smatch are up on kbugs.org
Sadly, I haven't changed any of the scripts since
2.5.65. I did get some work done on the gcc part
but it turns out there is a problem and I had to
revert to diff-smatch-v.42 to compile the kernel. :(
mysql> select kernelver, script, count(script) from
bugs where kernelver = "2.5.65" or kernelver = "2.5.66"
group by script, kernelver;
+-----------+-------------------+---------------+
| kernelver | script | count(script) |
+-----------+-------------------+---------------+
| 2.5.65 | Dereference | 321 |
| 2.5.66 | Dereference | 263 |
| 2.5.65 | GFP_DMA | 5 |
| 2.5.66 | GFP_DMA | 2 |
| 2.5.65 | ReleaseRegion | 48 |
| 2.5.66 | ReleaseRegion | 48 |
| 2.5.65 | SpinlockUndefined | 44 |
| 2.5.66 | SpinlockUndefined | 33 |
| 2.5.65 | SpinSleepLazy | 6 |
| 2.5.66 | SpinSleepLazy | 5 |
| 2.5.65 | UncheckedReturn | 118 |
| 2.5.66 | UncheckedReturn | 74 |
| 2.5.65 | UnFree | 872 |
| 2.5.66 | UnFree | 660 |
| 2.5.65 | UnreachedCode | 28 |
| 2.5.66 | UnreachedCode | 25 |
+-----------+-------------------+---------------+
16 rows in set (0.22 sec)
As you can see, there were bug fixes all everywhere. :)
mysql> select kernelver, count(kernelver) from bugs
where kernelver = "2.5.65" or kernelver = "2.5.66"
group by kernelver;
+-----------+------------------+
| kernelver | count(kernelver) |
+-----------+------------------+
| 2.5.65 | 1442 |
| 2.5.66 | 1110 |
+-----------+------------------+
That's 332 bugs fixed. :)
regards,
dan carpenter
--
_______________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup
reply other threads:[~2003-03-28 9:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030328091707.27905.qmail@email.com \
--to=error27@email.com \
--cc=kernel-janitor-discuss@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=smatch-discuss@lists.sf.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
all inboxes | Powered by JetHome®