On Mon, Mar 10, 2014 at 12:06 PM, Andrew Morton <a...@linux-foundation.org> wrote: > On Fri, 7 Mar 2014 17:00:23 -0800 Kees Cook <keesc...@chromium.org> wrote: >> Handles 0-based per_cpu variables as being absolute so they are >> not relocated under kASLR on x86_64. > > Would it be prudent to revert 0f55159d091cb1e5 ("kallsyms: fix absolute > addresses for kASLR") then sort all this out for 3.15?
My opinion is that if it breaks a real-life case (avr32), it should be reverted. The only people affected by the kallsyms per_cpu relocation reporting bug are those using kASLR on x86, and even then the bug is a corner case on live kernel debugging. I am fine either way. -Kees -- Kees Cook Chrome OS Security -- 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/