which does have only effect for i386 non-pae kernels, in which case the system accidentally assumes it has NX capabilities. I will update the other bug accordingly.
@Simon, to check whether you are affected the same: if you got a cpu which has no nx mentioned in cat /proc/cpuinfo but claims "NX (Execute Disable) protection: active" in dmesg, this is wrong. You might want to try the quick test kernel I put to http://people.canonical.com/~smb/bug464552. If that helps we can put this bug into "verification done".
@Martin, I bisected my problem down to
commit 8bf095f8b62c5fd fe55a8c95be775e a62be7bc10
Author: Kees Cook <email address hidden>
Date: Sun Oct 18 09:16:44 2009 -0700
UBUNTU: SAUCE: [x86] fix report of cs-limit nx-emulation bugs.launchpad. net/bugs/ 454285
BugLink: http://
which does have only effect for i386 non-pae kernels, in which case the system accidentally assumes it has NX capabilities. I will update the other bug accordingly.
@Simon, to check whether you are affected the same: if you got a cpu which has no nx mentioned in cat /proc/cpuinfo but claims "NX (Execute Disable) protection: active" in dmesg, this is wrong. You might want to try the quick test kernel I put to http:// people. canonical. com/~smb/ bug464552. If that helps we can put this bug into "verification done".