Ingo Molnar wrote:
> Also, kmemleak guarantees (assuming the implementation is correct) that
> if a leak happens in practice, it will be detected immediately.
> Coverity, being a static analyzer, wont find leaks that are obscured by
> some sort of complex codepath.
A good example is the skb allocation/freeing. I'm not sure Coverity is
able to track the code path in a protocol stack. I'll modify a network
driver to "forget" some skb freeing and test the kmemleak detection.
Catalin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
