From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-x241.google.com (mail-pf0-x241.google.com [IPv6:2607:f8b0:400e:c00::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3x2XDv4TZZzDqhn for ; Wed, 5 Jul 2017 17:14:39 +1000 (AEST) Received: by mail-pf0-x241.google.com with SMTP id e199so33816674pfh.0 for ; Wed, 05 Jul 2017 00:14:39 -0700 (PDT) From: Balbir Singh To: linuxppc-dev@lists.ozlabs.org, mpe@ellerman.id.au Subject: [PATCH 0/3] Have CONFIG_STRICT_KERNEL_RWX work with CONFIG_RELOCATABLE Date: Wed, 5 Jul 2017 17:14:22 +1000 Message-Id: <20170705071425.5417-1-bsingharora@gmail.com> List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , These patches make CONFIG_STRICT_KERNEL_RWX work with CONFIG_RELOCATABLE The first patch splits up the radix linear mapping nicely on relocation to support granular read-only and execution bits. The second patch warns if relocation is actually done (PHYSICAL_START > MEMORY_START), we do best effort support of expected permissions. We could do more granular linear mapping, but we decided to leave it as a TODO (to check for performance/MPSS/etc). The last patch changes the config so that we are no longer dependent on !RELOCATABLE for CONFIG_STRICT_KERNEL_RWX feature. Balbir Singh (3): powerpc/mm/radix: Fix relocatable radix mappings for STRICT_RWX powerpc/mm/hash: WARN if relocation is enabled and CONFIG_STRICT_KERNEL_RWX powerpc/strict_kernel_rwx: Don't depend on !RELOCATABLE arch/powerpc/Kconfig | 2 +- arch/powerpc/mm/pgtable-hash64.c | 7 +- arch/powerpc/mm/pgtable-radix.c | 225 +++++++++++++++++++++++++++++++-------- 3 files changed, 186 insertions(+), 48 deletions(-) -- 2.9.4