From: Paul Walmsley <pjw@kernel.org>
To: Lukas Gerlach <lukas.gerlach@cispa.de>
Cc: patchwork-bot+linux-riscv@kernel.org,
linux-riscv@lists.infradead.org, palmer@dabbelt.com,
pjw@kernel.org, aou@eecs.berkeley.edu, alex@ghiti.fr,
linux-kernel@vger.kernel.org, daniel.weber@cispa.de,
michael.schwarz@cispa.de, marton.bognar@kuleuven.be,
jo.vanbulck@kuleuven.be
Subject: Re: [PATCH 0/2] riscv: Add Spectre v1 mitigations
Date: Mon, 5 Jan 2026 16:17:22 -0700 (MST) [thread overview]
Message-ID: <6f196be2-3d56-75f5-78d8-800138a8ba46@kernel.org> (raw)
In-Reply-To: <176715189629.3416240.5165553541798344765.git-patchwork-notify@kernel.org>
On Wed, 31 Dec 2025, patchwork-bot+linux-riscv@kernel.org wrote:
> This series was applied to riscv/linux.git (fixes)
> by Paul Walmsley <pjw@kernel.org>:
>
> On Thu, 18 Dec 2025 20:13:30 +0100 you wrote:
> > This series adds Spectre v1 to RISC-V in line with x86 and arm64.
.
> > [...]
>
> Here is the summary with links:
> - [1/2] riscv: Use pointer masking to limit uaccess speculation
> (no matching commit)
> - [2/2] riscv: Sanitize syscall table indexing under speculation
> https://git.kernel.org/riscv/c/25fd7ee7bf58
Just to be clear, I only picked up the syscall table indexing patch, not
the address masking patch. Am still waiting for an update for that one.
- Paul
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-01-05 23:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 19:13 [PATCH 0/2] riscv: Add Spectre v1 mitigations Lukas Gerlach
2025-12-18 19:13 ` [PATCH 1/2] riscv: Use pointer masking to limit uaccess speculation Lukas Gerlach
2025-12-20 0:44 ` Deepak Gupta
2025-12-27 12:57 ` Lukas Gerlach
2025-12-28 0:41 ` Deepak Gupta
2025-12-27 21:28 ` David Laight
2025-12-28 1:59 ` Deepak Gupta
2025-12-28 22:34 ` David Laight
2025-12-29 12:32 ` David Laight
2025-12-31 3:47 ` Vivian Wang
2025-12-31 10:35 ` David Laight
2025-12-18 19:13 ` [PATCH 2/2] riscv: Sanitize syscall table indexing under speculation Lukas Gerlach
2025-12-31 3:01 ` Paul Walmsley
2025-12-31 3:31 ` [PATCH 0/2] riscv: Add Spectre v1 mitigations patchwork-bot+linux-riscv
2026-01-05 23:17 ` Paul Walmsley [this message]
2026-01-06 10:30 ` [PATCH 1/2] riscv: Use pointer masking to limit uaccess speculation Lukas Gerlach
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=6f196be2-3d56-75f5-78d8-800138a8ba46@kernel.org \
--to=pjw@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=daniel.weber@cispa.de \
--cc=jo.vanbulck@kuleuven.be \
--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=patchwork-bot+linux-riscv@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