From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v5 0/7] powerpc: Implement masked user access
Date: Wed, 14 Jan 2026 08:34:09 +0530 [thread overview]
Message-ID: <176835971837.41689.5793831185458832406.b4-ty@linux.ibm.com> (raw)
In-Reply-To: <cover.1766574657.git.chleroy@kernel.org>
On Wed, 24 Dec 2025 12:20:48 +0100, Christophe Leroy (CS GROUP) wrote:
> This is a rebase on top of v6.19-rc2
>
> Masked user access avoids the address/size verification by access_ok().
> Allthough its main purpose is to skip the speculation in the
> verification of user address and size hence avoid the need of spec
> mitigation, it also has the advantage to reduce the amount of
> instructions needed so it also benefits to platforms that don't
> need speculation mitigation, especially when the size of the copy is
> not know at build time.
>
> [...]
Applied to powerpc/next.
[1/7] powerpc/uaccess: Move barrier_nospec() out of allow_read_{from/write}_user()
https://git.kernel.org/powerpc/c/5fbc09eb0b4f4b1a4b33abebacbeee0d29f195e9
[2/7] powerpc/uaccess: Remove unused size and from parameters from allow_access_user()
https://git.kernel.org/powerpc/c/e3efbfbfaaaa739072b2756cfb76cd3de6d91c0f
[3/7] powerpc/uaccess: Remove {allow/prevent}_{read/write/read_write}_{from/to/}_user()
https://git.kernel.org/powerpc/c/5458989a0e48c2bd51a7d37a04ff6ae489fe5458
[4/7] powerpc/uaccess: Refactor user_{read/write/}_access_begin()
https://git.kernel.org/powerpc/c/704f4300315396af94e26ec0127ff0cd3fd309bf
[5/7] powerpc/32s: Fix segments setup when TASK_SIZE is not a multiple of 256M
https://git.kernel.org/powerpc/c/fb7903771c107b0358584a359b8545060e23c530
[6/7] powerpc/32: Automatically adapt TASK_SIZE based on constraints
https://git.kernel.org/powerpc/c/370d841929c3b863b7409047e8c84eabc4d0960f
[7/7] powerpc/uaccess: Implement masked user access
https://git.kernel.org/powerpc/c/861574d51bbd7a06dbf07f658a9a8def012c2f74
cheers
prev parent reply other threads:[~2026-01-14 3:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 11:20 [PATCH v5 0/7] powerpc: Implement masked user access Christophe Leroy (CS GROUP)
2025-12-24 11:20 ` [PATCH v5 1/7] powerpc/uaccess: Move barrier_nospec() out of allow_read_{from/write}_user() Christophe Leroy (CS GROUP)
2025-12-24 11:20 ` [PATCH v5 2/7] powerpc/uaccess: Remove unused size and from parameters from allow_access_user() Christophe Leroy (CS GROUP)
2025-12-24 11:20 ` [PATCH v5 3/7] powerpc/uaccess: Remove {allow/prevent}_{read/write/read_write}_{from/to/}_user() Christophe Leroy (CS GROUP)
2025-12-24 11:20 ` [PATCH v5 4/7] powerpc/uaccess: Refactor user_{read/write/}_access_begin() Christophe Leroy (CS GROUP)
2025-12-24 11:20 ` [PATCH v5 5/7] powerpc/32s: Fix segments setup when TASK_SIZE is not a multiple of 256M Christophe Leroy (CS GROUP)
2025-12-24 11:20 ` [PATCH v5 6/7] powerpc/32: Automatically adapt TASK_SIZE based on constraints Christophe Leroy (CS GROUP)
2025-12-24 11:20 ` [PATCH v5 7/7] powerpc/uaccess: Implement masked user access Christophe Leroy (CS GROUP)
2026-01-07 8:34 ` Gabriel Paubert
2026-01-14 3:04 ` Madhavan Srinivasan [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=176835971837.41689.5793831185458832406.b4-ty@linux.ibm.com \
--to=maddy@linux.ibm.com \
--cc=chleroy@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox