From: Will Deacon <will.deacon@arm.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: marc.zyngier@arm.com, catalin.marinas@arm.com, cdall@kernel.org,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH 0/3] arm64/kvm spectre-v1 fixes
Date: Thu, 26 Apr 2018 16:58:03 +0100 [thread overview]
Message-ID: <20180426155803.GA898@arm.com> (raw)
In-Reply-To: <20180425161342.38133-1-mark.rutland@arm.com>
On Wed, Apr 25, 2018 at 05:13:39PM +0100, Mark Rutland wrote:
> These patches fix arm64-specific potential spectre-v1 gadgets found by
> smatch when run over v4.17-rc2.
>
> I'm still building up my smatch database, so it's possible that there are
> further gadgets to be found.
>
> For the moment I've ignored issues which appear to be cross-architecture.
>
> Thanks,
> Mark.
>
> Mark Rutland (3):
> arm64: fix possible spectre-v1 in ptrace_hbp_get_event()
> KVM: arm/arm64: vgic: fix possible spectre-v1 in vgic_get_irq()
> KVM: arm/arm64: vgic: fix possible spectre-v1 in vgic_mmio_read_apr()
Thanks, I'll pick these up as fixes with Christoffer and Marc's acks on the
kvm parts.
Will
WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] arm64/kvm spectre-v1 fixes
Date: Thu, 26 Apr 2018 16:58:03 +0100 [thread overview]
Message-ID: <20180426155803.GA898@arm.com> (raw)
In-Reply-To: <20180425161342.38133-1-mark.rutland@arm.com>
On Wed, Apr 25, 2018 at 05:13:39PM +0100, Mark Rutland wrote:
> These patches fix arm64-specific potential spectre-v1 gadgets found by
> smatch when run over v4.17-rc2.
>
> I'm still building up my smatch database, so it's possible that there are
> further gadgets to be found.
>
> For the moment I've ignored issues which appear to be cross-architecture.
>
> Thanks,
> Mark.
>
> Mark Rutland (3):
> arm64: fix possible spectre-v1 in ptrace_hbp_get_event()
> KVM: arm/arm64: vgic: fix possible spectre-v1 in vgic_get_irq()
> KVM: arm/arm64: vgic: fix possible spectre-v1 in vgic_mmio_read_apr()
Thanks, I'll pick these up as fixes with Christoffer and Marc's acks on the
kvm parts.
Will
next prev parent reply other threads:[~2018-04-26 15:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 16:13 [PATCH 0/3] arm64/kvm spectre-v1 fixes Mark Rutland
2018-04-25 16:13 ` Mark Rutland
2018-04-25 16:13 ` [PATCH 1/3] arm64: fix possible spectre-v1 in ptrace_hbp_get_event() Mark Rutland
2018-04-25 16:13 ` Mark Rutland
2018-04-25 16:13 ` [PATCH 2/3] KVM: arm/arm64: vgic: fix possible spectre-v1 in vgic_get_irq() Mark Rutland
2018-04-25 16:13 ` Mark Rutland
2018-04-25 16:13 ` [PATCH 3/3] KVM: arm/arm64: vgic: fix possible spectre-v1 in vgic_mmio_read_apr() Mark Rutland
2018-04-25 16:13 ` Mark Rutland
2018-04-26 10:37 ` [PATCH 0/3] arm64/kvm spectre-v1 fixes Marc Zyngier
2018-04-26 10:37 ` Marc Zyngier
2018-04-26 14:10 ` Christoffer Dall
2018-04-26 14:10 ` Christoffer Dall
2018-04-26 15:58 ` Will Deacon [this message]
2018-04-26 15:58 ` Will Deacon
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=20180426155803.GA898@arm.com \
--to=will.deacon@arm.com \
--cc=catalin.marinas@arm.com \
--cc=cdall@kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.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.