From: Catalin Marinas <catalin.marinas@arm.com>
To: Pingfan Liu <kernelfans@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 1/2] arm64: uaccess: disable preempt during uaccess through ttbr0
Date: Wed, 22 Dec 2021 12:59:32 +0000 [thread overview]
Message-ID: <YcMhNFC0XgiCF1ki@arm.com> (raw)
In-Reply-To: <20211221134242.98877-1-kernelfans@gmail.com>
On Tue, Dec 21, 2021 at 09:42:41PM +0800, Pingfan Liu wrote:
> If using software PAN, the ttbr0 should keep unchanged, otherwise,
> considering the following scenario:
> task1
> __uaccess_ttbr0_enable()
> switch_mm(this,next,tsk), which resets ttbr0 to __pa_symbol(reserved_pg_dir)
> switch_mm(prev,this,tsk), which can not re-install the user page table automatically
Have you found a real problem with this in practice or just by code
inspection?
The assumption is that during uaccess_ttbr0_enable/disable regions, the
only way to get into switch_mm() is as a result of a page fault or
interrupt. The __swpan_{entry,exit}_el1 functions should take care of
restoring ttbr0 when returning to the interrupted context.
> Tackle this issue by disabling preemption.
>
> Signed-off-by: Pingfan Liu <kernelfans@gmail.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Vincenzo Frascino <vincenzo.frascino@arm.com>
> Cc: Andrey Konovalov <andreyknvl@gmail.com>
> Cc: Arnd Bergmann <arnd@arndb.de>
> To: linux-arm-kernel@lists.infradead.org
> ---
> arch/arm64/include/asm/uaccess.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm64/include/asm/uaccess.h b/arch/arm64/include/asm/uaccess.h
> index 3a5ff5e20586..406888877bbd 100644
> --- a/arch/arm64/include/asm/uaccess.h
> +++ b/arch/arm64/include/asm/uaccess.h
> @@ -121,6 +121,7 @@ static inline bool uaccess_ttbr0_disable(void)
> if (!system_uses_ttbr0_pan())
> return false;
> __uaccess_ttbr0_disable();
> + preempt_enable();
> return true;
> }
>
> @@ -128,6 +129,7 @@ static inline bool uaccess_ttbr0_enable(void)
> {
> if (!system_uses_ttbr0_pan())
> return false;
> + preempt_disable();
> __uaccess_ttbr0_enable();
> return true;
> }
preempt_disable() won't help much here if, for example, the subsequent
uaccess gets a fault and need to sleep until the accessed page gets
available. I suspect you'd get some sleeping in atomic warning as well
with the right debug options enabled.
--
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:[~2021-12-22 13:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 13:42 [PATCH 1/2] arm64: uaccess: disable preempt during uaccess through ttbr0 Pingfan Liu
2021-12-21 13:42 ` [PATCH 2/2] arm64: uaccess: disable preempt during uaccess PSTATE.{PAN, TCO} Pingfan Liu
2021-12-22 13:02 ` [PATCH 2/2] arm64: uaccess: disable preempt during uaccess PSTATE.{PAN,TCO} Catalin Marinas
2021-12-23 9:39 ` Pingfan Liu
2021-12-22 12:59 ` Catalin Marinas [this message]
2021-12-23 9:36 ` [PATCH 1/2] arm64: uaccess: disable preempt during uaccess through ttbr0 Pingfan Liu
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=YcMhNFC0XgiCF1ki@arm.com \
--to=catalin.marinas@arm.com \
--cc=andreyknvl@gmail.com \
--cc=arnd@arndb.de \
--cc=kernelfans@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=vincenzo.frascino@arm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.