lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-Id: <1522112702-27853-1-git-send-email-linuxram@us.ibm.com> Date: Mon, 26 Mar 2018 18:05:02 -0700 From: Ram Pai <linuxram@...ibm.com> To: mpe@...erman.id.au, mingo@...hat.com, akpm@...ux-foundation.org Cc: linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org, dave.hansen@...el.com, benh@...nel.crashing.org, paulus@...ba.org, aneesh.kumar@...ux.vnet.ibm.com, bsingharora@...il.com, hbabu@...ibm.com, mhocko@...nel.org, bauerman@...ux.vnet.ibm.com, linuxram@...ibm.com, fweimer@...hat.com, msuchanek@...e.com, tglx@...utronix.de, shuah@...nel.org Subject: [PATCH v2] powerpc, pkey: make protection key 0 less special Applications need the ability to associate an address-range with some key and latter revert to its initial default key. Pkey-0 comes close to providing this function but falls short, because the current implementation disallows applications to explicitly associate pkey-0 to the address range. Lets make pkey-0 less special and treat it almost like any other key. Thus it can be explicitly associated with any address range, and can be freed. This gives the application more flexibility and power. The ability to free pkey-0 must be used responsibily, since pkey-0 is associated with almost all address-range by default. Even with this change pkey-0 continues to be slightly more special from the following point of view. (a) it is implicitly allocated. (b) it is the default key assigned to any address-range. Tested on powerpc. cc: Thomas Gleixner <tglx@...utronix.de> cc: Dave Hansen <dave.hansen@...el.com> cc: Michael Ellermen <mpe@...erman.id.au> cc: Ingo Molnar <mingo@...nel.org> cc: Andrew Morton <akpm@...ux-foundation.org> Signed-off-by: Ram Pai <linuxram@...ibm.com> --- History: v2: mm_pkey_is_allocated() continued to treat pkey-0 special. fixed it. arch/powerpc/include/asm/pkeys.h | 20 ++++++++++++++++---- arch/powerpc/mm/pkeys.c | 20 ++++++++++++-------- 2 files changed, 28 insertions(+), 12 deletions(-) diff --git a/arch/powerpc/include/asm/pkeys.h b/arch/powerpc/include/asm/pkeys.h index 0409c80..b598fa9 100644 --- a/arch/powerpc/include/asm/pkeys.h +++ b/arch/powerpc/include/asm/pkeys.h @@ -101,10 +101,14 @@ static inline u16 pte_to_pkey_bits(u64 pteflags) static inline bool mm_pkey_is_allocated(struct mm_struct *mm, int pkey) { - /* A reserved key is never considered as 'explicitly allocated' */ - return ((pkey < arch_max_pkey()) && - !__mm_pkey_is_reserved(pkey) && - __mm_pkey_is_allocated(mm, pkey)); + if (pkey < 0 || pkey >= arch_max_pkey()) + return false; + + /* Reserved keys are never allocated. */ + if (__mm_pkey_is_reserved(pkey)) + return false; + + return __mm_pkey_is_allocated(mm, pkey); } extern void __arch_activate_pkey(int pkey); @@ -200,6 +204,14 @@ static inline int arch_set_user_pkey_access(struct task_struct *tsk, int pkey, { if (static_branch_likely(&pkey_disabled)) return -EINVAL; + + /* + * userspace is discouraged from changing permissions of + * pkey-0. powerpc hardware does not support it anyway. + */ + if (!pkey) + return init_val ? -EINVAL : 0; + return __arch_set_user_pkey_access(tsk, pkey, init_val); } diff --git a/arch/powerpc/mm/pkeys.c b/arch/powerpc/mm/pkeys.c index ba71c54..e7a9e34 100644 --- a/arch/powerpc/mm/pkeys.c +++ b/arch/powerpc/mm/pkeys.c @@ -119,19 +119,21 @@ int pkey_initialize(void) #else os_reserved = 0; #endif - /* - * Bits are in LE format. NOTE: 1, 0 are reserved. - * key 0 is the default key, which allows read/write/execute. - * key 1 is recommended not to be used. PowerISA(3.0) page 1015, - * programming note. - */ + /* Bits are in LE format. */ initial_allocation_mask = ~0x0; /* register mask is in BE format */ pkey_amr_uamor_mask = ~0x0ul; pkey_iamr_mask = ~0x0ul; - for (i = 2; i < (pkeys_total - os_reserved); i++) { + for (i = 0; i < (pkeys_total - os_reserved); i++) { + /* + * key 1 is recommended not to be used. + * PowerISA(3.0) page 1015, + */ + if (i == 1) + continue; + initial_allocation_mask &= ~(0x1 << i); pkey_amr_uamor_mask &= ~(0x3ul << pkeyshift(i)); pkey_iamr_mask &= ~(0x1ul << pkeyshift(i)); @@ -145,7 +147,9 @@ void pkey_mm_init(struct mm_struct *mm) { if (static_branch_likely(&pkey_disabled)) return; - mm_pkey_allocation_map(mm) = initial_allocation_mask; + + /* allocate key-0 by default */ + mm_pkey_allocation_map(mm) = initial_allocation_mask | 0x1; /* -1 means unallocated or invalid */ mm->context.execute_only_pkey = -1; } -- 1.8.3.1
Powered by blists - more mailing lists