From: Lukas Gerlach <lukas.gerlach@cispa.de>
To: <pjw@kernel.org>
Cc: <alex@ghiti.fr>, <aou@eecs.berkeley.edu>, <daniel.weber@cispa.de>,
<jo.vanbulck@kuleuven.be>, <linux-kernel@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, <lukas.gerlach@cispa.de>,
<marton.bognar@kuleuven.be>, <michael.schwarz@cispa.de>,
<palmer@dabbelt.com>, <patchwork-bot+linux-riscv@kernel.org>
Subject: Re: [PATCH 1/2] riscv: Use pointer masking to limit uaccess speculation
Date: Tue, 6 Jan 2026 11:30:10 +0100 [thread overview]
Message-ID: <20260106103010.5577-1-lukas.gerlach@cispa.de> (raw)
In-Reply-To: <6f196be2-3d56-75f5-78d8-800138a8ba46@kernel.org>
Thanks for the feedback.
> I would suggest to fix VA_BITS definition instead of defining a new macro here.
I can make VA_BITS branchfree at the cost of readability. Let me know
if that's preferred over a separate macro.
I agree that the guard page approach is more robust than clearing the sign
bit. Is Smnpm currently used or planned for the kernel? If not, clearing
the sign bit should be sufficient since it creates a non-canonical address
that always faults.
Thanks,
Lukas
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-01-06 10:30 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
2026-01-06 10:30 ` Lukas Gerlach [this message]
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=20260106103010.5577-1-lukas.gerlach@cispa.de \
--to=lukas.gerlach@cispa.de \
--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=marton.bognar@kuleuven.be \
--cc=michael.schwarz@cispa.de \
--cc=palmer@dabbelt.com \
--cc=patchwork-bot+linux-riscv@kernel.org \
--cc=pjw@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