On Mon, Mar 16, 2015 at 6:56 AM, Jiri Kosina <[email protected]> wrote: > On Mon, 16 Mar 2015, Borislav Petkov wrote: >> From: Borislav Petkov <[email protected]> >> Date: Mon, 16 Mar 2015 10:57:56 +0100 >> Subject: [PATCH] Revert "x86/mm/ASLR: Propagate base load address >> calculation" >> >> This reverts commit f47233c2d34f243ecdaac179c3408a39ff9216a7. ... > > Agreed. Let's work on a better refresh for 4.1+. The fix attempts were > quite chaotic.
Then what is the plan for 4.1+ ? Are you still going to use kaslr_setup_data? If if is YES, then we should have patch1: https://lkml.org/lkml/2015/3/15/7 patch2: f47233c2d34f243ecdaac179c3408a39ff9216a7 + fix from https://lkml.org/lkml/2015/3/15/8 If you are not going to have setup_data and f47233c2d34f243ecdaac179c3408a39ff9216a7 back, please let me know. I may need to change patch in https://lkml.org/lkml/2015/3/15/7, So it only have ADDON_ZO_SIZE with pgtable only and we can go on with kaslr on 64bit above 4G support. Thanks Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
