Manuel Bouyer wrote in <20181203183537.ga1...@antioche.eu.org>: |On Mon, Dec 03, 2018 at 12:54:26PM +0100, Maxime Villard wrote: |> In other words, 80% of KASLR is enabled by default, regardless of #ifdef |> KASLR. Therefore, it is wrong to add an ifdef, because in either case we | |So there's no way to completely disable KASLR now ? |Although I admit it's usefull to have it on by default, there should \ |be a way |to turn it off for low-level debugging
As an idiot from user space only: why is layout randomization still something desirable now that kernel and user address space is totally, cleanly and completely separated, and caches etc. are flushed upon context-switches and system calls? It is like that, right? Also, i was always curious whether there were any runtime costs implied due to the massive splitting of object files, i wondered whether that negatively affects the cache "hotness" in any way. As a programmer i always tried to keep things as compact as possible. --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)
