All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Oliver Upton <oliver.upton@linux.dev>,
	kvm@vger.kernel.org, kvmarm@lists.linux.dev,
	James Morse <james.morse@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Zenghui Yu <yuzenghui@huawei.com>, Will Deacon <will@kernel.org>,
	Mostafa Saleh <smostafa@google.com>,
	Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [GIT PULL v2] KVM/arm64 fixes for 6.3, part #4
Date: Sat, 22 Apr 2023 10:05:38 +0100	[thread overview]
Message-ID: <1023162f05aac3b460effa4a7baa0760@kernel.org> (raw)
In-Reply-To: <417f815d-3cf1-45ea-eba7-83e42f249424@redhat.com>

On 2023-04-22 00:51, Paolo Bonzini wrote:
> On 4/19/23 17:54, Oliver Upton wrote:
>> Hi Paolo,
>> 
>> Here is v2 of the last batch of fixes for 6.3 (for real this time!)
>> 
>> Details in the tag, but the noteworthy addition is Dan's fix for a
>> rather obvious buffer overflow when writing to a firmware register.
> 
> At least going by the Fixes tag, I think this one should have been
> Cc'd to stable as well.  Can you send it next week or would you like
> someone else to handle the backport?

Indeed, that's missing. But yes, backports are definitely on
the cards, and we'll make sure all stable versions get fixed
as soon as the fix hits Linus' tree.

         M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2023-04-22  9:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19 15:54 [GIT PULL v2] KVM/arm64 fixes for 6.3, part #4 Oliver Upton
2023-04-21 23:19 ` Paolo Bonzini
2023-04-21 23:51 ` Paolo Bonzini
2023-04-22  9:05   ` Marc Zyngier [this message]
2023-04-22 18:35     ` Oliver Upton
2023-04-23  9:08       ` 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=1023162f05aac3b460effa4a7baa0760@kernel.org \
    --to=maz@kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=james.morse@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=oliver.upton@linux.dev \
    --cc=pbonzini@redhat.com \
    --cc=smostafa@google.com \
    --cc=suzuki.poulose@arm.com \
    --cc=will@kernel.org \
    --cc=yuzenghui@huawei.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.