From: Paolo Bonzini <pbonzini@redhat.com>
To: David Stevens <stevensd@chromium.org>, Marc Zyngier <maz@kernel.org>
Cc: James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Will Deacon <will@kernel.org>,
Sean Christopherson <seanjc@google.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu,
open list <linux-kernel@vger.kernel.org>,
kvm@vger.kernel.org
Subject: Re: [PATCH v3 0/4] KVM: allow mapping non-refcounted pages
Date: Tue, 21 Sep 2021 12:27:54 +0200 [thread overview]
Message-ID: <7c9cf3aa-7edc-4f02-b7cd-4c3d4950beae@redhat.com> (raw)
In-Reply-To: <CAD=HUj6_CFE0ZjexVMQMansmVcFRm3-udG=_12ROKfWDroNt-g@mail.gmail.com>
On 21/09/21 08:27, David Stevens wrote:
> Is there any feedback on these patches? CVE-2021-22543 was fixed by
> disallowing mapping of non-refcounted memory. These patches add proper
> support for mapping that type of memory.
Sorry, I was busy the past few weeks and I'm now back to KVM work.
Paolo
next prev parent reply other threads:[~2021-09-21 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 2:50 [PATCH v3 0/4] KVM: allow mapping non-refcounted pages David Stevens
2021-08-25 2:50 ` [PATCH v3 1/4] KVM: mmu: introduce new gfn_to_pfn_page functions David Stevens
2021-08-25 2:50 ` [PATCH v3 2/4] KVM: x86/mmu: use gfn_to_pfn_page David Stevens
2021-08-25 2:50 ` [PATCH v3 3/4] KVM: arm64/mmu: " David Stevens
2021-08-25 2:50 ` [PATCH v3 4/4] KVM: mmu: remove over-aggressive warnings David Stevens
2021-09-21 6:27 ` [PATCH v3 0/4] KVM: allow mapping non-refcounted pages David Stevens
2021-09-21 10:27 ` Paolo Bonzini [this message]
2021-09-28 17:40 ` Paolo Bonzini
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=7c9cf3aa-7edc-4f02-b7cd-4c3d4950beae@redhat.com \
--to=pbonzini@redhat.com \
--cc=alexandru.elisei@arm.com \
--cc=james.morse@arm.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=seanjc@google.com \
--cc=stevensd@chromium.org \
--cc=suzuki.poulose@arm.com \
--cc=wanpengli@tencent.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox