ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Peter Huewe <PeterHuewe@gmx.de>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] coverity, static checking etc.
Date: Wed, 14 May 2014 18:36:08 +0200	[thread overview]
Message-ID: <20140514163608.GH12911@katana> (raw)
In-Reply-To: <trinity-66028479-dfde-4cf7-8530-4cbe587ae018-1400082294215@3capp-gmx-bs51>

[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]

On Wed, May 14, 2014 at 05:44:54PM +0200, Peter Huewe wrote:
> > Ditto. I personally use 'C=1 CHECK="ninja-check"' which is a wrapper
> > which calls all static analyzers I know of.
> 
> +1 on ninja-check
> 
> Care to share your wrapper?

Here, be warned that there will be some output you need to get used to
;)


#!/bin/sh -u
# wrapper to call various static checkers for kernel builds.
# Use: make C=1 CHECK='ninja-check' ...
# done by Wolfram Sang in 2012-14, version 20140514 - WTFPLv2

check_for()
{
	command -v $1 > /dev/null
	ret=$?
	[ $ret -eq 0 ] && echo "    $1" | tr a-z A-Z
	return $ret
}

# Get filename (last argument)
eval file_to_check=\${$#}

check_for sparse && sparse -Wsparse-all "$@"

check_for smatch && smatch --project=kernel "$@" 1>&2

check_for cppcheck && cppcheck -f -q --template=gcc --enable=all --language=c "$file_to_check"

check_for spatch && MODE=report scripts/coccicheck "$file_to_check" 1>&2

check_for flawfinder && flawfinder --minlevel=0 --quiet --dataonly --singleline "$file_to_check" 1>&2

check_for rats && rats --resultsonly -w 3 "$file_to_check" 1>&2


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-05-14 16:36 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
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 [this message]
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=20140514163608.GH12911@katana \
    --to=wsa@the-dreams.de \
    --cc=PeterHuewe@gmx.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