[patch V3 07/12] uaccess: Provide scoped masked user access regions
Thomas Gleixner
tglx at linutronix.de
Wed Oct 22 01:42:22 AEDT 2025
On Tue, Oct 21 2025 at 16:29, Thomas Gleixner wrote:
> On Mon, Oct 20 2025 at 19:28, David Laight wrote:
>> There is no requirement to do the accesses in strict memory order
>> (or to access the lowest address first).
>> The only constraint is that gaps must be significantly less than 4k.
>
> The requirement is that the access is not spilling over into the kernel
> address space, which means:
>
> USR_PTR_MAX <= address < (1U << 63)
>
> USR_PTR_MAX on x86 is either
> (1U << 47) - PAGE_SIZE (4-level page tables)
> or (1U << 57) - PAGE_SIZE (5-level page tables)
>
> Which means at least ~8 EiB of unmapped space in both cases.
>
> The access order does not matter at all.
I just noticed that LAM reduces that gap to one page, but then the
kernel has a 8EiB gap right at the kernel/user boundary, which means
even in the LAM case an access with less than 8EiB offset from
USR_PTR_MAX is guaranteed to fault and not to be able to speculatively
access actual kernel memory.
Thanks,
tglx
More information about the Linuxppc-dev
mailing list