From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Will Deacon <will@kernel.org>, linux-arm-kernel@lists.infradead.org
Cc: kernel-team@android.com,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Marc Zyngier <maz@kernel.org>,
Russell King <rmk+kernel@armlinux.org.uk>
Subject: Re: [PATCH 3/5] arm64: compat: Allow signal page to be remapped
Date: Thu, 18 Mar 2021 18:06:34 +0000 [thread overview]
Message-ID: <b52b6e22-c3d3-ed74-4c5f-d59f1a986589@arm.com> (raw)
In-Reply-To: <20210318170738.7756-4-will@kernel.org>
On 3/18/21 5:07 PM, Will Deacon wrote:
> For compatability with 32-bit Arm, allow the compat signal page to be
> remapped via mremap().
>
> Signed-off-by: Will Deacon <will@kernel.org>
Reviewed-by: Vincenzo Frascino <vincenzo.frascino@arm.com>
> ---
> arch/arm64/kernel/vdso.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/arch/arm64/kernel/vdso.c b/arch/arm64/kernel/vdso.c
> index 421411981dc3..16bf0b46fb70 100644
> --- a/arch/arm64/kernel/vdso.c
> +++ b/arch/arm64/kernel/vdso.c
> @@ -271,6 +271,14 @@ enum aarch32_map {
> static struct page *aarch32_vectors_page __ro_after_init;
> static struct page *aarch32_sig_page __ro_after_init;
>
> +static int aarch32_sigpage_mremap(const struct vm_special_mapping *sm,
> + struct vm_area_struct *new_vma)
> +{
> + current->mm->context.sigpage = (void *)new_vma->vm_start;
> +
> + return 0;
> +}
> +
> static struct vm_special_mapping aarch32_vdso_maps[] = {
> [AA32_MAP_VECTORS] = {
> .name = "[vectors]", /* ABI */
> @@ -279,6 +287,7 @@ static struct vm_special_mapping aarch32_vdso_maps[] = {
> [AA32_MAP_SIGPAGE] = {
> .name = "[sigpage]", /* ABI */
> .pages = &aarch32_sig_page,
> + .mremap = aarch32_sigpage_mremap,
> },
> [AA32_MAP_VVAR] = {
> .name = "[vvar]",
>
--
Regards,
Vincenzo
_______________________________________________
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:[~2021-03-18 18:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 17:07 [PATCH 0/5] Minor improvements to the compat vdso and sigpage Will Deacon
2021-03-18 17:07 ` [PATCH 1/5] arm64: vdso: Use GFP_KERNEL for allocating compat vdso and signal pages Will Deacon
2021-03-18 18:03 ` Vincenzo Frascino
2021-03-24 17:28 ` Catalin Marinas
2021-03-18 17:07 ` [PATCH 2/5] arm64: vdso: Remove redundant calls to flush_dcache_page() Will Deacon
2021-03-18 18:05 ` Vincenzo Frascino
2021-03-18 17:07 ` [PATCH 3/5] arm64: compat: Allow signal page to be remapped Will Deacon
2021-03-18 18:06 ` Vincenzo Frascino [this message]
2021-03-18 17:07 ` [PATCH 4/5] arm64: vdso: Avoid ISB after reading from cntvct_el0 Will Deacon
2021-03-18 18:08 ` Vincenzo Frascino
2021-03-18 17:07 ` [PATCH 5/5] arm64: compat: Poison the compat sigpage Will Deacon
2021-03-18 18:13 ` Vincenzo Frascino
2021-03-24 16:58 ` [PATCH 0/5] Minor improvements to the compat vdso and sigpage 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=b52b6e22-c3d3-ed74-4c5f-d59f1a986589@arm.com \
--to=vincenzo.frascino@arm.com \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=will@kernel.org \
/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).