It's not strange at all. 2.1 kernels since 2.1.43 use different methods for
kernel memory protection and this effectively works around the bug.
-- Meelis Roos (mroos@tartu.cyber.ee)- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu