From: patchwork-bot+linux-riscv@kernel.org
To: Lukas Gerlach <lukas.gerlach@cispa.de>
Cc: linux-riscv@lists.infradead.org, anup@brainfault.org,
atish.patra@linux.dev, pjw@kernel.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr, ajones@ventanamicro.com,
radim.krcmar@oss.qualcomm.com, kvm@vger.kernel.org,
kvm-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
daniel.weber@cispa.de, michael.schwarz@cispa.de,
marton.bognar@kuleuven.be, jo.vanbulck@kuleuven.be
Subject: Re: [PATCH v2 0/4] KVM: riscv: Fix Spectre-v1 vulnerabilities in register access
Date: Tue, 24 Mar 2026 06:07:30 +0000 [thread overview]
Message-ID: <177433245028.469836.11061694721898939145.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260303-kvm-riscv-spectre-v1-v2-0-192caab8e0dc@cispa.de>
Hello:
This series was applied to riscv/linux.git (for-next)
by Anup Patel <anup@brainfault.org>:
On Tue, 3 Mar 2026 15:19:40 +0100 you wrote:
> This series adds array_index_nospec() to RISC-V KVM to prevent
> speculative out-of-bounds access to kernel memory.
>
> Similar fixes exist for x86 (ioapic, lapic, PMU) and arm64 (vgic).
>
> Signed-off-by: Lukas Gerlach <lukas.gerlach@cispa.de>
>
> [...]
Here is the summary with links:
- [v2,1/4] KVM: riscv: Fix Spectre-v1 in ONE_REG register access
https://git.kernel.org/riscv/c/f9e26fc32541
- [v2,2/4] KVM: riscv: Fix Spectre-v1 in AIA CSR access
https://git.kernel.org/riscv/c/ec87a82ca874
- [v2,3/4] KVM: riscv: Fix Spectre-v1 in floating-point register access
https://git.kernel.org/riscv/c/8f0c15c4b14f
- [v2,4/4] KVM: riscv: Fix Spectre-v1 in PMU counter access
https://git.kernel.org/riscv/c/2dda6a9e09ee
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
--
kvm-riscv mailing list
kvm-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kvm-riscv
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Lukas Gerlach <lukas.gerlach@cispa.de>
Cc: linux-riscv@lists.infradead.org, anup@brainfault.org,
atish.patra@linux.dev, pjw@kernel.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr, ajones@ventanamicro.com,
radim.krcmar@oss.qualcomm.com, kvm@vger.kernel.org,
kvm-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
daniel.weber@cispa.de, michael.schwarz@cispa.de,
marton.bognar@kuleuven.be, jo.vanbulck@kuleuven.be
Subject: Re: [PATCH v2 0/4] KVM: riscv: Fix Spectre-v1 vulnerabilities in register access
Date: Tue, 24 Mar 2026 06:07:30 +0000 [thread overview]
Message-ID: <177433245028.469836.11061694721898939145.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260303-kvm-riscv-spectre-v1-v2-0-192caab8e0dc@cispa.de>
Hello:
This series was applied to riscv/linux.git (for-next)
by Anup Patel <anup@brainfault.org>:
On Tue, 3 Mar 2026 15:19:40 +0100 you wrote:
> This series adds array_index_nospec() to RISC-V KVM to prevent
> speculative out-of-bounds access to kernel memory.
>
> Similar fixes exist for x86 (ioapic, lapic, PMU) and arm64 (vgic).
>
> Signed-off-by: Lukas Gerlach <lukas.gerlach@cispa.de>
>
> [...]
Here is the summary with links:
- [v2,1/4] KVM: riscv: Fix Spectre-v1 in ONE_REG register access
https://git.kernel.org/riscv/c/f9e26fc32541
- [v2,2/4] KVM: riscv: Fix Spectre-v1 in AIA CSR access
https://git.kernel.org/riscv/c/ec87a82ca874
- [v2,3/4] KVM: riscv: Fix Spectre-v1 in floating-point register access
https://git.kernel.org/riscv/c/8f0c15c4b14f
- [v2,4/4] KVM: riscv: Fix Spectre-v1 in PMU counter access
https://git.kernel.org/riscv/c/2dda6a9e09ee
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Lukas Gerlach <lukas.gerlach@cispa.de>
Cc: linux-riscv@lists.infradead.org, anup@brainfault.org,
atish.patra@linux.dev, pjw@kernel.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr, ajones@ventanamicro.com,
radim.krcmar@oss.qualcomm.com, kvm@vger.kernel.org,
kvm-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
daniel.weber@cispa.de, michael.schwarz@cispa.de,
marton.bognar@kuleuven.be, jo.vanbulck@kuleuven.be
Subject: Re: [PATCH v2 0/4] KVM: riscv: Fix Spectre-v1 vulnerabilities in register access
Date: Tue, 24 Mar 2026 06:07:30 +0000 [thread overview]
Message-ID: <177433245028.469836.11061694721898939145.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260303-kvm-riscv-spectre-v1-v2-0-192caab8e0dc@cispa.de>
Hello:
This series was applied to riscv/linux.git (for-next)
by Anup Patel <anup@brainfault.org>:
On Tue, 3 Mar 2026 15:19:40 +0100 you wrote:
> This series adds array_index_nospec() to RISC-V KVM to prevent
> speculative out-of-bounds access to kernel memory.
>
> Similar fixes exist for x86 (ioapic, lapic, PMU) and arm64 (vgic).
>
> Signed-off-by: Lukas Gerlach <lukas.gerlach@cispa.de>
>
> [...]
Here is the summary with links:
- [v2,1/4] KVM: riscv: Fix Spectre-v1 in ONE_REG register access
https://git.kernel.org/riscv/c/f9e26fc32541
- [v2,2/4] KVM: riscv: Fix Spectre-v1 in AIA CSR access
https://git.kernel.org/riscv/c/ec87a82ca874
- [v2,3/4] KVM: riscv: Fix Spectre-v1 in floating-point register access
https://git.kernel.org/riscv/c/8f0c15c4b14f
- [v2,4/4] KVM: riscv: Fix Spectre-v1 in PMU counter access
https://git.kernel.org/riscv/c/2dda6a9e09ee
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-03-24 6:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 14:19 [PATCH v2 0/4] KVM: riscv: Fix Spectre-v1 vulnerabilities in register access Lukas Gerlach
2026-03-03 14:19 ` Lukas Gerlach
2026-03-03 14:19 ` Lukas Gerlach
2026-03-03 14:19 ` [PATCH v2 1/4] KVM: riscv: Fix Spectre-v1 in ONE_REG " Lukas Gerlach
2026-03-03 14:19 ` Lukas Gerlach
2026-03-03 14:19 ` Lukas Gerlach
2026-03-03 14:19 ` [PATCH v2 2/4] KVM: riscv: Fix Spectre-v1 in AIA CSR access Lukas Gerlach
2026-03-03 14:19 ` Lukas Gerlach
2026-03-03 14:19 ` Lukas Gerlach
2026-03-03 14:19 ` [PATCH v2 3/4] KVM: riscv: Fix Spectre-v1 in floating-point register access Lukas Gerlach
2026-03-03 14:19 ` Lukas Gerlach
2026-03-03 14:19 ` Lukas Gerlach
2026-03-03 14:19 ` [PATCH v2 4/4] KVM: riscv: Fix Spectre-v1 in PMU counter access Lukas Gerlach
2026-03-03 14:19 ` Lukas Gerlach
2026-03-03 14:19 ` Lukas Gerlach
2026-03-04 11:08 ` [PATCH v2 0/4] KVM: riscv: Fix Spectre-v1 vulnerabilities in register access Anup Patel
2026-03-04 11:08 ` Anup Patel
2026-03-04 11:08 ` Anup Patel
2026-03-24 6:07 ` patchwork-bot+linux-riscv [this message]
2026-03-24 6:07 ` patchwork-bot+linux-riscv
2026-03-24 6:07 ` patchwork-bot+linux-riscv
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=177433245028.469836.11061694721898939145.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@linux.dev \
--cc=daniel.weber@cispa.de \
--cc=jo.vanbulck@kuleuven.be \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lukas.gerlach@cispa.de \
--cc=marton.bognar@kuleuven.be \
--cc=michael.schwarz@cispa.de \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=radim.krcmar@oss.qualcomm.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.