From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: "Paul Elliott" <paul.elliott@arm.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Andrew Jones" <drjones@redhat.com>,
"Amit Kachhap" <amit.kachhap@arm.com>,
"Vincenzo Frascino" <vincenzo.frascino@arm.com>,
"Will Deacon" <will@kernel.org>,
linux-arch@vger.kernel.org, "Marc Zyngier" <maz@kernel.org>,
"Eugene Syromiatnikov" <esyr@redhat.com>,
"Szabolcs Nagy" <szabolcs.nagy@arm.com>,
"Dave Martin" <Dave.Martin@arm.com>,
"H.J. Lu" <hjl.tools@gmail.com>,
"Yu-cheng Yu" <yu-cheng.yu@intel.com>,
"Kees Cook" <keescook@chromium.org>,
"Arnd Bergmann" <arnd@arndb.de>, "Jann Horn" <jannh@google.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Kristina Martšenko" <kristina.martsenko@arm.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org,
"Florian Weimer" <fweimer@redhat.com>,
linux-kernel@vger.kernel.org, "Sudakshina Das" <sudi.das@arm.com>
Subject: Re: [PATCH v4 03/12] mm: Reserve asm-generic prot flag 0x10 for arch use
Date: Thu, 12 Dec 2019 10:48:32 +0000 [thread overview]
Message-ID: <20191212104831.GD18258@arrakis.emea.arm.com> (raw)
In-Reply-To: <20191211154206.46260-4-broonie@kernel.org>
On Wed, Dec 11, 2019 at 03:41:57PM +0000, Mark Brown wrote:
> From: Dave Martin <Dave.Martin@arm.com>
>
> The asm-generic mman definitions are used by a few architectures
> that also define an arch-specific PROT flag with value 0x10. This
> currently applies to sparc and powerpc, and arm64 will soon join
> in.
>
> To help future maintainers, document the use of this flag in the
> asm-generic header too.
>
> Signed-off-by: Dave Martin <Dave.Martin@arm.com>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
> include/uapi/asm-generic/mman-common.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/uapi/asm-generic/mman-common.h b/include/uapi/asm-generic/mman-common.h
> index c160a5354eb6..81442d2aaecb 100644
> --- a/include/uapi/asm-generic/mman-common.h
> +++ b/include/uapi/asm-generic/mman-common.h
> @@ -11,6 +11,7 @@
> #define PROT_WRITE 0x2 /* page can be written */
> #define PROT_EXEC 0x4 /* page can be executed */
> #define PROT_SEM 0x8 /* page may be used for atomic ops */
> + /* 0x10 reserved for arch-specific use */
> #define PROT_NONE 0x0 /* page can not be accessed */
> #define PROT_GROWSDOWN 0x01000000 /* mprotect flag: extend change to start of growsdown vma */
> #define PROT_GROWSUP 0x02000000 /* mprotect flag: extend change to end of growsup vma */
Since the BTI will likely be merged before the MTE series, please
consider reserving 0x20 as well. The updated patch, acked by Arnd:
https://lore.kernel.org/linux-arm-kernel/20191211184027.20130-2-catalin.marinas@arm.com/
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-12-12 10:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 15:41 [PATCH v4 00/12] arm64: ARMv8.5-A: Branch Target Identification support Mark Brown
2019-12-11 15:41 ` [PATCH v4 01/12] ELF: UAPI and Kconfig additions for ELF program properties Mark Brown
2020-01-14 15:03 ` Catalin Marinas
2019-12-11 15:41 ` [PATCH v4 02/12] ELF: Add ELF program property parsing support Mark Brown
2020-01-14 16:34 ` Catalin Marinas
2020-01-14 17:28 ` Mark Brown
2019-12-11 15:41 ` [PATCH v4 03/12] mm: Reserve asm-generic prot flag 0x10 for arch use Mark Brown
2019-12-12 10:48 ` Catalin Marinas [this message]
2019-12-12 16:16 ` Mark Brown
2019-12-11 15:41 ` [PATCH v4 04/12] arm64: Basic Branch Target Identification support Mark Brown
2020-01-10 18:28 ` Catalin Marinas
2020-01-13 14:00 ` Mark Brown
2019-12-11 15:41 ` [PATCH v4 05/12] elf: Allow arch to tweak initial mmap prot flags Mark Brown
2020-01-14 16:38 ` Catalin Marinas
2019-12-11 15:42 ` [PATCH v4 06/12] arm64: elf: Enable BTI at exec based on ELF program properties Mark Brown
2020-01-14 17:33 ` Catalin Marinas
2019-12-11 15:42 ` [PATCH v4 07/12] arm64: BTI: Decode BYTPE bits when printing PSTATE Mark Brown
2020-01-14 17:34 ` Catalin Marinas
2019-12-11 15:42 ` [PATCH v4 08/12] arm64: unify native/compat instruction skipping Mark Brown
2020-01-13 16:43 ` Catalin Marinas
2019-12-11 15:42 ` [PATCH v4 09/12] arm64: traps: Shuffle code to eliminate forward declarations Mark Brown
2020-01-14 17:35 ` Catalin Marinas
2019-12-11 15:42 ` [PATCH v4 10/12] arm64: BTI: Reset BTYPE when skipping emulated instructions Mark Brown
2020-01-14 17:36 ` Catalin Marinas
2019-12-11 15:42 ` [PATCH v4 11/12] KVM: " Mark Brown
2020-01-14 17:36 ` Catalin Marinas
2019-12-11 15:42 ` [PATCH v4 12/12] arm64: mm: Display guarded pages in ptdump Mark Brown
2020-01-14 17:37 ` Catalin Marinas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191212104831.GD18258@arrakis.emea.arm.com \
--to=catalin.marinas@arm.com \
--cc=Dave.Martin@arm.com \
--cc=amit.kachhap@arm.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=drjones@redhat.com \
--cc=esyr@redhat.com \
--cc=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=kristina.martsenko@arm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=paul.elliott@arm.com \
--cc=peterz@infradead.org \
--cc=richard.henderson@linaro.org \
--cc=sudi.das@arm.com \
--cc=szabolcs.nagy@arm.com \
--cc=tglx@linutronix.de \
--cc=vincenzo.frascino@arm.com \
--cc=will@kernel.org \
--cc=yu-cheng.yu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).