summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAndy Lutomirski <luto@amacapital.net>2014-07-25 16:27:01 -0700
committerH. Peter Anvin <hpa@linux.intel.com>2014-07-25 16:32:53 -0700
commitac379835e820de27429b5c4eadf4c1b40320cff4 (patch)
treea3946752e7667cde6bf12b4921b6d095d3a7724a
parentda861e18ecccb5c126b9eb95ff720ce082a46286 (diff)
downloadlinux-stable-ac379835e820de27429b5c4eadf4c1b40320cff4.tar.gz
linux-stable-ac379835e820de27429b5c4eadf4c1b40320cff4.tar.bz2
linux-stable-ac379835e820de27429b5c4eadf4c1b40320cff4.zip
x86/vdso: Set VM_MAYREAD for the vvar vma
The VVAR area can, obviously, be read; that is kind of the point. AFAIK this has no effect whatsoever unless x86 suddenly turns into a nommu architecture. Nonetheless, not setting it is suspicious. Reported-by: Nathan Lynch <Nathan_Lynch@mentor.com> Signed-off-by: Andy Lutomirski <luto@amacapital.net> Link: http://lkml.kernel.org/r/e4c8bf4bc2725bda22c4a4b7d0c82adcd8f8d9b8.1406330779.git.luto@amacapital.net Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
-rw-r--r--arch/x86/vdso/vma.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/x86/vdso/vma.c b/arch/x86/vdso/vma.c
index dbef622bb5af..970463b566cf 100644
--- a/arch/x86/vdso/vma.c
+++ b/arch/x86/vdso/vma.c
@@ -138,7 +138,7 @@ static int map_vdso(const struct vdso_image *image, bool calculate_addr)
vma = _install_special_mapping(mm,
addr,
-image->sym_vvar_start,
- VM_READ,
+ VM_READ|VM_MAYREAD,
&vvar_mapping);
if (IS_ERR(vma)) {