Some suggestions.

[Lars Gaarden <larsg@trustix.com>]

I expect that we'll need some kind of revision tracking, to make sure
that
all relevant problems found in 2.x are back/forward-ported to 2.y<x and
2.y>x.

Someone mentioned splitting the kernel into subsystems and auditing them
in turn. While this would catch stuff like potential buffer overflows
and
incomplete/lacking parameter validations, it won't catch design bugs and
thinkos in the interaction of the subsystems.

-- 
LarsG. These are my opinions, which may or may not be shared by my
employer.

Code that cracks a protection device is criminal under the DMCA even if
the
use of the copyrighted material that the code enables would be fair use.
- Lawrence Lessig, Berkman Professor of Law, Harward Law School.

Kernel-audit:  discussion list for security and the linux kernel
Archive:       http://mail.nl.linux.org/kernel-audit/