+1 to coverity we use that :) On Tue, Aug 18, 2015 at 9:01 AM, leo kirotawa <kirotawa@gmail.com> wrote:
For memory leaks kernel has a clever mechanism to verify it that you can enable in .config for use [1]. You can also uses Sparse in kernel for static analyze purpose.
There are others out there such as coverity scan, coccinelle, etc.
[1] https://www.kernel.org/doc/Documentation/kmemleak.txt
[]'s
On Tue, Aug 18, 2015 at 10:45 AM, Kenneth Adam Miller <kennethadammiller@gmail.com> wrote:
Why? That's what the vast majority of the kernel is written in (besides assembler, but what I'm looking for isn't a way to write safe assembler). Plus, tons of people in the kernel development community *must* have some concern or interest in security. I don't care if the kernel is written in C, but I sure would like my kernel module to be safer. If I can get it I don't care what language it's in-it just has to work and *be secure*.
On Tue, Aug 18, 2015 at 9:40 AM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
On Tue, 18 Aug 2015, Kenneth Adam Miller wrote:
Ok- so I know that C is the defacto standard for kernel development...
and that's probably where you should have stopped typing. :-)
rday
--
======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca
Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
--
---------------------------------------------- Leônidas S. Barbosa (Kirotawa) blog: corecode.wordpress.com
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies