From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
Anshuman Khandual <anshuman.khandual@arm.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org, James Morse <james.morse@arm.com>
Subject: Re: [PATCH] arm64/mm: Fix ttbr0 values stored in struct thread_info for software-pan
Date: Tue, 15 Jun 2021 20:18:21 +0100 [thread overview]
Message-ID: <162378020482.22871.14339302272957309916.b4-ty@kernel.org> (raw)
In-Reply-To: <1623749578-11231-1-git-send-email-anshuman.khandual@arm.com>
On Tue, 15 Jun 2021 15:02:58 +0530, Anshuman Khandual wrote:
> When using CONFIG_ARM64_SW_TTBR0_PAN, a task's thread_info::ttbr0 must be
> the TTBR0_EL1 value used to run userspace. With 52-bit PAs, the PA must be
> packed into the TTBR using phys_to_ttbr(), but we forget to do this in some
> of the SW PAN code. Thus, if the value is installed into TTBR0_EL1 (as may
> happen in the uaccess routines), this could result in UNPREDICTABLE
> behaviour.
>
> [...]
Applied to arm64 (for-next/mm), thanks!
[1/1] arm64/mm: Fix ttbr0 values stored in struct thread_info for software-pan
https://git.kernel.org/arm64/c/9163f0113030
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
Anshuman Khandual <anshuman.khandual@arm.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org, James Morse <james.morse@arm.com>
Subject: Re: [PATCH] arm64/mm: Fix ttbr0 values stored in struct thread_info for software-pan
Date: Tue, 15 Jun 2021 20:18:21 +0100 [thread overview]
Message-ID: <162378020482.22871.14339302272957309916.b4-ty@kernel.org> (raw)
In-Reply-To: <1623749578-11231-1-git-send-email-anshuman.khandual@arm.com>
On Tue, 15 Jun 2021 15:02:58 +0530, Anshuman Khandual wrote:
> When using CONFIG_ARM64_SW_TTBR0_PAN, a task's thread_info::ttbr0 must be
> the TTBR0_EL1 value used to run userspace. With 52-bit PAs, the PA must be
> packed into the TTBR using phys_to_ttbr(), but we forget to do this in some
> of the SW PAN code. Thus, if the value is installed into TTBR0_EL1 (as may
> happen in the uaccess routines), this could result in UNPREDICTABLE
> behaviour.
>
> [...]
Applied to arm64 (for-next/mm), thanks!
[1/1] arm64/mm: Fix ttbr0 values stored in struct thread_info for software-pan
https://git.kernel.org/arm64/c/9163f0113030
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
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-06-15 19:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 9:32 [PATCH] arm64/mm: Fix ttbr0 values stored in struct thread_info for software-pan Anshuman Khandual
2021-06-15 9:32 ` Anshuman Khandual
2021-06-15 14:25 ` Catalin Marinas
2021-06-15 14:25 ` Catalin Marinas
2021-06-15 14:26 ` Will Deacon
2021-06-15 14:26 ` Will Deacon
2021-06-15 19:18 ` Will Deacon [this message]
2021-06-15 19:18 ` Will Deacon
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=162378020482.22871.14339302272957309916.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@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 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.