diff options
author | Kees Cook <keescook@chromium.org> | 2013-07-16 18:34:41 (GMT) |
---|---|---|
committer | H. Peter Anvin <hpa@linux.intel.com> | 2013-07-16 22:14:48 (GMT) |
commit | 4df05f361937ee86e5a8c9ead8aeb6a19ea9b7d7 (patch) | |
tree | 5ecfbd89245a33b1902b210cf92619587e12209c /arch/x86/mm/numa.c | |
parent | 5ff560fd48d5b3d82fa0c3aff625c9da1a301911 (diff) | |
download | linux-fsl-qoriq-4df05f361937ee86e5a8c9ead8aeb6a19ea9b7d7.tar.xz |
x86: Make sure IDT is page aligned
Since the IDT is referenced from a fixmap, make sure it is page aligned.
Merge with 32-bit one, since it was already aligned to deal with F00F
bug. Since bss is cleared before IDT setup, it can live there. This also
moves the other *_idt_table variables into common locations.
This avoids the risk of the IDT ever being moved in the bss and having
the mapping be offset, resulting in calling incorrect handlers. In the
current upstream kernel this is not a manifested bug, but heavily patched
kernels (such as those using the PaX patch series) did encounter this bug.
The tables other than idt_table technically do not need to be page
aligned, at least not at the current time, but using a common
declaration avoids mistakes. On 64 bits the table is exactly one page
long, anyway.
Signed-off-by: Kees Cook <keescook@chromium.org>
Link: http://lkml.kernel.org/r/20130716183441.GA14232@www.outflux.net
Reported-by: PaX Team <pageexec@gmail.com>
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Diffstat (limited to 'arch/x86/mm/numa.c')
0 files changed, 0 insertions, 0 deletions