From: Marc Zyngier <maz@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
Zenghui Yu <yuzenghui@huawei.com>,
kvmarm@lists.linux.dev, kvm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] KVM/arm64 fixes for 6.8, take #3
Date: Wed, 21 Feb 2024 10:34:20 +0000 [thread overview]
Message-ID: <86ttm22jir.wl-maz@kernel.org> (raw)
In-Reply-To: <CABgObfYhVK+qF25h8+hhuyCvbgfpocDo0UDac3CTEHghRGww+w@mail.gmail.com>
On Wed, 21 Feb 2024 10:22:04 +0000,
Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> On Wed, Feb 21, 2024 at 11:17 AM Marc Zyngier <maz@kernel.org> wrote:
> >
> > Hey Paolo,
> >
> > Another week, another couple of fixes. This time, two fixes for the
> > ITS emulation that could result in non-existent LPIs being used, with
> > unpredictable consequences. Thanks to Oliver for spotting those as he
> > was reworking the ITS translation cache.
>
> The consequences would really be NULL pointer dereferences, wouldn't they?
That's the effect. The consequences depend on how the fault is
handled ('benign' oops, panic, or reboot...).
Thanks,
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: Paolo Bonzini <pbonzini@redhat.com>
Cc: James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
Zenghui Yu <yuzenghui@huawei.com>,
kvmarm@lists.linux.dev, kvm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] KVM/arm64 fixes for 6.8, take #3
Date: Wed, 21 Feb 2024 10:34:20 +0000 [thread overview]
Message-ID: <86ttm22jir.wl-maz@kernel.org> (raw)
In-Reply-To: <CABgObfYhVK+qF25h8+hhuyCvbgfpocDo0UDac3CTEHghRGww+w@mail.gmail.com>
On Wed, 21 Feb 2024 10:22:04 +0000,
Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> On Wed, Feb 21, 2024 at 11:17 AM Marc Zyngier <maz@kernel.org> wrote:
> >
> > Hey Paolo,
> >
> > Another week, another couple of fixes. This time, two fixes for the
> > ITS emulation that could result in non-existent LPIs being used, with
> > unpredictable consequences. Thanks to Oliver for spotting those as he
> > was reworking the ITS translation cache.
>
> The consequences would really be NULL pointer dereferences, wouldn't they?
That's the effect. The consequences depend on how the fault is
handled ('benign' oops, panic, or reboot...).
Thanks,
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
next prev parent reply other threads:[~2024-02-21 10:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 10:17 [GIT PULL] KVM/arm64 fixes for 6.8, take #3 Marc Zyngier
2024-02-21 10:17 ` Marc Zyngier
2024-02-21 10:22 ` Paolo Bonzini
2024-02-21 10:22 ` Paolo Bonzini
2024-02-21 10:34 ` Marc Zyngier [this message]
2024-02-21 10:34 ` 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=86ttm22jir.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=suzuki.poulose@arm.com \
--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.