x86/mm/pti: close two Meltdown leaks with Global kernel mapping
Subsystems (4)
Dave Hansen
maintainerv2 cover x86/mm/pti: close two Meltdown leaks with Global kernel mapping
The fixes for the problem Hugh reported took a bit more surgery than I would have liked, but they do appear to work. Note that the last two patches are unnecessary cleanups that could be removed from backports.
Changes from v1:
* Modify set_memory_np() to avoid messing with the direct map by limiting its changes to the high kernel image map.
--
This applies to 4.17 and 4.18.
Thanks to Hugh Dickins for initially finding the r/w kernel text issue and coming up with an initial fix. I found the "unused hole" part and came up with different approach for fixing the mess.
--
Background:
Process Context IDentifiers (PCIDs) are a hardware feature that allows TLB entries to survive page table switches (CR3 writes). As an optimization, the PTI code currently allows the kernel image to be Global when running on hardware without PCIDs. This results in fewer TLB misses, especially upon entry.
The downside is that these Global areas are theoretically susceptible to Meltdown. The logic is that there are no secrets in the kernel image, so why pay the cost of TLB misses.
Problem:
The current PTI code leaves the entire area of the kernel binary between '_text' and '_end' as Global (on non-PCID hardware). However, that range contains both read-write kernel data, and two "unused" holes in addition to text. The areas which are not text or read-only might contain secrets once they are freed back into the allocator.
This issue affects systems which are susceptible to Meltdown, do not have PCIDs and which are using the default PTI_AUTO mode (no pti=on/off on the cmdline).
PCIDs became generally available for servers in ~2010 (Westmere) and desktop (client) parts in roughly 2011 (Sandybridge). This is not expected to affect anything newer than that.
Solution:
The solution for the read-write area is to clear the global bit for the area (patch #1).
The "unused" holes need a bit more work since we free them in a bit of an ad-hoc way, but we fix this up in patches 2-5.
Dave Hansen
maintainerPATCH v2 1/7 x86/mm/pti: clear Global bit more aggressively
From: Dave Hansen <[email protected]>
The kernel image starts out with the Global bit set across the entire kernel image. The bit is cleared with set_memory_nonglobal() in the configurations with PCIDs where we do not need the performance benefits of the Global bit.
However, this is fragile. It means that we are stuck opting *out* of the less-secure (Global bit set) configuration, which seems backwards. Let's start more secure (Global bit clear) and then let things opt back in if they want performance, or are truly mapping common data between kernel and userspace.
This fixes a bug. Before this patch, there are areas that are unmapped from the user page tables (like like everything above 0xffffffff82600000 in the example below). These have the hallmark of being a wrong Global area: they are no identical in the 'current_kernel' and 'current_user' page table dumps. They are also read-write, which means they're much more likely to contain secrets.
Before this patch:
current_kernel:---[ High Kernel Mapping ]---
current_kernel-0xffffffff80000000-0xffffffff81000000 16M pmd current_kernel-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_kernel-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte current_kernel-0xffffffff81e11000-0xffffffff82000000 1980K RW GLB NX pte current_kernel-0xffffffff82000000-0xffffffff82600000 6M ro PSE GLB NX pmd current_kernel-0xffffffff82600000-0xffffffff82c00000 6M RW PSE GLB NX pmd current_kernel-0xffffffff82c00000-0xffffffff82e00000 2M RW GLB NX pte current_kernel-0xffffffff82e00000-0xffffffff83200000 4M RW PSE GLB NX pmd
current_kernel-0xffffffff83200000-0xffffffffa0000000 462M pmd
current_user:---[ High Kernel Mapping ]---
current_user-0xffffffff80000000-0xffffffff81000000 16M pmd current_user-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_user-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte current_user-0xffffffff81e11000-0xffffffff82000000 1980K RW GLB NX pte current_user-0xffffffff82000000-0xffffffff82600000 6M ro PSE GLB NX pmd
current_user-0xffffffff82600000-0xffffffffa0000000 474M pmd
After this patch:
current_kernel:---[ High Kernel Mapping ]---
current_kernel-0xffffffff80000000-0xffffffff81000000 16M pmd current_kernel-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_kernel-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte current_kernel-0xffffffff81e11000-0xffffffff82000000 1980K RW NX pte current_kernel-0xffffffff82000000-0xffffffff82600000 6M ro PSE GLB NX pmd current_kernel-0xffffffff82600000-0xffffffff82c00000 6M RW PSE NX pmd current_kernel-0xffffffff82c00000-0xffffffff82e00000 2M RW NX pte current_kernel-0xffffffff82e00000-0xffffffff83200000 4M RW PSE NX pmd
current_kernel-0xffffffff83200000-0xffffffffa0000000 462M pmd
current_user:---[ High Kernel Mapping ]---
current_user-0xffffffff80000000-0xffffffff81000000 16M pmd current_user-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_user-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte
current_user-0xffffffff81e11000-0xffffffff82000000 1980K RW NX pte
current_user-0xffffffff82000000-0xffffffff82600000 6M ro PSE GLB NX pmd
current_user-0xffffffff82600000-0xffffffffa0000000 474M pmd
---
b/arch/x86/mm/pageattr.c | 6 ++++++ b/arch/x86/mm/pti.c | 34 ++++++++++++++++++++++++---------- 2 files changed, 30 insertions(+), 10 deletions(-)
arch/x86/mm/pageattr.c renamed from arch/x86/mm/pageattr.c~pti-non-pcid-clear-more-global-in-kernel-mapping +6 -0
@@ -1784,6 +1784,12 @@ int set_memory_nonglobal(unsigned long a __pgprot(_PAGE_GLOBAL), 0); } +int set_memory_global (unsigned long addr,int numpages) +{ +return change_page_attr_set (&addr, numpages, +__pgprot (_PAGE_GLOBAL),0 ); +} +static int __set_memory_enc_dec (unsigned long addr,int numpages,bool enc) {struct cpa_data cpa;
arch/x86/mm/pti.c renamed from arch/x86/mm/pti.c~pti-non-pcid-clear-more-global-in-kernel-mapping +24 -10
@@ -435,6 +435,13 @@ static inline bool pti_kernel_image_glob }/* +* This is the only user for these and it is not arch-generic +* like the other set_memory.h functions. Just extern them. +*/ +extern int set_memory_nonglobal (unsigned long addr,int numpages); +extern int set_memory_global (unsigned long addr,int numpages); + +/* * For some configurations, map all of kernel text into the user page * tables. This reduces TLB misses, especially on non-PCID systems. */
@@ -446,7 +453,8 @@ void pti_clone_kernel_text(void)* clone the areas past rodata, they might contain secrets. */ unsigned long start =PFN_ALIGN (_text); -unsigned long end = (unsigned long )__end_rodata_hpage_align; +unsigned long end_clone = (unsigned long )__end_rodata_hpage_align; +unsigned long end_global =PFN_ALIGN ((unsigned long )__stop___ex_table);if (!pti_kernel_image_global_ok ())return ;
@@ -458,14 +466,18 @@ void pti_clone_kernel_text(void)* pti_set_kernel_image_nonglobal() did to clear the * global bit. */ -pti_clone_pmds (start, end, _PAGE_RW); +pti_clone_pmds (start, end_clone, _PAGE_RW); + +/* +* pti_clone_pmds() will set the global bit in any PMDs +* that it clones, but we also need to get any PTEs in +* the last level for areas that are not huge-page-aligned. +*/ + +/* Set the global bit for normal non-__init kernel text: */ +set_memory_global (start, (end_global - start) >>PAGE_SHIFT ); } -/* -* This is the only user for it and it is not arch-generic like -* the other set_memory.h functions. Just extern it. -*/ -extern int set_memory_nonglobal (unsigned long addr,int numpages);void pti_set_kernel_image_nonglobal (void ) {/*
@@ -477,9 +489,11 @@ void pti_set_kernel_image_nonglobal(voidunsigned long start =PFN_ALIGN (_text);unsigned long end =ALIGN ((unsigned long )_end,PMD_PAGE_SIZE ); -if (pti_kernel_image_global_ok ()) -return ; - +/* +* This clears _PAGE_GLOBAL from the entire kernel image. +* pti_clone_kernel_text() map put _PAGE_GLOBAL back for +* areas that are mapped to userspace. +*/ set_memory_nonglobal (start, (end - start) >>PAGE_SHIFT ); }
_
tip-bot for Dave Hansen
merge bot[tip:x86/pti] x86/mm/pti: Clear Global bit more aggressively
x86/mm/pti: Clear Global bit more aggressively
Commit-ID: eac7073aa69aa1cac819aa712146284f53f642b1 Gitweb: https://git.kernel.org/tip/eac7073aa69aa1cac819aa712146284f53f642b1 Author: Dave Hansen <[email protected]> AuthorDate: Thu, 2 Aug 2018 15:58:25 -0700 Committer: Thomas Gleixner <[email protected]> CommitDate: Sun, 5 Aug 2018 22:21:02 +0200
x86/mm/pti: Clear Global bit more aggressively
The kernel image starts out with the Global bit set across the entire kernel image. The bit is cleared with set_memory_nonglobal() in the configurations with PCIDs where the performance benefits of the Global bit are not needed.
However, this is fragile. It means that we are stuck opting *out* of the less-secure (Global bit set) configuration, which seems backwards. Let's start more secure (Global bit clear) and then let things opt back in if they want performance, or are truly mapping common data between kernel and userspace.
This fixes a bug. Before this patch, there are areas that are unmapped from the user page tables (like like everything above 0xffffffff82600000 in the example below). These have the hallmark of being a wrong Global area:
they are not identical in the 'current_kernel' and 'current_user' page table dumps. They are also read-write, which means they're much more likely to contain secrets.
Before this patch:
current_kernel:---[ High Kernel Mapping ]---
current_kernel-0xffffffff80000000-0xffffffff81000000 16M pmd current_kernel-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_kernel-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte current_kernel-0xffffffff81e11000-0xffffffff82000000 1980K RW GLB NX pte current_kernel-0xffffffff82000000-0xffffffff82600000 6M ro PSE GLB NX pmd current_kernel-0xffffffff82600000-0xffffffff82c00000 6M RW PSE GLB NX pmd current_kernel-0xffffffff82c00000-0xffffffff82e00000 2M RW GLB NX pte current_kernel-0xffffffff82e00000-0xffffffff83200000 4M RW PSE GLB NX pmd
current_kernel-0xffffffff83200000-0xffffffffa0000000 462M pmd
current_user:---[ High Kernel Mapping ]---
current_user-0xffffffff80000000-0xffffffff81000000 16M pmd current_user-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_user-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte current_user-0xffffffff81e11000-0xffffffff82000000 1980K RW GLB NX pte current_user-0xffffffff82000000-0xffffffff82600000 6M ro PSE GLB NX pmd
current_user-0xffffffff82600000-0xffffffffa0000000 474M pmd
After this patch:
current_kernel:---[ High Kernel Mapping ]---
current_kernel-0xffffffff80000000-0xffffffff81000000 16M pmd current_kernel-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_kernel-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte current_kernel-0xffffffff81e11000-0xffffffff82000000 1980K RW NX pte current_kernel-0xffffffff82000000-0xffffffff82600000 6M ro PSE GLB NX pmd current_kernel-0xffffffff82600000-0xffffffff82c00000 6M RW PSE NX pmd current_kernel-0xffffffff82c00000-0xffffffff82e00000 2M RW NX pte current_kernel-0xffffffff82e00000-0xffffffff83200000 4M RW PSE NX pmd
current_kernel-0xffffffff83200000-0xffffffffa0000000 462M pmd
current_user:---[ High Kernel Mapping ]---
current_user-0xffffffff80000000-0xffffffff81000000 16M pmd current_user-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_user-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte
current_user-0xffffffff81e11000-0xffffffff82000000 1980K RW NX pte
current_user-0xffffffff82000000-0xffffffff82600000 6M ro PSE GLB NX pmd
current_user-0xffffffff82600000-0xffffffffa0000000 474M pmd
--- arch/x86/mm/pageattr.c | 6 ++++++ arch/x86/mm/pti.c | 34 ++++++++++++++++++++++++---------- 2 files changed, 30 insertions(+), 10 deletions(-)
arch/x86/mm/pageattr.c +6 -0
@@ -1784,6 +1784,12 @@ int set_memory_nonglobal(unsigned long addr, int numpages) __pgprot(_PAGE_GLOBAL), 0); } +int set_memory_global (unsigned long addr,int numpages) +{ +return change_page_attr_set (&addr, numpages, +__pgprot (_PAGE_GLOBAL),0 ); +} +static int __set_memory_enc_dec (unsigned long addr,int numpages,bool enc) {struct cpa_data cpa;
arch/x86/mm/pti.c +24 -10
@@ -434,6 +434,13 @@ static inline bool pti_kernel_image_global_ok(void)return true; } +/* +* This is the only user for these and it is not arch-generic +* like the other set_memory.h functions. Just extern them. +*/ +extern int set_memory_nonglobal (unsigned long addr,int numpages); +extern int set_memory_global (unsigned long addr,int numpages); +/* * For some configurations, map all of kernel text into the user page * tables. This reduces TLB misses, especially on non-PCID systems.
@@ -446,7 +453,8 @@ void pti_clone_kernel_text(void)* clone the areas past rodata, they might contain secrets. */ unsigned long start =PFN_ALIGN (_text); -unsigned long end = (unsigned long )__end_rodata_hpage_align; +unsigned long end_clone = (unsigned long )__end_rodata_hpage_align; +unsigned long end_global =PFN_ALIGN ((unsigned long )__stop___ex_table);if (!pti_kernel_image_global_ok ())return ;
@@ -458,14 +466,18 @@ void pti_clone_kernel_text(void)* pti_set_kernel_image_nonglobal() did to clear the * global bit. */ -pti_clone_pmds (start, end, _PAGE_RW); +pti_clone_pmds (start, end_clone, _PAGE_RW); + +/* +* pti_clone_pmds() will set the global bit in any PMDs +* that it clones, but we also need to get any PTEs in +* the last level for areas that are not huge-page-aligned. +*/ + +/* Set the global bit for normal non-__init kernel text: */ +set_memory_global (start, (end_global - start) >>PAGE_SHIFT ); } -/* -* This is the only user for it and it is not arch-generic like -* the other set_memory.h functions. Just extern it. -*/ -extern int set_memory_nonglobal (unsigned long addr,int numpages);void pti_set_kernel_image_nonglobal (void ) {/*
@@ -477,9 +489,11 @@ void pti_set_kernel_image_nonglobal(void)unsigned long start =PFN_ALIGN (_text);unsigned long end =ALIGN ((unsigned long )_end,PMD_PAGE_SIZE ); -if (pti_kernel_image_global_ok ()) -return ; - +/* +* This clears _PAGE_GLOBAL from the entire kernel image. +* pti_clone_kernel_text() map put _PAGE_GLOBAL back for +* areas that are mapped to userspace. +*/ set_memory_nonglobal (start, (end - start) >>PAGE_SHIFT ); }
Dave Hansen
maintainerPATCH v2 2/7 mm: allow non-direct-map arguments to free_reserved_area()
In reply to Dave HansenFrom: Dave Hansen <[email protected]>
free_reserved_area() takes pointers as arguments to show which addresses should be freed. However, it does this in a somewhat ambiguous way. If it gets a kernel direct map address, it always works. However, if it gets an address that is part of the kernel image alias mapping, it can fail.
It fails if all of the following happen:
* The specified address is part of the kernel image alias
* Poisoning is requested (forcing a memset())
* The address is in a read-only portion of the kernel image
The memset() fails on the read-only mapping, of course. free_reserved_area() *is* called both on the direct map and on kernel image alias addresses. We've just lucked out thus far that the kernel image alias areas it gets used on are read-write. I'm fairly sure this has been just a happy accident.
It is quite easy to make free_reserved_area() work for all
cases: just convert the address to a direct map address before doing the memset(), and do this unconditionally. There is little chance of a regression here because we previously did a virt_to_page() on the address for the memset, so we know these are no highmem pages for which virt_to_page() would fail.
---
b/mm/page_alloc.c | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-)
mm/page_alloc.c renamed from mm/page_alloc.c~x86-mm-init-handle-non-linear-map-ranges-free_init_pages +14 -2
@@ -6939,9 +6939,21 @@ unsigned long free_reserved_area(void *s start = (void *)PAGE_ALIGN ((unsigned long )start); end = (void *)((unsigned long )end &PAGE_MASK );for (pos = start; pos < end; pos +=PAGE_SIZE , pages++) { +struct page *page =virt_to_page (pos); +void *direct_map_addr; + +/* +* 'direct_map_addr' might be different from 'pos' +* because some architectures' virt_to_page() +* work with aliases. Getting the direct map +* address ensures that we get a _writeable_ +* alias for the memset(). +*/ + direct_map_addr =page_address (page);if ((unsigned int )poison <=0xFF ) -memset (pos, poison,PAGE_SIZE ); -free_reserved_page (virt_to_page (pos)); +memset (direct_map_addr, poison,PAGE_SIZE ); + +free_reserved_page (page); }if (pages && s)
_
tip-bot for Dave Hansen
merge bot[tip:x86/pti] mm: Allow non-direct-map arguments to free_reserved_area()
mm: Allow non-direct-map arguments to free_reserved_area()
Commit-ID: 0d83432811f26871295a9bc24d3c387924da6071 Gitweb: https://git.kernel.org/tip/0d83432811f26871295a9bc24d3c387924da6071 Author: Dave Hansen <[email protected]> AuthorDate: Thu, 2 Aug 2018 15:58:26 -0700 Committer: Thomas Gleixner <[email protected]> CommitDate: Sun, 5 Aug 2018 22:21:02 +0200
mm: Allow non-direct-map arguments to free_reserved_area()
free_reserved_area() takes pointers as arguments to show which addresses should be freed. However, it does this in a somewhat ambiguous way. If it gets a kernel direct map address, it always works. However, if it gets an address that is part of the kernel image alias mapping, it can fail.
It fails if all of the following happen:
* The specified address is part of the kernel image alias
* Poisoning is requested (forcing a memset())
* The address is in a read-only portion of the kernel image
The memset() fails on the read-only mapping, of course. free_reserved_area() *is* called both on the direct map and on kernel image alias addresses. We've just lucked out thus far that the kernel image alias areas it gets used on are read-write. I'm fairly sure this has been just a happy accident.
It is quite easy to make free_reserved_area() work for all cases: just convert the address to a direct map address before doing the memset(), and do this unconditionally. There is little chance of a regression here because we previously did a virt_to_page() on the address for the memset, so we know these are not highmem pages for which virt_to_page() would fail.
--- mm/page_alloc.c | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-)
mm/page_alloc.c +14 -2
@@ -6939,9 +6939,21 @@ unsigned long free_reserved_area(void *start, void *end, int poison, char *s) start = (void *)PAGE_ALIGN ((unsigned long )start); end = (void *)((unsigned long )end &PAGE_MASK );for (pos = start; pos < end; pos +=PAGE_SIZE , pages++) { +struct page *page =virt_to_page (pos); +void *direct_map_addr; + +/* +* 'direct_map_addr' might be different from 'pos' +* because some architectures' virt_to_page() +* work with aliases. Getting the direct map +* address ensures that we get a _writeable_ +* alias for the memset(). +*/ + direct_map_addr =page_address (page);if ((unsigned int )poison <=0xFF ) -memset (pos, poison,PAGE_SIZE ); -free_reserved_page (virt_to_page (pos)); +memset (direct_map_addr, poison,PAGE_SIZE ); + +free_reserved_page (page); }if (pages && s)
Dave Hansen
maintainerPATCH v2 3/7 x86/mm/init: pass unconverted symbol addresses to free_init_pages()
In reply to Dave HansenFrom: Dave Hansen <[email protected]>
The x86 code has several places where it frees parts of kernel image:
1. Unused SMP alternative
2. __init code
3. The hole between text and rodata
4. The hole between rodata and data
We call free_init_pages() to do this. Strangely, we convert the symbol addresses to kernel direct map addresses in some cases (#3, #4) but not others (#1, #2).
The virt_to_page() and the other code in free_reserved_area() now works fine for for symbol addresses on x86, so don't bother converting the addresses to direct map addresses before freeing them.
---
b/arch/x86/mm/init_64.c | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-)
arch/x86/mm/init_64.c renamed from arch/x86/mm/init_64.c~x86-init-do-not-convert-symbol-addresses +2 -6
@@ -1283,12 +1283,8 @@ void mark_rodata_ro(void)set_memory_ro (start, (end-start) >>PAGE_SHIFT );#endif -free_init_pages ("unused kernel" , - (unsigned long )__va (__pa_symbol (text_end)), - (unsigned long )__va (__pa_symbol (rodata_start))); -free_init_pages ("unused kernel" , - (unsigned long )__va (__pa_symbol (rodata_end)), - (unsigned long )__va (__pa_symbol (_sdata))); +free_init_pages ("unused kernel" , text_end, rodata_start); +free_init_pages ("unused kernel" , rodata_end, _sdata);debug_checkwx ();
_
Re: [PATCH 3/7] x86/mm/init: pass unconverted symbol addresses to free_init_pages()
Quoted 10 lines · Dave Hansen
From: Dave Hansen <[email protected]>
The x86 code has several places where it frees parts of kernel image:
1. Unused SMP alternative
2.__initcode
3. The hole between text and rodata
4. The hole between rodata and data
Quoted 9 lines
We call
free_init_pages()to do this. Strangely, we convert the symbol addresses to kernel direct map addresses in some cases (#3, #4) but not others (#1, #2).The
virt_to_page()and the other code infree_reserved_area()now works fine for for symbol addresses on x86, so don't bother converting the addresses to direct map addresses before freeing them.
Thanks Dave, this series works for me.
But in trying to review it, I am feeling very stupid about this 3/7 (and/or the 2/7 before it: though I don't think that it's wrong).
I simply do not understand how this change works, and how #1 and #2 work. I thought that virt_to_page() only works on virtual addresses in the direct map: the __va(__pa_symbol()) you remove below was a good conversion from high kernel mapping to direct map. Without it, how does virt_to_page() then find the right page?
Is it that there's a guaranteed common alignment between the direct map and the high kernel mapping, and the ffffffff8....... addresses pass through the arithmetic in such a way that virt_to_page() comes up with the right answer; and that is well-known and relied upon by x86 developers? Or are you now adding a dependency on a coincidence? Or does it not work at all, and the pages are actually not freed?
Hugh
p.s. if there were to be a respin (I hope not), I notice that in both 1/7 and 2/7 commit comments, you've said " no " for " not "; which always makes us pause and wonder if you meant " now ".
Quoted 38 lines
Signed-off-by Dave Hansen <[email protected]>Cc Kees Cook <[email protected]>Cc Thomas Gleixner <[email protected]>Cc Ingo Molnar <[email protected]>Cc Andrea Arcangeli <[email protected]>Cc Juergen Gross <[email protected]>Cc Josh Poimboeuf <[email protected]>Cc Greg Kroah-Hartman <[email protected]>Cc Peter Zijlstra <[email protected]>Cc Hugh Dickins <[email protected]>Cc Linus Torvalds <[email protected]>Cc Borislav Petkov <[email protected]>Cc Andy Lutomirski <[email protected]>Cc Andi Kleen <[email protected]>---
b/arch/x86/mm/init_64.c | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-)diff -puN
arch/x86/mm/init_64.c~x86-init-do-not-convert-symbol-addressesarch/x86/mm/init_64.carch/x86/mm/init_64.c renamed from arch/x86/mm/init_64.c~x86-init-do-not-convert-symbol-addresses +2
-6@@ -1283,12 +1283,8 @@ void mark_rodata_ro(void)set_memory_ro (start, (end-start) >>PAGE_SHIFT );#endif -free_init_pages ("unused kernel" , - (unsigned long )__va (__pa_symbol (text_end)), - (unsigned long )__va (__pa_symbol (rodata_start))); -free_init_pages ("unused kernel" , - (unsigned long )__va (__pa_symbol (rodata_end)), - (unsigned long )__va (__pa_symbol (_sdata))); +free_init_pages ("unused kernel" , text_end, rodata_start); +free_init_pages ("unused kernel" , rodata_end, _sdata);debug_checkwx ();_
Re: [PATCH 3/7] x86/mm/init: pass unconverted symbol addresses to free_init_pages()
Quoted 3 lines · Hugh Dickins
I thought that
virt_to_page()only works on virtual addresses in the direct map
You're right that virt_to_page() does not work on any _actual_ virtual mappings (ie no user pages, and no vmalloc() pages etc). It does not follow page tables at all.
And on 32-bit, it literally ends up doing (see __phys_addr_nodebug()) a simple
#define __phys_addr_nodebug(x) ((x) - PAGE_OFFSET)
However, on x86-64, we have *two* cases of direct mappings: we have the one at __START_KERNEL_map, and we have the one at PAGE_OFFSET.
And virt_to_page() handles both of those direct mappings.
Annoying? Yes. And it has caused bugs in the past. And I entirely forget why we needed it on x86-64.
[ Goes around and rummages ]
Oh, never mind, looking around reminded me why: we want to map the kernel text in the top 31 bits, so that we can use the faster -mcmodel=kernel because all symbols fit in sign-extended 32 bits.
Maybe there was some other reason too, but I think that's it.
Linus
Re: [PATCH 3/7] x86/mm/init: pass unconverted symbol addresses to free_init_pages()
Quoted 21 lines · Linus Torvalds
Quoted 3 lines · Hugh Dickins
I thought that
virt_to_page()only works on virtual addresses in the direct mapYou're right that
virt_to_page()does not work on any _actual_ virtual mappings (ie no user pages, and novmalloc()pages etc). It does not follow page tables at all.And on 32-bit, it literally ends up doing (see
__phys_addr_nodebug()) a simple#define __phys_addr_nodebug(x) ((x) - PAGE_OFFSET)However, on x86-64, we have *two* cases of direct mappings: we have the one at
__START_KERNEL_map, and we have the one atPAGE_OFFSET.And
virt_to_page()handles both of those direct mappings.Annoying? Yes. And it has caused bugs in the past. And I entirely forget why we needed it on x86-64.
Quoted 7 lines
[ Goes around and rummages ]
Oh, never mind, looking around reminded me why: we want to map the kernel text in the top 31 bits, so that we can use the faster -mcmodel=kernel because all symbols fit in sign-extended 32 bits.
Maybe there was some other reason too, but I think that's it.
Thanks a lot for writing that up. You shamed me into grepping a little harder than I did yesterday, when all I could find were "- PAGE_OFFSET" conversions (maybe I got lost in 32-bit-land). I had missed __phys_addr_nodebug(), where the __START_KERNEL_map alternative is handled.
Hugh
Re: [PATCH 3/7] x86/mm/init: pass unconverted symbol addresses to free_init_pages()
In reply to Linus TorvaldsQuoted 7 lines
[ Goes around and rummages ]
Oh, never mind, looking around reminded me why: we want to map the kernel text in the top 31 bits, so that we can use the faster -mcmodel=kernel because all symbols fit in sign-extended 32 bits.
Maybe there was some other reason too, but I think that's it.
No that was the only reason.
Large code model would be extremely expensive, and PIC linked kernel also had some issues. So we ended up with this set up.
-Andi
tip-bot for Dave Hansen
merge bot[tip:x86/pti] x86/mm/init: Pass unconverted symbol addresses to free_init_pages()
In reply to Dave Hansenx86/mm/init: Pass unconverted symbol addresses to free_init_pages()
Commit-ID: 9f515cdb411ef34f1aaf4c40bb0c932cf6db5de1 Gitweb: https://git.kernel.org/tip/9f515cdb411ef34f1aaf4c40bb0c932cf6db5de1 Author: Dave Hansen <[email protected]> AuthorDate: Thu, 2 Aug 2018 15:58:28 -0700 Committer: Thomas Gleixner <[email protected]> CommitDate: Sun, 5 Aug 2018 22:21:02 +0200
x86/mm/init: Pass unconverted symbol addresses to free_init_pages()
The x86 code has several places where it frees parts of kernel image:
1. Unused SMP alternative
2. __init code
3. The hole between text and rodata
4. The hole between rodata and data
We call free_init_pages() to do this. Strangely, we convert the symbol addresses to kernel direct map addresses in some cases (#3, #4) but not others (#1, #2).
The virt_to_page() and the other code in free_reserved_area() now works fine for for symbol addresses on x86, so don't bother converting the addresses to direct map addresses before freeing them.
--- arch/x86/mm/init_64.c | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-)
arch/x86/mm/init_64.c +2 -6
@@ -1283,12 +1283,8 @@ void mark_rodata_ro(void)set_memory_ro (start, (end-start) >>PAGE_SHIFT );#endif -free_init_pages ("unused kernel" , - (unsigned long )__va (__pa_symbol (text_end)), - (unsigned long )__va (__pa_symbol (rodata_start))); -free_init_pages ("unused kernel" , - (unsigned long )__va (__pa_symbol (rodata_end)), - (unsigned long )__va (__pa_symbol (_sdata))); +free_init_pages ("unused kernel" , text_end, rodata_start); +free_init_pages ("unused kernel" , rodata_end, _sdata);debug_checkwx ();
Dave Hansen
maintainerPATCH v2 4/7 x86/mm/init: add helper for freeing kernel image pages
In reply to Dave HansenFrom: Dave Hansen <[email protected]>
When chunks of the kernel image are freed, free_init_pages() is used directly. Consolidate the three sites that do this. Also update the string to give an incrementally better description of that memory versus what was there before.
---
b/arch/x86/include/asm/processor.h | 1 + b/arch/x86/mm/init.c | 15 ++++++++++++--- b/arch/x86/mm/init_64.c | 4 ++-- 3 files changed, 15 insertions(+), 5 deletions(-)
arch/x86/include/asm/processor.h renamed from arch/x86/include/asm/processor.h~x86-mm-init-common-kernel-image-free-helper +1 -0
@@ -966,6 +966,7 @@ static inline uint32_t hypervisor_cpuid_extern unsigned long arch_align_stack (unsigned long sp);extern void free_init_pages (char *what,unsigned long begin,unsigned long end); +extern void free_kernel_image_pages (void *begin,void *end);void default_idle (void );#ifdef CONFIG_XEN
arch/x86/mm/init_64.c renamed from arch/x86/mm/init_64.c~x86-mm-init-common-kernel-image-free-helper +2 -2
@@ -1283,8 +1283,8 @@ void mark_rodata_ro(void)set_memory_ro (start, (end-start) >>PAGE_SHIFT );#endif -free_init_pages ("unused kernel" , text_end, rodata_start); -free_init_pages ("unused kernel" , rodata_end, _sdata); +free_kernel_image_pages ((void *)text_end, (void *)rodata_start); +free_kernel_image_pages ((void *)rodata_end, (void *)_sdata);debug_checkwx ();
arch/x86/mm/init.c renamed from arch/x86/mm/init.c~x86-mm-init-common-kernel-image-free-helper +12 -3
@@ -773,13 +773,22 @@ void free_init_pages(char *what, unsigne } } +/* +* begin/end can be in the direct map or the "high kernel mapping" +* used for the kernel image only. free_init_pages() will do the +* right thing for either kind of address. +*/ +void free_kernel_image_pages (void *begin,void *end) +{ +free_init_pages ("unused kernel image" , + (unsigned long )begin, (unsigned long )end); +} +void __ref free_initmem (void ) {e820__reallocate_tables (); -free_init_pages ("unused kernel" , - (unsigned long )(&__init_begin), - (unsigned long )(&__init_end)); +free_kernel_image_pages (&__init_begin, &__init_end); }#ifdef CONFIG_BLK_DEV_INITRD
_
tip-bot for Dave Hansen
merge bot[tip:x86/pti] x86/mm/init: Add helper for freeing kernel image pages
x86/mm/init: Add helper for freeing kernel image pages
Commit-ID: 6ea2738e0ca0e626c75202fb051c1e88d7a950fa Gitweb: https://git.kernel.org/tip/6ea2738e0ca0e626c75202fb051c1e88d7a950fa Author: Dave Hansen <[email protected]> AuthorDate: Thu, 2 Aug 2018 15:58:29 -0700 Committer: Thomas Gleixner <[email protected]> CommitDate: Sun, 5 Aug 2018 22:21:03 +0200
x86/mm/init: Add helper for freeing kernel image pages
When chunks of the kernel image are freed, free_init_pages() is used directly. Consolidate the three sites that do this. Also update the string to give an incrementally better description of that memory versus what was there before.
--- arch/x86/include/asm/processor.h | 1 + arch/x86/mm/init.c | 15 ++++++++++++--- arch/x86/mm/init_64.c | 4 ++-- 3 files changed, 15 insertions(+), 5 deletions(-)
arch/x86/include/asm/processor.h +1 -0
@@ -966,6 +966,7 @@ static inline uint32_t hypervisor_cpuid_base(const char *sig, uint32_t leaves)extern unsigned long arch_align_stack (unsigned long sp);extern void free_init_pages (char *what,unsigned long begin,unsigned long end); +extern void free_kernel_image_pages (void *begin,void *end);void default_idle (void );#ifdef CONFIG_XEN
arch/x86/mm/init.c +12 -3
@@ -773,13 +773,22 @@ void free_init_pages(char *what, unsigned long begin, unsigned long end) } } +/* +* begin/end can be in the direct map or the "high kernel mapping" +* used for the kernel image only. free_init_pages() will do the +* right thing for either kind of address. +*/ +void free_kernel_image_pages (void *begin,void *end) +{ +free_init_pages ("unused kernel image" , + (unsigned long )begin, (unsigned long )end); +} +void __ref free_initmem (void ) {e820__reallocate_tables (); -free_init_pages ("unused kernel" , - (unsigned long )(&__init_begin), - (unsigned long )(&__init_end)); +free_kernel_image_pages (&__init_begin, &__init_end); }#ifdef CONFIG_BLK_DEV_INITRD
arch/x86/mm/init_64.c +2 -2
@@ -1283,8 +1283,8 @@ void mark_rodata_ro(void)set_memory_ro (start, (end-start) >>PAGE_SHIFT );#endif -free_init_pages ("unused kernel" , text_end, rodata_start); -free_init_pages ("unused kernel" , rodata_end, _sdata); +free_kernel_image_pages ((void *)text_end, (void *)rodata_start); +free_kernel_image_pages ((void *)rodata_end, (void *)_sdata);debug_checkwx ();
Dave Hansen
maintainerPATCH v2 5/7 x86/mm/init: remove freed kernel image areas from alias mapping
In reply to Dave HansenFrom: Dave Hansen <[email protected]>
The kernel image is mapped into two places in the virtual address space (addresses without KASLR, of course):
1. The kernel direct map (0xffff880000000000)
2. The "high kernel map" (0xffffffff81000000)
We actually execute out of #2. If we get the address of a kernel symbol, it points to #2, but almost all physical-to-virtual translations point to #1.
Parts of the "high kernel map" alias are mapped in the userspace page tables with the Global bit for performance reasons. The parts that we map to userspace do not (er, should not) have secrets.
This is fine, except that some areas in the kernel image that are adjacent to the non-secret-containing areas are unused holes. We free these holes back into the normal page allocator and reuse them as normal kernel memory. The memory will, of course, get *used* via the normal map, but the alias mapping is kept.
This otherwise unused alias mapping of the holes will, by default keep the Global bit, be mapped out to userspace, and be vulnerable to Meltdown.
Remove the alias mapping of these pages entirely. This is likely to fracture the 2M page mapping the kernel image near these areas, but this should affect a minority of the area.
The pageattr code changes *all* aliases mapping the physical pages that it operates on (by default). We only want to modify a single alias, so we need to tweak its behavior.
This unmapping behavior is currently dependent on PTI being in place. Going forward, we should at least consider doing this for all configurations. Having an extra read-write alias for memory is not exactly ideal for debugging things like random memory corruption and this does undercut features like DEBUG_PAGEALLOC or future work like eXclusive Page Frame Ownership (XPFO).
Before this patch:
current_kernel:---[ High Kernel Mapping ]---
current_kernel-0xffffffff80000000-0xffffffff81000000 16M pmd current_kernel-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_kernel-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte current_kernel-0xffffffff81e11000-0xffffffff82000000 1980K RW NX pte current_kernel-0xffffffff82000000-0xffffffff82600000 6M ro PSE GLB NX pmd current_kernel-0xffffffff82600000-0xffffffff82c00000 6M RW PSE NX pmd current_kernel-0xffffffff82c00000-0xffffffff82e00000 2M RW NX pte current_kernel-0xffffffff82e00000-0xffffffff83200000 4M RW PSE NX pmd
current_kernel-0xffffffff83200000-0xffffffffa0000000 462M pmd
current_user:---[ High Kernel Mapping ]---
current_user-0xffffffff80000000-0xffffffff81000000 16M pmd current_user-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_user-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte
current_user-0xffffffff81e11000-0xffffffff82000000 1980K RW NX pte
current_user-0xffffffff82000000-0xffffffff82600000 6M ro PSE GLB NX pmd
current_user-0xffffffff82600000-0xffffffffa0000000 474M pmd
After this patch:
current_kernel:---[ High Kernel Mapping ]---
current_kernel-0xffffffff80000000-0xffffffff81000000 16M pmd current_kernel-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_kernel-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte current_kernel-0xffffffff81e11000-0xffffffff82000000 1980K pte current_kernel-0xffffffff82000000-0xffffffff82400000 4M ro PSE GLB NX pmd current_kernel-0xffffffff82400000-0xffffffff82488000 544K ro NX pte current_kernel-0xffffffff82488000-0xffffffff82600000 1504K pte current_kernel-0xffffffff82600000-0xffffffff82c00000 6M RW PSE NX pmd current_kernel-0xffffffff82c00000-0xffffffff82c0d000 52K RW NX pte
current_kernel-0xffffffff82c0d000-0xffffffff82dc0000 1740K pte
current_user:---[ High Kernel Mapping ]---
current_user-0xffffffff80000000-0xffffffff81000000 16M pmd current_user-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_user-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte current_user-0xffffffff81e11000-0xffffffff82000000 1980K pte
current_user-0xffffffff82000000-0xffffffff82400000 4M ro PSE GLB NX pmd
current_user-0xffffffff82400000-0xffffffff82488000 544K ro NX pte
current_user-0xffffffff82488000-0xffffffff82600000 1504K pte
current_user-0xffffffff82600000-0xffffffffa0000000 474M pmd
---
b/arch/x86/include/asm/set_memory.h | 1 + b/arch/x86/mm/init.c | 25 +++++++++++++++++++++++-- b/arch/x86/mm/pageattr.c | 13 +++++++++++++ 3 files changed, 37 insertions(+), 2 deletions(-)
arch/x86/include/asm/set_memory.h renamed from arch/x86/include/asm/set_memory.h~x86-unmap-freed-areas-from-kernel-image +1 -0
@@ -46,6 +46,7 @@ int set_memory_np(unsigned long addr, inint set_memory_4k (unsigned long addr,int numpages);int set_memory_encrypted (unsigned long addr,int numpages);int set_memory_decrypted (unsigned long addr,int numpages); +int set_memory_np_noalias (unsigned long addr,int numpages);int set_memory_array_uc (unsigned long *addr,int addrinarray);int set_memory_array_wc (unsigned long *addr,int addrinarray);
arch/x86/mm/init.c renamed from arch/x86/mm/init.c~x86-unmap-freed-areas-from-kernel-image +23 -2
@@ -780,8 +780,29 @@ void free_init_pages(char *what, unsigne*/ void free_kernel_image_pages (void *begin,void *end) { -free_init_pages ("unused kernel image" , - (unsigned long )begin, (unsigned long )end); +unsigned long begin_ul = (unsigned long )begin; +unsigned long end_ul = (unsigned long )end; +unsigned long len_pages = (end_ul - begin_ul) >>PAGE_SHIFT ; + + +free_init_pages ("unused kernel image" , begin_ul, end_ul); + +/* +* PTI maps some of the kernel into userspace. For +* performance, this includes some kernel areas that +* do not contain secrets. Those areas might be +* adjacent to the parts of the kernel image being +* freed, which may contain secrets. Remove the +* "high kernel image mapping" for these freed areas, +* ensuring they are not even potentially vulnerable +* to Meltdown regardless of the specific optimizations +* PTI is currently using. +* +* The "noalias" prevents unmapping the direct map +* alias which is needed to access the freed pages. +*/ +if (cpu_feature_enabled (X86_FEATURE_PTI )) +set_memory_np_noalias (begin_ul, len_pages); }void __ref free_initmem (void )
arch/x86/mm/pageattr.c renamed from arch/x86/mm/pageattr.c~x86-unmap-freed-areas-from-kernel-image +13 -0
@@ -53,6 +53,7 @@ static DEFINE_SPINLOCK(cpa_lock);#define CPA_FLUSHTLB 1#define CPA_ARRAY 2#define CPA_PAGES_ARRAY 4 +#define CPA_NO_CHECK_ALIAS 8/* Do not search for aliases */ #ifdef CONFIG_PROC_FS static unsigned long direct_pages_count[PG_LEVEL_NUM ];
@@ -1486,6 +1487,9 @@ static int change_page_attr_set_clr(unsi/* No alias checking for _NX bit modifications */ checkalias = (pgprot_val (mask_set) |pgprot_val (mask_clr)) != _PAGE_NX; +/* Never check aliases if the caller asks for it explicitly: */ +if (checkalias && (in_flag &CPA_NO_CHECK_ALIAS )) + checkalias =0 ; ret =__change_page_attr_set_clr (&cpa, checkalias);
@@ -1772,6 +1776,15 @@ int set_memory_np(unsigned long addr, inreturn change_page_attr_clear (&addr, numpages,__pgprot (_PAGE_PRESENT),0 ); } +int set_memory_np_noalias (unsigned long addr,int numpages) +{ +int cpa_flags =CPA_NO_CHECK_ALIAS ; + +return change_page_attr_set_clr (&addr, numpages,__pgprot (0 ), +__pgprot (_PAGE_PRESENT),0 , + cpa_flags,NULL ); +} +int set_memory_4k (unsigned long addr,int numpages) { return change_page_attr_set_clr(&addr, numpages, __pgprot(0),
_
Re: [PATCH 5/7] x86/mm/init: remove freed kernel image areas from alias mapping
Quoted 9 lines · Dave Hansen
From: Dave Hansen <[email protected]>
The kernel image is mapped into two places in the virtual address space (addresses without KASLR, of course):
1. The kernel direct map (
0xffff880000000000)
2. The "high kernel map" (0xffffffff81000000)
Quoted 8 lines
We actually execute out of #2. If we get the address of a kernel symbol, it points to #2, but almost all physical-to-virtual translations point to #1.
Parts of the "high kernel map" alias are mapped in the userspace page tables with the Global bit for performance reasons. The parts that we map to userspace do not (er, should not) have secrets.
If respun, I think it would be worth reminding us here that with PTI, the Global bit is not usually set on the high kernel map at all: it's just used to compensate for poor performance when PCIDs not available.
Quoted 62 lines
This is fine, except that some areas in the kernel image that are adjacent to the non-secret-containing areas are unused holes. We free these holes back into the normal page allocator and reuse them as normal kernel memory. The memory will, of course, get *used* via the normal map, but the alias mapping is kept.
This otherwise unused alias mapping of the holes will, by default keep the Global bit, be mapped out to userspace, and be vulnerable to Meltdown.
Remove the alias mapping of these pages entirely. This is likely to fracture the 2M page mapping the kernel image near these areas, but this should affect a minority of the area.
The pageattr code changes *all* aliases mapping the physical pages that it operates on (by default). We only want to modify a single alias, so we need to tweak its behavior.
This unmapping behavior is currently dependent on PTI being in place. Going forward, we should at least consider doing this for all configurations. Having an extra read-write alias for memory is not exactly ideal for debugging things like random memory corruption and this does undercut features like
DEBUG_PAGEALLOCor future work like eXclusive Page Frame Ownership (XPFO).Before this patch:
current_kernel:---[ High Kernel Mapping ]---
current_kernel-0xffffffff80000000-0xffffffff81000000 16M pmd current_kernel-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_kernel-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte current_kernel-0xffffffff81e11000-0xffffffff82000000 1980K RW NX pte current_kernel-0xffffffff82000000-0xffffffff82600000 6M ro PSE GLB NX pmd current_kernel-0xffffffff82600000-0xffffffff82c00000 6M RW PSE NX pmd current_kernel-0xffffffff82c00000-0xffffffff82e00000 2M RW NX pte current_kernel-0xffffffff82e00000-0xffffffff83200000 4M RW PSE NX pmdcurrent_kernel-0xffffffff83200000-0xffffffffa0000000 462M pmd
current_user:---[ High Kernel Mapping ]---
current_user-0xffffffff80000000-0xffffffff81000000 16M pmd current_user-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_user-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x ptecurrent_user-0xffffffff81e11000-0xffffffff82000000 1980K RW NX pte
current_user-0xffffffff82000000-0xffffffff82600000 6M ro PSE GLB NX pmd
current_user-0xffffffff82600000-0xffffffffa0000000 474M pmdAfter this patch:
current_kernel:---[ High Kernel Mapping ]---
current_kernel-0xffffffff80000000-0xffffffff81000000 16M pmd current_kernel-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_kernel-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte current_kernel-0xffffffff81e11000-0xffffffff82000000 1980K pte current_kernel-0xffffffff82000000-0xffffffff82400000 4M ro PSE GLB NX pmd current_kernel-0xffffffff82400000-0xffffffff82488000 544K ro NX pte current_kernel-0xffffffff82488000-0xffffffff82600000 1504K pte current_kernel-0xffffffff82600000-0xffffffff82c00000 6M RW PSE NX pmd current_kernel-0xffffffff82c00000-0xffffffff82c0d000 52K RW NX ptecurrent_kernel-0xffffffff82c0d000-0xffffffff82dc0000 1740K pte
Quoted 7 lines
current_user:---[ High Kernel Mapping ]---
current_user-0xffffffff80000000-0xffffffff81000000 16M pmd current_user-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_user-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte current_user-0xffffffff81e11000-0xffffffff82000000 1980K ptecurrent_user-0xffffffff82000000-0xffffffff82400000 4M ro PSE GLB NX pmd
current_user-0xffffffff82400000-0xffffffff82488000 544K ro NX pte
That entry correctly matches the current-kernel entry, but I would expect both of them to be marked "GLB". Probably of very little importance, but it might indicate that something (my brain, perhaps) is not working quite as you would hope.
Hugh
Quoted 109 lines
current_user-0xffffffff82488000-0xffffffff82600000 1504K pte
current_user-0xffffffff82600000-0xffffffffa0000000 474M pmdSigned-off-by Dave Hansen <[email protected]>Cc Kees Cook <[email protected]>Cc Thomas Gleixner <[email protected]>Cc Ingo Molnar <[email protected]>Cc Andrea Arcangeli <[email protected]>Cc Juergen Gross <[email protected]>Cc Josh Poimboeuf <[email protected]>Cc Greg Kroah-Hartman <[email protected]>Cc Peter Zijlstra <[email protected]>Cc Hugh Dickins <[email protected]>Cc Linus Torvalds <[email protected]>Cc Borislav Petkov <[email protected]>Cc Andy Lutomirski <[email protected]>Cc Andi Kleen <[email protected]>---
b/arch/x86/include/asm/set_memory.h | 1 + b/arch/x86/mm/init.c | 25 +++++++++++++++++++++++-- b/arch/x86/mm/pageattr.c | 13 +++++++++++++ 3 files changed, 37 insertions(+), 2 deletions(-)diff -puN
arch/x86/include/asm/set_memory.h~x86-unmap-freed-areas-from-kernel-imagearch/x86/include/asm/set_memory.harch/x86/include/asm/set_memory.h renamed from arch/x86/include/asm/set_memory.h~x86-unmap-freed-areas-from-kernel-image +1
-0@@ -46,6 +46,7 @@ int set_memory_np(unsigned long addr, inint set_memory_4k (unsigned long addr,int numpages);int set_memory_encrypted (unsigned long addr,int numpages);int set_memory_decrypted (unsigned long addr,int numpages); +int set_memory_np_noalias (unsigned long addr,int numpages);int set_memory_array_uc (unsigned long *addr,int addrinarray);int set_memory_array_wc (unsigned long *addr,int addrinarray);diff -puN
arch/x86/mm/init.c~x86-unmap-freed-areas-from-kernel-imagearch/x86/mm/init.carch/x86/mm/init.c renamed from arch/x86/mm/init.c~x86-unmap-freed-areas-from-kernel-image +23
-2@@ -780,8 +780,29 @@ void free_init_pages(char *what, unsigne*/ void free_kernel_image_pages (void *begin,void *end) { -free_init_pages ("unused kernel image" , - (unsigned long )begin, (unsigned long )end); +unsigned long begin_ul = (unsigned long )begin; +unsigned long end_ul = (unsigned long )end; +unsigned long len_pages = (end_ul - begin_ul) >>PAGE_SHIFT ; + + +free_init_pages ("unused kernel image" , begin_ul, end_ul); + +/* +* PTI maps some of the kernel into userspace. For +* performance, this includes some kernel areas that +* do not contain secrets. Those areas might be +* adjacent to the parts of the kernel image being +* freed, which may contain secrets. Remove the +* "high kernel image mapping" for these freed areas, +* ensuring they are not even potentially vulnerable +* to Meltdown regardless of the specific optimizations +* PTI is currently using. +* +* The "noalias" prevents unmapping the direct map +* alias which is needed to access the freed pages. +*/ +if (cpu_feature_enabled (X86_FEATURE_PTI )) +set_memory_np_noalias (begin_ul, len_pages); }void __ref free_initmem (void )diff -puN
arch/x86/mm/pageattr.c~x86-unmap-freed-areas-from-kernel-imagearch/x86/mm/pageattr.carch/x86/mm/pageattr.c renamed from arch/x86/mm/pageattr.c~x86-unmap-freed-areas-from-kernel-image +13
-0@@ -53,6 +53,7 @@ static DEFINE_SPINLOCK(cpa_lock);#define CPA_FLUSHTLB 1#define CPA_ARRAY 2#define CPA_PAGES_ARRAY 4 +#define CPA_NO_CHECK_ALIAS 8/* Do not search for aliases */ #ifdef CONFIG_PROC_FS static unsigned long direct_pages_count[PG_LEVEL_NUM ];@@ -1486,6 +1487,9 @@ static int change_page_attr_set_clr(unsi/* No alias checking for _NX bit modifications */ checkalias = (pgprot_val (mask_set) |pgprot_val (mask_clr)) != _PAGE_NX; +/* Never check aliases if the caller asks for it explicitly: */ +if (checkalias && (in_flag &CPA_NO_CHECK_ALIAS )) + checkalias =0 ; ret =__change_page_attr_set_clr (&cpa, checkalias);@@ -1772,6 +1776,15 @@ int set_memory_np(unsigned long addr, inreturn change_page_attr_clear (&addr, numpages,__pgprot (_PAGE_PRESENT),0 ); } +int set_memory_np_noalias (unsigned long addr,int numpages) +{ +int cpa_flags =CPA_NO_CHECK_ALIAS ; + +return change_page_attr_set_clr (&addr, numpages,__pgprot (0 ), +__pgprot (_PAGE_PRESENT),0 , + cpa_flags,NULL ); +} +int set_memory_4k (unsigned long addr,int numpages) { return change_page_attr_set_clr(&addr, numpages, __pgprot(0),_
Andy Lutomirski
maintainerRe: [PATCH 5/7] x86/mm/init: remove freed kernel image areas from alias mapping
In reply to Dave HansenQuoted 36 lines · Dave Hansen
From: Dave Hansen <[email protected]>
The kernel image is mapped into two places in the virtual address space (addresses without KASLR, of course):
1. The kernel direct map (
0xffff880000000000)
2. The "high kernel map" (0xffffffff81000000)We actually execute out of #2. If we get the address of a kernel symbol, it points to #2, but almost all physical-to-virtual translations point to #1.
Parts of the "high kernel map" alias are mapped in the userspace page tables with the Global bit for performance reasons. The parts that we map to userspace do not (er, should not) have secrets.
This is fine, except that some areas in the kernel image that are adjacent to the non-secret-containing areas are unused holes. We free these holes back into the normal page allocator and reuse them as normal kernel memory. The memory will, of course, get *used* via the normal map, but the alias mapping is kept.
This otherwise unused alias mapping of the holes will, by default keep the Global bit, be mapped out to userspace, and be vulnerable to Meltdown.
Remove the alias mapping of these pages entirely. This is likely to fracture the 2M page mapping the kernel image near these areas, but this should affect a minority of the area.
The pageattr code changes *all* aliases mapping the physical pages that it operates on (by default). We only want to modify a single alias, so we need to tweak its behavior.
Quoted 7 lines
This unmapping behavior is currently dependent on PTI being in place. Going forward, we should at least consider doing this for all configurations. Having an extra read-write alias for memory is not exactly ideal for debugging things like random memory corruption and this does undercut features like
DEBUG_PAGEALLOCor future work like eXclusive Page Frame Ownership (XPFO).
I like this patch, and I tend to think we should (eventually) enable it regardless of PTI. Cleaning up the memory map is generally a good thing.
Also, just to make sure I fully understand: the kernel text is aliased in both the direct map and the high map, right? This means that we should be able to make the high kernel mapping have proper RO permissions very early without breaking text_poke() at the minor cost of needing to force a serializing instruction at the end of each big block of text pokes. I think this would be worthwhile, although I suspect we'll uncover *tons* of bugs in the process.
Dave Hansen
maintainerRe: [PATCH 5/7] x86/mm/init: remove freed kernel image areas from alias mapping
Quoted 8 lines · Andy Lutomirski
Quoted 7 lines · Dave Hansen
This otherwise unused alias mapping of the holes will, by default keep the Global bit, be mapped out to userspace, and be vulnerable to Meltdown.
Remove the alias mapping of these pages entirely. This is likely to fracture the 2M page mapping the kernel image near these areas, but this should affect a minority of the area.
...
Quoted 7 lines
I like this patch, and I tend to think we should (eventually) enable it regardless of PTI. Cleaning up the memory map is generally a good thing.
Also, just to make sure I fully understand: the kernel text is aliased in both the direct map and the high map, right?
Yes. I don't think the double mapping was because of anything that we really intentionally designed, though. I think it was just easiest to leave it in place and it didn't hurt anything.
Quoted 6 lines
This means that we should be able to make the high kernel mapping have proper RO permissions very early without breaking
text_poke()at the minor cost of needing to force a serializing instruction at the end of each big block of text pokes. I think this would be worthwhile, although I suspect we'll uncover *tons* of bugs in the process.
Yeah, this could easily happen much earlier.
tip-bot for Dave Hansen
merge bot[tip:x86/pti] x86/mm/init: Remove freed kernel image areas from alias mapping
In reply to Dave Hansenx86/mm/init: Remove freed kernel image areas from alias mapping
Commit-ID: 2140e26f3d98e615c60c5f6a97d8421a077d61eb Gitweb: https://git.kernel.org/tip/2140e26f3d98e615c60c5f6a97d8421a077d61eb Author: Dave Hansen <[email protected]> AuthorDate: Thu, 2 Aug 2018 15:58:31 -0700 Committer: Thomas Gleixner <[email protected]> CommitDate: Sun, 5 Aug 2018 22:21:03 +0200
x86/mm/init: Remove freed kernel image areas from alias mapping
The kernel image is mapped into two places in the virtual address space (addresses without KASLR, of course):
1. The kernel direct map (0xffff880000000000)
2. The "high kernel map" (0xffffffff81000000)
We actually execute out of #2. If we get the address of a kernel symbol, it points to #2, but almost all physical-to-virtual translations point to #1.
Parts of the "high kernel map" alias are mapped in the userspace page tables with the Global bit for performance reasons. The parts that we map to userspace do not (er, should not) have secrets. When PTI is enabled then the global bit is usually not set in the high mapping and just used to compensate for poor performance on systems which lack PCID.
This is fine, except that some areas in the kernel image that are adjacent to the non-secret-containing areas are unused holes. We free these holes back into the normal page allocator and reuse them as normal kernel memory. The memory will, of course, get *used* via the normal map, but the alias mapping is kept.
This otherwise unused alias mapping of the holes will, by default keep the Global bit, be mapped out to userspace, and be vulnerable to Meltdown.
Remove the alias mapping of these pages entirely. This is likely to fracture the 2M page mapping the kernel image near these areas, but this should affect a minority of the area.
The pageattr code changes *all* aliases mapping the physical pages that it operates on (by default). We only want to modify a single alias, so we need to tweak its behavior.
This unmapping behavior is currently dependent on PTI being in place. Going forward, we should at least consider doing this for all configurations. Having an extra read-write alias for memory is not exactly ideal for debugging things like random memory corruption and this does undercut features like DEBUG_PAGEALLOC or future work like eXclusive Page Frame Ownership (XPFO).
Before this patch:
current_kernel:---[ High Kernel Mapping ]---
current_kernel-0xffffffff80000000-0xffffffff81000000 16M pmd current_kernel-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_kernel-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte current_kernel-0xffffffff81e11000-0xffffffff82000000 1980K RW NX pte current_kernel-0xffffffff82000000-0xffffffff82600000 6M ro PSE GLB NX pmd current_kernel-0xffffffff82600000-0xffffffff82c00000 6M RW PSE NX pmd current_kernel-0xffffffff82c00000-0xffffffff82e00000 2M RW NX pte current_kernel-0xffffffff82e00000-0xffffffff83200000 4M RW PSE NX pmd
current_kernel-0xffffffff83200000-0xffffffffa0000000 462M pmd
current_user:---[ High Kernel Mapping ]---
current_user-0xffffffff80000000-0xffffffff81000000 16M pmd current_user-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_user-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte
current_user-0xffffffff81e11000-0xffffffff82000000 1980K RW NX pte
current_user-0xffffffff82000000-0xffffffff82600000 6M ro PSE GLB NX pmd
current_user-0xffffffff82600000-0xffffffffa0000000 474M pmd
After this patch:
current_kernel:---[ High Kernel Mapping ]---
current_kernel-0xffffffff80000000-0xffffffff81000000 16M pmd current_kernel-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_kernel-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte current_kernel-0xffffffff81e11000-0xffffffff82000000 1980K pte current_kernel-0xffffffff82000000-0xffffffff82400000 4M ro PSE GLB NX pmd current_kernel-0xffffffff82400000-0xffffffff82488000 544K ro NX pte current_kernel-0xffffffff82488000-0xffffffff82600000 1504K pte current_kernel-0xffffffff82600000-0xffffffff82c00000 6M RW PSE NX pmd current_kernel-0xffffffff82c00000-0xffffffff82c0d000 52K RW NX pte
current_kernel-0xffffffff82c0d000-0xffffffff82dc0000 1740K pte
current_user:---[ High Kernel Mapping ]---
current_user-0xffffffff80000000-0xffffffff81000000 16M pmd current_user-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_user-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte current_user-0xffffffff81e11000-0xffffffff82000000 1980K pte
current_user-0xffffffff82000000-0xffffffff82400000 4M ro PSE GLB NX pmd
current_user-0xffffffff82400000-0xffffffff82488000 544K ro NX pte
current_user-0xffffffff82488000-0xffffffff82600000 1504K pte
current_user-0xffffffff82600000-0xffffffffa0000000 474M pmd
--- arch/x86/include/asm/set_memory.h | 1 + arch/x86/mm/init.c | 25 +++++++++++++++++++++++-- arch/x86/mm/pageattr.c | 13 +++++++++++++ 3 files changed, 37 insertions(+), 2 deletions(-)
arch/x86/include/asm/set_memory.h +1 -0
@@ -46,6 +46,7 @@ int set_memory_np(unsigned long addr, int numpages);int set_memory_4k (unsigned long addr,int numpages);int set_memory_encrypted (unsigned long addr,int numpages);int set_memory_decrypted (unsigned long addr,int numpages); +int set_memory_np_noalias (unsigned long addr,int numpages);int set_memory_array_uc (unsigned long *addr,int addrinarray);int set_memory_array_wc (unsigned long *addr,int addrinarray);
arch/x86/mm/init.c +23 -2
@@ -780,8 +780,29 @@ void free_init_pages(char *what, unsigned long begin, unsigned long end)*/ void free_kernel_image_pages (void *begin,void *end) { -free_init_pages ("unused kernel image" , - (unsigned long )begin, (unsigned long )end); +unsigned long begin_ul = (unsigned long )begin; +unsigned long end_ul = (unsigned long )end; +unsigned long len_pages = (end_ul - begin_ul) >>PAGE_SHIFT ; + + +free_init_pages ("unused kernel image" , begin_ul, end_ul); + +/* +* PTI maps some of the kernel into userspace. For +* performance, this includes some kernel areas that +* do not contain secrets. Those areas might be +* adjacent to the parts of the kernel image being +* freed, which may contain secrets. Remove the +* "high kernel image mapping" for these freed areas, +* ensuring they are not even potentially vulnerable +* to Meltdown regardless of the specific optimizations +* PTI is currently using. +* +* The "noalias" prevents unmapping the direct map +* alias which is needed to access the freed pages. +*/ +if (cpu_feature_enabled (X86_FEATURE_PTI )) +set_memory_np_noalias (begin_ul, len_pages); }void __ref free_initmem (void )
arch/x86/mm/pageattr.c +13 -0
@@ -53,6 +53,7 @@ static DEFINE_SPINLOCK(cpa_lock);#define CPA_FLUSHTLB 1#define CPA_ARRAY 2#define CPA_PAGES_ARRAY 4 +#define CPA_NO_CHECK_ALIAS 8/* Do not search for aliases */ #ifdef CONFIG_PROC_FS static unsigned long direct_pages_count[PG_LEVEL_NUM ];
@@ -1486,6 +1487,9 @@ static int change_page_attr_set_clr(unsigned long *addr, int numpages,/* No alias checking for _NX bit modifications */ checkalias = (pgprot_val (mask_set) |pgprot_val (mask_clr)) != _PAGE_NX; +/* Never check aliases if the caller asks for it explicitly: */ +if (checkalias && (in_flag &CPA_NO_CHECK_ALIAS )) + checkalias =0 ; ret =__change_page_attr_set_clr (&cpa, checkalias);
@@ -1772,6 +1776,15 @@ int set_memory_np(unsigned long addr, int numpages)return change_page_attr_clear (&addr, numpages,__pgprot (_PAGE_PRESENT),0 ); } +int set_memory_np_noalias (unsigned long addr,int numpages) +{ +int cpa_flags =CPA_NO_CHECK_ALIAS ; + +return change_page_attr_set_clr (&addr, numpages,__pgprot (0 ), +__pgprot (_PAGE_PRESENT),0 , + cpa_flags,NULL ); +} +int set_memory_4k (unsigned long addr,int numpages) { return change_page_attr_set_clr(&addr, numpages, __pgprot(0),
tip-bot for Dave Hansen
merge bot[tip:x86/pti-urgent] x86/mm/init: Remove freed kernel image areas from alias mapping
In reply to Dave Hansenx86/mm/init: Remove freed kernel image areas from alias mapping
Commit-ID: c40a56a7818cfe735fc93a69e1875f8bba834483 Gitweb: https://git.kernel.org/tip/c40a56a7818cfe735fc93a69e1875f8bba834483 Author: Dave Hansen <[email protected]> AuthorDate: Thu, 2 Aug 2018 15:58:31 -0700 Committer: Thomas Gleixner <[email protected]> CommitDate: Mon, 6 Aug 2018 20:54:16 +0200
x86/mm/init: Remove freed kernel image areas from alias mapping
The kernel image is mapped into two places in the virtual address space (addresses without KASLR, of course):
1. The kernel direct map (0xffff880000000000)
2. The "high kernel map" (0xffffffff81000000)
We actually execute out of #2. If we get the address of a kernel symbol, it points to #2, but almost all physical-to-virtual translations point to
Parts of the "high kernel map" alias are mapped in the userspace page tables with the Global bit for performance reasons. The parts that we map to userspace do not (er, should not) have secrets. When PTI is enabled then the global bit is usually not set in the high mapping and just used to compensate for poor performance on systems which lack PCID.
This is fine, except that some areas in the kernel image that are adjacent to the non-secret-containing areas are unused holes. We free these holes back into the normal page allocator and reuse them as normal kernel memory. The memory will, of course, get *used* via the normal map, but the alias mapping is kept.
This otherwise unused alias mapping of the holes will, by default keep the Global bit, be mapped out to userspace, and be vulnerable to Meltdown.
Remove the alias mapping of these pages entirely. This is likely to fracture the 2M page mapping the kernel image near these areas, but this should affect a minority of the area.
The pageattr code changes *all* aliases mapping the physical pages that it operates on (by default). We only want to modify a single alias, so we need to tweak its behavior.
This unmapping behavior is currently dependent on PTI being in place. Going forward, we should at least consider doing this for all configurations. Having an extra read-write alias for memory is not exactly ideal for debugging things like random memory corruption and this does undercut features like DEBUG_PAGEALLOC or future work like eXclusive Page Frame Ownership (XPFO).
Before this patch:
current_kernel:---[ High Kernel Mapping ]---
current_kernel-0xffffffff80000000-0xffffffff81000000 16M pmd current_kernel-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_kernel-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte current_kernel-0xffffffff81e11000-0xffffffff82000000 1980K RW NX pte current_kernel-0xffffffff82000000-0xffffffff82600000 6M ro PSE GLB NX pmd current_kernel-0xffffffff82600000-0xffffffff82c00000 6M RW PSE NX pmd current_kernel-0xffffffff82c00000-0xffffffff82e00000 2M RW NX pte current_kernel-0xffffffff82e00000-0xffffffff83200000 4M RW PSE NX pmd
current_kernel-0xffffffff83200000-0xffffffffa0000000 462M pmd
current_user:---[ High Kernel Mapping ]---
current_user-0xffffffff80000000-0xffffffff81000000 16M pmd current_user-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_user-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte
current_user-0xffffffff81e11000-0xffffffff82000000 1980K RW NX pte
current_user-0xffffffff82000000-0xffffffff82600000 6M ro PSE GLB NX pmd
current_user-0xffffffff82600000-0xffffffffa0000000 474M pmd
After this patch:
current_kernel:---[ High Kernel Mapping ]---
current_kernel-0xffffffff80000000-0xffffffff81000000 16M pmd current_kernel-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_kernel-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte current_kernel-0xffffffff81e11000-0xffffffff82000000 1980K pte current_kernel-0xffffffff82000000-0xffffffff82400000 4M ro PSE GLB NX pmd current_kernel-0xffffffff82400000-0xffffffff82488000 544K ro NX pte current_kernel-0xffffffff82488000-0xffffffff82600000 1504K pte current_kernel-0xffffffff82600000-0xffffffff82c00000 6M RW PSE NX pmd current_kernel-0xffffffff82c00000-0xffffffff82c0d000 52K RW NX pte
current_kernel-0xffffffff82c0d000-0xffffffff82dc0000 1740K pte
current_user:---[ High Kernel Mapping ]---
current_user-0xffffffff80000000-0xffffffff81000000 16M pmd current_user-0xffffffff81000000-0xffffffff81e00000 14M ro PSE GLB x pmd current_user-0xffffffff81e00000-0xffffffff81e11000 68K ro GLB x pte current_user-0xffffffff81e11000-0xffffffff82000000 1980K pte
current_user-0xffffffff82000000-0xffffffff82400000 4M ro PSE GLB NX pmd
current_user-0xffffffff82400000-0xffffffff82488000 544K ro NX pte
current_user-0xffffffff82488000-0xffffffff82600000 1504K pte
current_user-0xffffffff82600000-0xffffffffa0000000 474M pmd
[ tglx: Do not unmap on 32bit as there is only one mapping ]
--- arch/x86/include/asm/set_memory.h | 1 + arch/x86/mm/init.c | 26 ++++++++++++++++++++++++-- arch/x86/mm/pageattr.c | 13 +++++++++++++ 3 files changed, 38 insertions(+), 2 deletions(-)
arch/x86/include/asm/set_memory.h +1 -0
@@ -46,6 +46,7 @@ int set_memory_np(unsigned long addr, int numpages);int set_memory_4k (unsigned long addr,int numpages);int set_memory_encrypted (unsigned long addr,int numpages);int set_memory_decrypted (unsigned long addr,int numpages); +int set_memory_np_noalias (unsigned long addr,int numpages);int set_memory_array_uc (unsigned long *addr,int addrinarray);int set_memory_array_wc (unsigned long *addr,int addrinarray);
arch/x86/mm/init.c +24 -2
@@ -780,8 +780,30 @@ void free_init_pages(char *what, unsigned long begin, unsigned long end)*/ void free_kernel_image_pages (void *begin,void *end) { -free_init_pages ("unused kernel image" , - (unsigned long )begin, (unsigned long )end); +unsigned long begin_ul = (unsigned long )begin; +unsigned long end_ul = (unsigned long )end; +unsigned long len_pages = (end_ul - begin_ul) >>PAGE_SHIFT ; + + +free_init_pages ("unused kernel image" , begin_ul, end_ul); + +/* +* PTI maps some of the kernel into userspace. For performance, +* this includes some kernel areas that do not contain secrets. +* Those areas might be adjacent to the parts of the kernel image +* being freed, which may contain secrets. Remove the "high kernel +* image mapping" for these freed areas, ensuring they are not even +* potentially vulnerable to Meltdown regardless of the specific +* optimizations PTI is currently using. +* +* The "noalias" prevents unmapping the direct map alias which is +* needed to access the freed pages. +* +* This is only valid for 64bit kernels. 32bit has only one mapping +* which can't be treated in this way for obvious reasons. +*/ +if (IS_ENABLED (CONFIG_X86_64 ) &&cpu_feature_enabled (X86_FEATURE_PTI )) +set_memory_np_noalias (begin_ul, len_pages); }void __ref free_initmem (void )
arch/x86/mm/pageattr.c +13 -0
@@ -53,6 +53,7 @@ static DEFINE_SPINLOCK(cpa_lock);#define CPA_FLUSHTLB 1#define CPA_ARRAY 2#define CPA_PAGES_ARRAY 4 +#define CPA_NO_CHECK_ALIAS 8/* Do not search for aliases */ #ifdef CONFIG_PROC_FS static unsigned long direct_pages_count[PG_LEVEL_NUM ];
@@ -1486,6 +1487,9 @@ static int change_page_attr_set_clr(unsigned long *addr, int numpages,/* No alias checking for _NX bit modifications */ checkalias = (pgprot_val (mask_set) |pgprot_val (mask_clr)) != _PAGE_NX; +/* Has caller explicitly disabled alias checking? */ +if (in_flag &CPA_NO_CHECK_ALIAS ) + checkalias =0 ; ret =__change_page_attr_set_clr (&cpa, checkalias);
@@ -1772,6 +1776,15 @@ int set_memory_np(unsigned long addr, int numpages)return change_page_attr_clear (&addr, numpages,__pgprot (_PAGE_PRESENT),0 ); } +int set_memory_np_noalias (unsigned long addr,int numpages) +{ +int cpa_flags =CPA_NO_CHECK_ALIAS ; + +return change_page_attr_set_clr (&addr, numpages,__pgprot (0 ), +__pgprot (_PAGE_PRESENT),0 , + cpa_flags,NULL ); +} +int set_memory_4k (unsigned long addr,int numpages) { return change_page_attr_set_clr(&addr, numpages, __pgprot(0),
Dave Hansen
maintainerPATCH v2 6/7 x86/mm/pageattr: pass named flag instead of 0/1
In reply to Dave HansenFrom: Dave Hansen <[email protected]>
This is a cleanup. There should be functional changes in this patch.
change_page_attr_set/clear() take an 0/1 argument to indicate whether CPA_ARRAY should be passed down to change_page_attr_set/clear(). Rather than having a 0/1 argument to turn a single flag on/off, just pass down the flag itself.
---
b/arch/x86/mm/pageattr.c | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-)
arch/x86/mm/pageattr.c renamed from arch/x86/mm/pageattr.c~x86-pageattr-pass-flags +8 -6
@@ -1525,17 +1525,17 @@ out: }static inline int change_page_attr_set (unsigned long *addr,int numpages, -pgprot_t mask,int array) +pgprot_t mask,int flags) {return change_page_attr_set_clr (addr, numpages, mask,__pgprot (0 ),0 , - (array ?CPA_ARRAY :0 ),NULL ); + flags,NULL ); }static inline int change_page_attr_clear (unsigned long *addr,int numpages, -pgprot_t mask,int array) +pgprot_t mask,int flags) {return change_page_attr_set_clr (addr, numpages,__pgprot (0 ), mask,0 , - (array ?CPA_ARRAY :0 ),NULL ); + flags,NULL ); } static inline int cpa_set_pages_array(struct page **pages, int numpages,
@@ -1609,7 +1609,8 @@ static int _set_memory_array(unsigned lo _PAGE_CACHE_MODE_UC_MINUS : new_type; ret =change_page_attr_set (addr, addrinarray, -cachemode2pgprot (set_type),1 ); +cachemode2pgprot (set_type), +CPA_ARRAY );if (!ret && new_type == _PAGE_CACHE_MODE_WC) ret = change_page_attr_set_clr(addr, addrinarray,
@@ -1732,7 +1733,8 @@ int set_memory_array_wb(unsigned long *a/* WB cache mode is hard wired to all cache attribute bits being 0 */ ret =change_page_attr_clear (addr, addrinarray, -__pgprot (_PAGE_CACHE_MASK),1 ); +__pgprot (_PAGE_CACHE_MASK), +CPA_ARRAY );if (ret)return ret;
_
Re: [PATCH 6/7] x86/mm/pageattr: pass named flag instead of 0/1
Quoted 4 lines · Dave Hansen
From: Dave Hansen <[email protected]>
This is a cleanup. There should be functional changes in this patch.
Missing 'no' after 'be', right?
Thanks,
tglx
Dave Hansen
maintainerRe: [PATCH 6/7] x86/mm/pageattr: pass named flag instead of 0/1
Quoted 4 lines · Thomas Gleixner
Quoted 3 lines
From: Dave Hansen <[email protected]>
This is a cleanup. There should be functional changes in this patch.
Missing 'no' after 'be', right?
Correct. Should be:
"This is a cleanup. There should be no functional changes in this patch."
Dave Hansen
maintainerPATCH v2 7/7 x86/mm/pageattr: Remove implicit NX behavior
In reply to Dave HansenFrom: Dave Hansen <[email protected]>
This is a cleanup. There should be functional changes in this patch.
The pageattr code has the ability to find and change aliases mappings. It does this for requests by default unless the page protections being modified contain only the NX bit.
But, this behavior is rather obscure and buried very deep within the infrastructure. Rather than doing it implicitly from NX, use the new CPA_NO_CHECK_ALIAS to do it more explicitly from the call site where NX is set.
---
b/arch/x86/mm/pageattr.c | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-)
arch/x86/mm/pageattr.c renamed from arch/x86/mm/pageattr.c~x86-pageattr-nx +6 -4
@@ -1485,8 +1485,6 @@ static int change_page_attr_set_clr(unsiif (in_flag & (CPA_ARRAY |CPA_PAGES_ARRAY )) cpa.flags |= in_flag; -/* No alias checking for _NX bit modifications */ - checkalias = (pgprot_val (mask_set) |pgprot_val (mask_clr)) != _PAGE_NX;/* Never check aliases if the caller asks for it explicitly: */ if (checkalias && (in_flag &CPA_NO_CHECK_ALIAS )) checkalias =0 ;
@@ -1750,7 +1748,9 @@ int set_memory_x(unsigned long addr, intif (!(__supported_pte_mask & _PAGE_NX))return 0 ; -return change_page_attr_clear (&addr, numpages,__pgprot (_PAGE_NX),0 ); +/* NX is not required to be consistent across aliases. */ +return change_page_attr_clear (&addr, numpages,__pgprot (_PAGE_NX), +CPA_NO_CHECK_ALIAS ); }EXPORT_SYMBOL (set_memory_x);
@@ -1759,7 +1759,9 @@ int set_memory_nx(unsigned long addr, inif (!(__supported_pte_mask & _PAGE_NX))return 0 ; -return change_page_attr_set (&addr, numpages,__pgprot (_PAGE_NX),0 ); +/* NX is not required to be consistent across aliases. */ +return change_page_attr_set (&addr, numpages,__pgprot (_PAGE_NX), +CPA_NO_CHECK_ALIAS ); }EXPORT_SYMBOL (set_memory_nx);
_