Re: [Ksummit-discuss] coverity, static checking etc.

[Johannes Berg <johannes@sipsolutions.net>]

On Fri, 2014-05-09 at 10:19 -0700, josh@joshtriplett.org wrote:

> I'd like to see this topic as well.  I think we could do a lot better
> here than we do.  And don't forget that GCC is one of our top static
> analysis tools, if only because it's the only one *everyone* runs; that
> includes both warnings and the possibility of shipping and building our
> own GCC plugin.
> 
> I'd also like to nominate Christopher Li, for Sparse.

Seconded, I'm also interested in general in whether people still think
sparse is useful and we should give it attention, or should focus more
on really getting everything into gcc - we have a number of sparse
warnings in very low-level header files that get used everywhere, for
example the one I just fixed in [1] or the one I tried to fix but that
ended up being buggy ([2]), but there doesn't seem to be much attention
to these during the patch submission etc.

johannes

[1] http://thread.gmane.org/gmane.linux.kernel/1699192
[2] http://thread.gmane.org/gmane.linux.kernel/1642101/focus=1642108