2b26583164
by UVM, so there is no physical loss. On amd64 we always remap the kernel text with 2MB pages, and because of the 1MB start address we were forced to map [0MB; 2MB[ inside the first large page. The problem is, the lower half is used by UVM to allocate physical pages, and it is possible that some of these could be used by userland. We could end up with userland-controllable data mapped into the kernel text on a privileged page, which is far from being a good idea from a security pov. I am not fixing i386 yet, because the large page size depends on PAE, and we probably don't want to have a text located at 4MB on low-memory systems. (note: I didn't introduce this issue, it was already there when I came in) |
||
---|---|---|
.. | ||
ALL | ||
files.amd64 | ||
GENERIC | ||
GENERIC_USERMODE | ||
INSTALL | ||
INSTALL_XEN3_DOMU | ||
kern.ldscript | ||
kern.ldscript.Xen | ||
majors.amd64 | ||
Makefile.amd64 | ||
MODULAR | ||
RNDVERBOSE | ||
std.amd64 | ||
std.xen | ||
XEN3_DOM0 | ||
XEN3_DOMU |