From: Catalin Marinas <catalin.marinas@arm.com>
To: Vincenzo Frascino <vincenzo.frascino@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Will Deacon <will.deacon@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/4] arm64: compat: Alloc separate pages for vectors and sigpage
Date: Tue, 2 Apr 2019 15:31:34 +0100 [thread overview]
Message-ID: <20190402143134.7dlfj2vb5fwmfnfk@mbp> (raw)
In-Reply-To: <20190402111304.20825-2-vincenzo.frascino@arm.com>
On Tue, Apr 02, 2019 at 12:13:01PM +0100, Vincenzo Frascino wrote:
> In the current implementation AArch32 installs a special page called
> "[vectors]" that contains sigreturn trampolines and kuser helpers,
> and this is done at fixed address specified by the kuser helpers ABI.
>
> Having sigreturn trampolines and kuser helpers in the same page, makes
> difficult to maintain compatibility with arm because it makes not
> possible to disable kuser helpers.
>
> Address the problem creating separate pages for vectors and sigpage in
> a similar fashion to what happens today on arm.
>
> Change as well the meaning of mm->context.vdso for AArch32 compat since
> it now points to sigpage and not to vectors anymore in order to make
> simpler the implementation of the signal handling (the address of
> sigpage is randomized).
>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Signed-off-by: Vincenzo Frascino <vincenzo.frascino@arm.com>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
_______________________________________________
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-04-02 14:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 11:13 [PATCH v2 0/4] arm64: compat: Add kuser helpers config option Vincenzo Frascino
2019-04-02 11:13 ` [PATCH v2 1/4] arm64: compat: Alloc separate pages for vectors and sigpage Vincenzo Frascino
2019-04-02 14:31 ` Catalin Marinas [this message]
2019-04-02 11:13 ` [PATCH v2 2/4] arm64: compat: Split kuser32 Vincenzo Frascino
2019-04-02 14:35 ` Catalin Marinas
2019-04-02 11:13 ` [PATCH v2 3/4] arm64: compat: Refactor aarch32_alloc_vdso_pages() Vincenzo Frascino
2019-04-02 14:20 ` Catalin Marinas
2019-04-02 14:36 ` Vincenzo Frascino
2019-04-02 11:13 ` [PATCH v2 4/4] arm64: compat: Add KUSER_HELPERS config option Vincenzo Frascino
2019-04-02 14: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=20190402143134.7dlfj2vb5fwmfnfk@mbp \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=vincenzo.frascino@arm.com \
--cc=will.deacon@arm.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