x86/vdso: Track each mm's loaded vDSO image as well as its base
authorAndy Lutomirski <luto@kernel.org>
Wed, 30 Dec 2015 04:12:21 +0000 (20:12 -0800)
committerIngo Molnar <mingo@kernel.org>
Tue, 12 Jan 2016 10:59:34 +0000 (11:59 +0100)
commit352b78c62f27b356b182008acd3117f3ee03ffd2
treec7049a57f0db45444e58a0e8026f65f2b0d5e726
parent1745cbc5d0dee0749a6bc0ea8e872c5db0074061
x86/vdso: Track each mm's loaded vDSO image as well as its base

As we start to do more intelligent things with the vDSO at
runtime (as opposed to just at mm initialization time), we'll
need to know which vDSO is in use.

In principle, we could guess based on the mm type, but that's
over-complicated and error-prone.  Instead, just track it in the
mmu context.

Signed-off-by: Andy Lutomirski <luto@kernel.org>
Reviewed-by: Kees Cook <keescook@chromium.org>
Cc: Andy Lutomirski <luto@amacapital.net>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Dave Hansen <dave.hansen@linux.intel.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>
Cc: H. Peter Anvin <hpa@zytor.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Oleg Nesterov <oleg@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Quentin Casasnovas <quentin.casasnovas@oracle.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Link: http://lkml.kernel.org/r/c99ac48681bad709ca7ad5ee899d9042a3af6b00.1451446564.git.luto@kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
arch/x86/entry/vdso/vma.c
arch/x86/include/asm/mmu.h