Messages in this thread | | | Date | Sat, 10 Dec 2016 13:33:41 +0100 | From | Borislav Petkov <> | Subject | Re: [PATCH v2 2/2] x86/KASLR/64: Determine kernel text mapping size at runtime |
| |
On Sat, Dec 10, 2016 at 08:27:57PM +0800, Baoquan He wrote: > Whether CONFIG_RANDOMIZE_BASE is yes or not, with 'nokaslr' specified, > Kernel text mapping size should be 512M, just the same as no kaslr code > compiled in.
"should be" still doesn't really explain what the problem is. What's wrong with it remaining 1G?
IOW, something like "The problem is X and the issues it causes are Y. That's why we need to do Z."
Now please replace X,Y and Z with the real content.
-- Regards/Gruss, Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) --
| |