2.0 also has the segment invalid on syscall return path oopses. When
we tried to fix it for .34 the result was horrible and Linus (quite sanely)
didnt like it one bit. 2.1.x however we can do what the FreeBSD people do
for this path - now we have exception handling for copy*user etc we can
catch that path and bounce the result to a syscall clean up and segv
function.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu