Re: smatch warnings in current upstream kernel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Sep 11, 2012 at 01:51:27PM +0300, Dan Carpenter wrote:
> On Tue, Sep 11, 2012 at 06:10:02PM +0800, Fengguang Wu wrote:
> > Here are the 7161 smatch warnings for 2139 files in upstream head
> > 1a95620f45155ac523cd1419d89150fbb4eb858b.  It's not a complete build
> > (no make clean), so does not include all possible warnings.
> > 
> 
> There are some sparse warnings mixed in as well.  They would have
> been sent to stderr and smatch warnings get sent to stdout.

Thanks for pointing this out!

> But if you want you could look at smatch_scripts/test_kernel.sh
> which allows for a parallel build and saves all the warnings in
> warns.txt.
 
Yeah I looked at the script, however did not want to touch the source
tree, so...

> I guess you have your own parallel build technique as well and that
> works too.

I have a tiny smatch wrapper script for passing to CHECK=.
According to your advice, I will only save its stdout:

$SMATCH -p kernel "$@" > $SMATCH_OUT_ROOT/$PPID-$$-$RANDOM

Thanks,
Fengguang
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Kernel Development]     [Kernel Announce]     [Kernel Newbies]     [Linux Networking Development]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Device Mapper]

  Powered by Linux