All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu, Marc Zyngier <maz@kernel.org>,
	kvm@vger.kernel.org
Cc: Quentin Perret <qperret@google.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Will Deacon <will@kernel.org>,
	kernel-team@android.com, James Morse <james.morse@arm.com>,
	Alexandru Elisei <alexandru.elisei@arm.com>
Subject: Re: [PATCH v2 0/2] KVM: arm64: Prevent kmemleak from accessing HYP data
Date: Wed,  4 Aug 2021 13:26:37 +0100	[thread overview]
Message-ID: <162807998838.4077325.1915601762078271589.b4-ty@kernel.org> (raw)
In-Reply-To: <20210802123830.2195174-1-maz@kernel.org>

On Mon, 2 Aug 2021 13:38:28 +0100, Marc Zyngier wrote:
> This is a rework of the patch previously posted at [1].
> 
> The gist of the problem is that kmemleak can legitimately access data
> that has been removed from the kernel view, for two reasons:
> 
> (1) .hyp.rodata is lumped together with the BSS
> (2) there is no separation of the HYP BSS from the kernel BSS
> 
> [...]

Applied to next, thanks!

[1/2] arm64: Move .hyp.rodata outside of the _sdata.._edata range
      commit: eb48d154cd0dade56a0e244f0cfa198ea2925ed3
[2/2] KVM: arm64: Unregister HYP sections from kmemleak in protected mode
      commit: 47e6223c841e029bfc23c3ce594dac5525cebaf8

Cheers,

	M.
-- 
Without deviation from the norm, progress is not possible.



WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu, Marc Zyngier <maz@kernel.org>,
	kvm@vger.kernel.org
Cc: Will Deacon <will@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	kernel-team@android.com
Subject: Re: [PATCH v2 0/2] KVM: arm64: Prevent kmemleak from accessing HYP data
Date: Wed,  4 Aug 2021 13:26:37 +0100	[thread overview]
Message-ID: <162807998838.4077325.1915601762078271589.b4-ty@kernel.org> (raw)
In-Reply-To: <20210802123830.2195174-1-maz@kernel.org>

On Mon, 2 Aug 2021 13:38:28 +0100, Marc Zyngier wrote:
> This is a rework of the patch previously posted at [1].
> 
> The gist of the problem is that kmemleak can legitimately access data
> that has been removed from the kernel view, for two reasons:
> 
> (1) .hyp.rodata is lumped together with the BSS
> (2) there is no separation of the HYP BSS from the kernel BSS
> 
> [...]

Applied to next, thanks!

[1/2] arm64: Move .hyp.rodata outside of the _sdata.._edata range
      commit: eb48d154cd0dade56a0e244f0cfa198ea2925ed3
[2/2] KVM: arm64: Unregister HYP sections from kmemleak in protected mode
      commit: 47e6223c841e029bfc23c3ce594dac5525cebaf8

Cheers,

	M.
-- 
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: linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu, Marc Zyngier <maz@kernel.org>,
	kvm@vger.kernel.org
Cc: Quentin Perret <qperret@google.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Will Deacon <will@kernel.org>,
	kernel-team@android.com, James Morse <james.morse@arm.com>,
	Alexandru Elisei <alexandru.elisei@arm.com>
Subject: Re: [PATCH v2 0/2] KVM: arm64: Prevent kmemleak from accessing HYP data
Date: Wed,  4 Aug 2021 13:26:37 +0100	[thread overview]
Message-ID: <162807998838.4077325.1915601762078271589.b4-ty@kernel.org> (raw)
In-Reply-To: <20210802123830.2195174-1-maz@kernel.org>

On Mon, 2 Aug 2021 13:38:28 +0100, Marc Zyngier wrote:
> This is a rework of the patch previously posted at [1].
> 
> The gist of the problem is that kmemleak can legitimately access data
> that has been removed from the kernel view, for two reasons:
> 
> (1) .hyp.rodata is lumped together with the BSS
> (2) there is no separation of the HYP BSS from the kernel BSS
> 
> [...]

Applied to next, thanks!

[1/2] arm64: Move .hyp.rodata outside of the _sdata.._edata range
      commit: eb48d154cd0dade56a0e244f0cfa198ea2925ed3
[2/2] KVM: arm64: Unregister HYP sections from kmemleak in protected mode
      commit: 47e6223c841e029bfc23c3ce594dac5525cebaf8

Cheers,

	M.
-- 
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

  parent reply	other threads:[~2021-08-04 12:26 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02 12:38 [PATCH v2 0/2] KVM: arm64: Prevent kmemleak from accessing HYP data Marc Zyngier
2021-08-02 12:38 ` Marc Zyngier
2021-08-02 12:38 ` Marc Zyngier
2021-08-02 12:38 ` [PATCH v2 1/2] arm64: Move .hyp.rodata outside of the _sdata.._edata range Marc Zyngier
2021-08-02 12:38   ` Marc Zyngier
2021-08-02 12:38   ` Marc Zyngier
2021-08-02 13:11   ` Quentin Perret
2021-08-02 13:11     ` Quentin Perret
2021-08-02 13:11     ` Quentin Perret
2021-08-02 13:20     ` Marc Zyngier
2021-08-02 13:20       ` Marc Zyngier
2021-08-02 13:20       ` Marc Zyngier
2021-08-02 13:47       ` Quentin Perret
2021-08-02 13:47         ` Quentin Perret
2021-08-02 13:47         ` Quentin Perret
2021-08-02 16:52   ` Catalin Marinas
2021-08-02 16:52     ` Catalin Marinas
2021-08-02 16:52     ` Catalin Marinas
2021-08-02 12:38 ` [PATCH v2 2/2] KVM: arm64: Unregister HYP sections from kmemleak in protected mode Marc Zyngier
2021-08-02 12:38   ` Marc Zyngier
2021-08-02 12:38   ` Marc Zyngier
2021-08-02 16:52   ` Catalin Marinas
2021-08-02 16:52     ` Catalin Marinas
2021-08-02 16:52     ` Catalin Marinas
2021-08-04 12:26 ` Marc Zyngier [this message]
2021-08-04 12:26   ` [PATCH v2 0/2] KVM: arm64: Prevent kmemleak from accessing HYP data Marc Zyngier
2021-08-04 12:26   ` 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=162807998838.4077325.1915601762078271589.b4-ty@kernel.org \
    --to=maz@kernel.org \
    --cc=alexandru.elisei@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=james.morse@arm.com \
    --cc=kernel-team@android.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=qperret@google.com \
    --cc=suzuki.poulose@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.