On Fri, Feb 19, 2016 at 06:38:19PM +0100, Ard Biesheuvel wrote:
quoted
I noticed that we still have MODULES_VADDR around and used in couple of
places (printing the kernel memory layout during init, debugfs
kernel_page_tables and KASAN). Shouldn't we use module_alloc_base
instead?
For KASAN, I updated the patches so that the modules are always
allocated in the original module region, to prevent issues with the
zero shadow that backs the vmalloc region.
Ah, I forgot about this.
For the other purposes, it is really a matter of taste. The reserved
region still exists, KASLR or not, so if you omit it, you will have a
hole in the memory map. For the page table dumper, i did not add a
special section for the kernel either.
I'm happy to propose a patch that changes that, once we (you) decide
what you want to see.
Leave it as it is for now.
--
Catalin