Weekly edition	Kernel	Security	Distributions	Contact Us	Search
Archives	Calendar	Subscribe	Write for LWN	LWN.net FAQ	Sponsors

Double kfree() errors

Posted Mar 9, 2006 15:57 UTC (Thu) by mbligh (subscriber, #7720)
Parent article: Double kfree() errors

Eh, no idea why I didn't fix this a year ago. I'll arrange with Andy to run a debug kernel with CONFIG_DEBUG_SLAB as well as a few other debug bits, and I can create a separate matrix on http://test.kernel.org for the debug runs - will fold it more nicely later. That should do every -git snapshot, and every -mm, etc across a variety of machines.

(Log in to post comments)

Posted Mar 10, 2006 0:46 UTC (Fri) by davej (subscriber, #354) [Link]

A lot of problems we've seen in Fedora bugzilla from our slab debug kernels have been driver specific though (or out-of-tree junk which is another great argument for 'poison kfree in non-debug kernels'), so getting it into your nightly tests isn't really going to be the end-all of this class of bug.

I believe the future lies in tools like Coverity's checker, as it's the only way we can feasibly get complete coverage.

Double kfree() errors

Posted Mar 10, 2006 16:39 UTC (Fri) by mbligh (subscriber, #7720) [Link]

Ugh. yes, that's going to be much harder. Ah well, should give us something at least. Once we have the open harness, hopefully we can get a broader range of hardware in nightly test, but still ... won't cover everything.