On 5/30/25 02:27, Bo Li wrote: > RPAL leverages Memory Protection Keys (MPK) to safeguard shared memory > from illegal access and corruption by other processes. ... as long as nobody uses the completely unprivileged WRPKRU or XRSTOR instructions. Right? ... the instructions that are plainly available in super obscure libraries like glibc? This seems like a rather major oversight. Oh, speaking of major oversights, you stymied pkey_alloc() but forgot pkey_free(). There's nothing to stop folks from pkey_free()'ing a pkey that RPAL is using and then letting someone else allocate it. Is this all for real and serious?
