Skip to contentSkip to conversation

arm64: enable PTE type bit in the mask for pte_modify

PATCH New Feng Kan 2 participants 2 messages Feb 24, 2015 – Feb 25, 2015 arm64

lore
Share & tools
lore

Feng Kan

author
#0 lore raw

PATCH 1/1 arm64: enable PTE type bit in the mask for pte_modify

Caught during Trinity testing. The pte_modify does not allow modification for PTE type bit. This cause the test to hang the system. It is found that the PTE can't transit from an inaccessible page (b00) to a valid page (b11) because the mask does not allow it. This happens when a big block of mmaped memory is set the PROT_NONE, then the a small piece is broken off and set to PROT_WRITE | PROT_READ cause a huge page split.

---
 arch/arm64/include/asm/pgtable.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/include/asm/pgtable.h +1 -1
index a26a574..8255b52 100644
@@ -462,7 +462,7 @@ static inline pud_t *pud_offset(pgd_t *pgd, unsigned long addr)
 static inline pte_t pte_modify(pte_t pte, pgprot_t newprot)
 {
 	const pteval_t mask = PTE_USER | PTE_PXN | PTE_UXN | PTE_RDONLY |
-			      PTE_PROT_NONE | PTE_VALID | PTE_WRITE;
+			      PTE_PROT_NONE | PTE_WRITE | PTE_TYPE_MASK;
 	pte_val(pte) = (pte_val(pte) & ~mask) | (pgprot_val(newprot) & mask);
 	return pte;
 }
Signature · 1 line
1.9.1
maintainer
#1 lore raw

PATCH 1/1 arm64: enable PTE type bit in the mask for pte_modify

Quoted 9 lines · Feng Kan

Caught during Trinity testing. The pte_modify does not allow modification for PTE type bit. This cause the test to hang the system. It is found that the PTE can't transit from an inaccessible page (b00) to a valid page (b11) because the mask does not allow it. This happens when a big block of mmaped memory is set the PROT_NONE, then the a small piece is broken off and set to PROT_WRITE | PROT_READ cause a huge page split.

It looks fine to me. Thanks.

I wonder whether mprotect() to change between PROT_NONE and an accessible protection ever worked (I thought we tested this).

Signature · 1 line
Catalin