diff options
| author | Joerg Roedel | 2019-07-19 20:46:52 +0200 |
|---|---|---|
| committer | Thomas Gleixner | 2019-07-22 10:18:30 +0200 |
| commit | 3f8fd02b1bf1d7ba964485a56f2f4b53ae88c167 (patch) | |
| tree | 756e384ae006cd3db422e2b4281a8b90a69262b5 /mm | |
| parent | x86/mm: Sync also unmappings in vmalloc_sync_all() (diff) | |
| download | kernel-qcow2-linux-3f8fd02b1bf1d7ba964485a56f2f4b53ae88c167.tar.gz kernel-qcow2-linux-3f8fd02b1bf1d7ba964485a56f2f4b53ae88c167.tar.xz kernel-qcow2-linux-3f8fd02b1bf1d7ba964485a56f2f4b53ae88c167.zip | |
mm/vmalloc: Sync unmappings in __purge_vmap_area_lazy()
On x86-32 with PTI enabled, parts of the kernel page-tables are not shared
between processes. This can cause mappings in the vmalloc/ioremap area to
persist in some page-tables after the region is unmapped and released.
When the region is re-used the processes with the old mappings do not fault
in the new mappings but still access the old ones.
This causes undefined behavior, in reality often data corruption, kernel
oopses and panics and even spontaneous reboots.
Fix this problem by activly syncing unmaps in the vmalloc/ioremap area to
all page-tables in the system before the regions can be re-used.
References: https://bugzilla.suse.com/show_bug.cgi?id=1118689
Fixes: 5d72b4fba40ef ('x86, mm: support huge I/O mapping capability I/F')
Signed-off-by: Joerg Roedel <jroedel@suse.de>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Dave Hansen <dave.hansen@linux.intel.com>
Link: https://lkml.kernel.org/r/20190719184652.11391-4-joro@8bytes.org
Diffstat (limited to 'mm')
| -rw-r--r-- | mm/vmalloc.c | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/mm/vmalloc.c b/mm/vmalloc.c index 4fa8d84599b0..e0fc963acc41 100644 --- a/mm/vmalloc.c +++ b/mm/vmalloc.c @@ -1259,6 +1259,12 @@ static bool __purge_vmap_area_lazy(unsigned long start, unsigned long end) return false; /* + * First make sure the mappings are removed from all page-tables + * before they are freed. + */ + vmalloc_sync_all(); + + /* * TODO: to calculate a flush range without looping. * The list can be up to lazy_max_pages() elements. */ @@ -3038,6 +3044,9 @@ EXPORT_SYMBOL(remap_vmalloc_range); /* * Implement a stub for vmalloc_sync_all() if the architecture chose not to * have one. + * + * The purpose of this function is to make sure the vmalloc area + * mappings are identical in all page-tables in the system. */ void __weak vmalloc_sync_all(void) { |