Wtf... Kees Cook <keesc...@chromium.org> wrote:
>On Thu, Dec 20, 2012 at 7:00 PM, Kees Cook <keesc...@chromium.org> >wrote: >> While trying to fix test_nx, I discovered that it looks like stack >and >> heap are executable again (at least on x86_64). :( I tried to bisect > >Btw, this ends up looking like this on v3.4: > >[ 2.486223] test_nx: Testing NX protection ... >[ 2.487468] test_nx: calling ffff88001dd57e45 (0xC3) >[ 2.488766] test_nx: stack is executable >[ 2.489802] test_nx: calling ffff88001e2c7580 (0xC3) >[ 2.491106] test_nx: heap is executable >[ 2.492086] test_nx: calling ffffffff81803c80 (0xC3) >[ 2.493201] test_nx: calling ffffffffa0002220 (0xC3) >[ 2.493843] test_nx: calling ffffffffa0001224 (0xC3) >[ 2.494549] test_nx: Done testing. > >-Kees > >-- >Kees Cook >Chrome OS Security -- Sent from my mobile phone. Please excuse brevity and lack of formatting. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
