ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] coverity, static checking etc.
Date: Fri, 9 May 2014 16:33:07 -0400	[thread overview]
Message-ID: <20140509203307.GA20593@redhat.com> (raw)
In-Reply-To: <5857276.jy6b86PZuN@wuerfel>

On Fri, May 09, 2014 at 10:18:40PM +0200, Arnd Bergmann wrote:
 > On Friday 09 May 2014 13:07:09 Dave Jones wrote:
 > > I gave a lightning talk on this last year. This year I have a bit more data
 > > so could probably fill a whole session.
 > > 
 > > Last year I had been doing the coverity scans on an almost daily basis
 > > for 2-3 months.  Now that we're a year in, I'd like to share some
 > > results, and show some of the more common trends and bug patterns that
 > > seem to pop up.
 > > 
 > > [ spoiler: For the most part, it's all pretty positive, but we still suck ]
 > > 
 > > It would also be good to have some more discussion about other tools
 > > we could be making more use of.  (Nomination: Dan Carpenter for smatch).
 > 
 > I'd be interested in this. One thing I'd been meaning to ask you about
 > for ages is what I can do to get scan results for ARM (or any other
 > architecture for that matter) specific code. We have a lot of that these
 > days, and as I understand it, the results on the public website are just
 > for x86 builds.

yeah, right now their tool (definitely front-end, but back-end too iirc)
is x86 only.   So unless it's something that CONFIG_COMPILE_TEST would pick up,
it's not going to be in the scans.

	Dave

  reply	other threads:[~2014-05-09 20:33 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09 17:07 Dave Jones
2014-05-09 17:19 ` josh
2014-05-09 17:31   ` Johannes Berg
2014-05-09 17:54     ` Guenter Roeck
2014-05-09 18:04     ` Mark Brown
2014-05-09 19:08     ` Jiri Kosina
2014-05-09 19:41       ` Dmitry Torokhov
2014-05-09 19:29     ` Josh Triplett
2014-05-09 17:37 ` Bjorn Helgaas
2014-05-09 20:18 ` Arnd Bergmann
2014-05-09 20:33   ` Dave Jones [this message]
2014-05-09 21:39     ` Arnd Bergmann
2014-05-09 20:33 ` Roland Dreier
2014-05-09 20:52   ` Dave Jones
2014-05-09 20:57 ` tytso
2014-05-14 11:06   ` Dan Carpenter
2014-05-11 11:10 ` Wolfram Sang
2014-05-12  6:48   ` Michal Simek
2014-05-12  9:32     ` Wolfram Sang
2014-05-14 11:09       ` Dan Carpenter
2014-05-14 13:32       ` Johannes Berg
2014-05-14 13:51         ` Guenter Roeck
2014-05-14 15:22           ` Wolfram Sang
2014-05-14 15:44             ` Peter Huewe
2014-05-14 16:36               ` Wolfram Sang
2014-05-18 16:38     ` Mauro Carvalho Chehab
2014-05-19 10:13       ` Michal Simek
2014-05-12  8:58   ` Peter Senna Tschudin

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=20140509203307.GA20593@redhat.com \
    --to=davej@redhat.com \
    --cc=arnd@arndb.de \
    --cc=ksummit-discuss@lists.linuxfoundation.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