A kernel developer who can submit kernel fix or module shall be good enough to avoid this pre-school level traps/bombs.
So the only problem is who he is and for whom he is working? Phoronix has an issue tracing back tool?
It is just slightly better than openbsd that it does not take 10 years to be discovered.
GCC also can check array access, but not for C
For front ends that support it, generate additional code to check that indices used to access arrays are within the declared range. This is currently only supported by the Java and Fortran front ends, where this option defaults to true and false respectively.
Well, I'm glad I'm using debian testing, which is so ancient that it is still on 3.2 kernel..
Yeah, I bet all of you are jealous of me now..
http://www.mosa-project.org/ and Microsoft Midori doing a managed microkernel in C#. I'll definitely be interested to see if either of those actually goes anywhere.
1: If you're on Debian Wheezy or Ubuntu 12.04, you're still affected.
The commit introducing this is actually from just before 3.2.
2: The patch was committed by a Red Hat employee, but was written by a Parallels employee.
Now I'm off to build a new kernel for my Squeeze system.Code:sock_diag: Initial skeleton author Pavel Emelyanov <firstname.lastname@example.org> Tue, 6 Dec 2011 07:58:03 +0000 (07:58 +0000) committer David S. Miller <email@example.com> Tue, 6 Dec 2011 18:58:01 +0000 (13:58 -0500) commit d366477a52f1df29fa066ffb18e4e6101ee2ad04 tree 267a65f626108423f73ef6dc0040b3b3171f7b45 tree | snapshot parent f13c95f0e255e6d21762259875295cc212e6bc32 commit | diff