From: Marc Zyngier <maz@kernel.org>
To: Ryan Roberts <ryan.roberts@arm.com>
Cc: Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
kvmarm@lists.linux.dev, kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1] KVM: arm64: Fix benign bug with incorrect use of VA_BITS.
Date: Mon, 05 Dec 2022 13:49:22 +0000 [thread overview]
Message-ID: <86y1rmkljx.wl-maz@kernel.org> (raw)
In-Reply-To: <20221205114031.3972780-1-ryan.roberts@arm.com>
Hi Ryan,
Thanks for that.
On Mon, 05 Dec 2022 11:40:31 +0000,
Ryan Roberts <ryan.roberts@arm.com> wrote:
>
> get_user_mapping_size() uses kvm's pgtable library to walk a user space
> page table created by the kernel, and in doing so, fakes up the metadata
> that the library needs, including ia_bits, which defines the size of the
> input address.
It isn't supposed to "fake" anything. It simply provides the
information that the walker needs to correctly parse the page tables.
>
> For the case where the kernel is compiled for 52 VA bits but runs on HW
> that does not support LVA, it will fall back to 48 VA bits at runtime.
> Therefore we must use vabits_actual rather than VA_BITS to get the true
> address size.
>
> This is benign in the current code base because the pgtable library only
> uses it for error checking.
>
> Fixes: 6011cf68c885 ("KVM: arm64: Walk userspace page tables to compute
> the THP mapping size")
nit: this should appear on a single line, without a line-break in the
middle [1]...
>
... without a blank line between Fixes: and the rest of the tags.
And while I'm on the "trivial remarks" train, drop the full stop at
the end of the subject line.
> Signed-off-by: Ryan Roberts <ryan.roberts@arm.com>
> ---
> arch/arm64/kvm/mmu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/kvm/mmu.c b/arch/arm64/kvm/mmu.c
> index 4efb983cff43..1ef0704420d9 100644
> --- a/arch/arm64/kvm/mmu.c
> +++ b/arch/arm64/kvm/mmu.c
> @@ -641,7 +641,7 @@ static int get_user_mapping_size(struct kvm *kvm, u64 addr)
> {
> struct kvm_pgtable pgt = {
> .pgd = (kvm_pte_t *)kvm->mm->pgd,
> - .ia_bits = VA_BITS,
> + .ia_bits = vabits_actual,
> .start_level = (KVM_PGTABLE_MAX_LEVELS -
> CONFIG_PGTABLE_LEVELS),
> .mm_ops = &kvm_user_mm_ops,
> --
> 2.25.1
>
>
Other than the above nits, this is well spotted. I need to regenerate
the kvmarm/next branch after the sysreg attack from James, so I'll try
and fold that in.
Thanks,
M.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst#n139
--
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Ryan Roberts <ryan.roberts@arm.com>
Cc: James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH v1] KVM: arm64: Fix benign bug with incorrect use of VA_BITS.
Date: Mon, 05 Dec 2022 13:49:22 +0000 [thread overview]
Message-ID: <86y1rmkljx.wl-maz@kernel.org> (raw)
Message-ID: <20221205134922.A9G2pTilfPwjsbfy-g_KY6nX3we3jmPh6p0cDhFbqfs@z> (raw)
In-Reply-To: <20221205114031.3972780-1-ryan.roberts@arm.com>
Hi Ryan,
Thanks for that.
On Mon, 05 Dec 2022 11:40:31 +0000,
Ryan Roberts <ryan.roberts@arm.com> wrote:
>
> get_user_mapping_size() uses kvm's pgtable library to walk a user space
> page table created by the kernel, and in doing so, fakes up the metadata
> that the library needs, including ia_bits, which defines the size of the
> input address.
It isn't supposed to "fake" anything. It simply provides the
information that the walker needs to correctly parse the page tables.
>
> For the case where the kernel is compiled for 52 VA bits but runs on HW
> that does not support LVA, it will fall back to 48 VA bits at runtime.
> Therefore we must use vabits_actual rather than VA_BITS to get the true
> address size.
>
> This is benign in the current code base because the pgtable library only
> uses it for error checking.
>
> Fixes: 6011cf68c885 ("KVM: arm64: Walk userspace page tables to compute
> the THP mapping size")
nit: this should appear on a single line, without a line-break in the
middle [1]...
>
... without a blank line between Fixes: and the rest of the tags.
And while I'm on the "trivial remarks" train, drop the full stop at
the end of the subject line.
> Signed-off-by: Ryan Roberts <ryan.roberts@arm.com>
> ---
> arch/arm64/kvm/mmu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/kvm/mmu.c b/arch/arm64/kvm/mmu.c
> index 4efb983cff43..1ef0704420d9 100644
> --- a/arch/arm64/kvm/mmu.c
> +++ b/arch/arm64/kvm/mmu.c
> @@ -641,7 +641,7 @@ static int get_user_mapping_size(struct kvm *kvm, u64 addr)
> {
> struct kvm_pgtable pgt = {
> .pgd = (kvm_pte_t *)kvm->mm->pgd,
> - .ia_bits = VA_BITS,
> + .ia_bits = vabits_actual,
> .start_level = (KVM_PGTABLE_MAX_LEVELS -
> CONFIG_PGTABLE_LEVELS),
> .mm_ops = &kvm_user_mm_ops,
> --
> 2.25.1
>
>
Other than the above nits, this is well spotted. I need to regenerate
the kvmarm/next branch after the sysreg attack from James, so I'll try
and fold that in.
Thanks,
M.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst#n139
--
Without deviation from the norm, progress is not possible.
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Ryan Roberts <ryan.roberts@arm.com>
Cc: James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH v1] KVM: arm64: Fix benign bug with incorrect use of VA_BITS.
Date: Mon, 05 Dec 2022 13:49:22 +0000 [thread overview]
Message-ID: <86y1rmkljx.wl-maz@kernel.org> (raw)
In-Reply-To: <20221205114031.3972780-1-ryan.roberts@arm.com>
Hi Ryan,
Thanks for that.
On Mon, 05 Dec 2022 11:40:31 +0000,
Ryan Roberts <ryan.roberts@arm.com> wrote:
>
> get_user_mapping_size() uses kvm's pgtable library to walk a user space
> page table created by the kernel, and in doing so, fakes up the metadata
> that the library needs, including ia_bits, which defines the size of the
> input address.
It isn't supposed to "fake" anything. It simply provides the
information that the walker needs to correctly parse the page tables.
>
> For the case where the kernel is compiled for 52 VA bits but runs on HW
> that does not support LVA, it will fall back to 48 VA bits at runtime.
> Therefore we must use vabits_actual rather than VA_BITS to get the true
> address size.
>
> This is benign in the current code base because the pgtable library only
> uses it for error checking.
>
> Fixes: 6011cf68c885 ("KVM: arm64: Walk userspace page tables to compute
> the THP mapping size")
nit: this should appear on a single line, without a line-break in the
middle [1]...
>
... without a blank line between Fixes: and the rest of the tags.
And while I'm on the "trivial remarks" train, drop the full stop at
the end of the subject line.
> Signed-off-by: Ryan Roberts <ryan.roberts@arm.com>
> ---
> arch/arm64/kvm/mmu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/kvm/mmu.c b/arch/arm64/kvm/mmu.c
> index 4efb983cff43..1ef0704420d9 100644
> --- a/arch/arm64/kvm/mmu.c
> +++ b/arch/arm64/kvm/mmu.c
> @@ -641,7 +641,7 @@ static int get_user_mapping_size(struct kvm *kvm, u64 addr)
> {
> struct kvm_pgtable pgt = {
> .pgd = (kvm_pte_t *)kvm->mm->pgd,
> - .ia_bits = VA_BITS,
> + .ia_bits = vabits_actual,
> .start_level = (KVM_PGTABLE_MAX_LEVELS -
> CONFIG_PGTABLE_LEVELS),
> .mm_ops = &kvm_user_mm_ops,
> --
> 2.25.1
>
>
Other than the above nits, this is well spotted. I need to regenerate
the kvmarm/next branch after the sysreg attack from James, so I'll try
and fold that in.
Thanks,
M.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst#n139
--
Without deviation from the norm, progress is not possible.
_______________________________________________
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:[~2022-12-05 13:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 11:40 [PATCH v1] KVM: arm64: Fix benign bug with incorrect use of VA_BITS Ryan Roberts
2022-12-05 11:40 ` Ryan Roberts
2022-12-05 11:40 ` Ryan Roberts
2022-12-05 13:49 ` Marc Zyngier [this message]
2022-12-05 13:49 ` Marc Zyngier
2022-12-05 13:49 ` Marc Zyngier
2022-12-05 14:06 ` Ryan Roberts
2022-12-05 14:06 ` Ryan Roberts
2022-12-05 14:06 ` Ryan Roberts
2022-12-05 14:42 ` Marc Zyngier
2022-12-05 14:42 ` Marc Zyngier
2022-12-05 14:42 ` Marc Zyngier
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=86y1rmkljx.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=ryan.roberts@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.