linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: davej@redhat.com (Dave Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [Ksummit-2013-discuss] [ARM ATTEND] catching up on exploit mitigations
Date: Thu, 1 Aug 2013 15:05:56 -0400	[thread overview]
Message-ID: <20130801190556.GA1495@redhat.com> (raw)
In-Reply-To: <20130801091322.GA5302@mwanda>

On Thu, Aug 01, 2013 at 12:13:22PM +0300, Dan Carpenter wrote:
 > I was just reading http://faultlinux.lip6.fr/ which says that in
 > 2011 the static checker fault rate in arch/ and fs/ was worse than
 > in drivers/

I've been working on getting more regular builds in coverity, so we can
get more meaningful statistics on things like "what area is getting worse".

Of the current bugs I've categorised so far, here's the breakdown for 3.11-rc3
in terms of highest bug counts.

Drivers/net/wireless: 659 
Drivers/ [1] : 600
Drivers/staging: 449
Drivers/scsi: 409
Drivers/net: 350
Net/[2] : 297
Drivers/media: 286
Sound: 220
Drivers/GPU: 217

That's the top categories for the whole kernel.

That wireless was top of the list was the least shocking thing to me,
based on what we get reported to Fedora bugzilla.  That it found more
bugs there than in staging was amusing though. The good news is that
wireless also takes the top slot for 'resolved' issues.

The paper above talks about 'arch' but doesn't indicate if it's counting
all arches, or just the one they run the tests on. (Coverity only covers x86,
so arch/ shows up in 10th place there).
FS doesn't show up on the list until 14th place, where there's a another
catchall category like [1][2]. The first actual fs category with the most
bugs is btrfs at 16th place, with 68 outstanding reports.

There's a lot of work to do picking through their database, including writing
modelling functions to reduce false positives. But, I'm on it.
I'll write up something a bit more in-depth later.

	Dave

[1] This is everything that doesn't match one of the more specific drivers category, 
    of which there's those mentioned above, plus about a dozen others.
[2] This is everything in net/ except for ipv4/ipv6/sctp, so all the weirdo protocols basically.

  reply	other threads:[~2013-08-01 19:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30 19:05 [ARM ATTEND] catching up on exploit mitigations Kees Cook
2013-07-30 22:14 ` [Ksummit-2013-discuss] " Dave Jones
2013-07-30 22:28   ` H. Peter Anvin
2013-07-31 13:55     ` Jason Cooper
2013-07-30 23:11   ` Aaro Koskinen
2013-07-30 23:15     ` Dave Jones
2013-07-30 23:33       ` Kees Cook
2013-07-31  0:01         ` H. Peter Anvin
2013-07-30 23:58       ` Aaro Koskinen
2013-07-31  0:04         ` Dave Jones
2013-07-31  9:40           ` Russell King - ARM Linux
2013-07-31 14:24             ` Dave Jones
2013-08-01  2:47               ` Olof Johansson
2013-08-01  2:59                 ` Dave Jones
2013-08-01 16:02                   ` Vince Weaver
2013-08-21 15:26               ` Russell King - ARM Linux
2013-08-21 15:43                 ` Dave Jones
2013-08-21 15:56                   ` Russell King - ARM Linux
2013-08-01  9:13 ` Dan Carpenter
2013-08-01 19:05   ` Dave Jones [this message]
2013-08-01 19:16     ` Dan Carpenter
2013-08-01 19:26       ` Julia Lawall
2013-08-03  0:03 ` Russell King - ARM Linux
2013-08-06 21:44   ` Kees Cook
2013-08-13  4:51 ` Laura Abbott
2013-08-26 19:56   ` Mark Brown
2013-08-27  2:09     ` Laura Abbott

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=20130801190556.GA1495@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).