after many years of procrastination, private (née unreadable) kstacks are about to graduate from PoC to production. not possible without some existing infrastructure we've developed for UDEREF and other features over a decade ago. payoff++ :)
3
8
31
While the first thing that comes to mind when thinking “kstack” is RANDKSTACK, the first hits on Google point to @jonoberheide’s Stackjacking (paid ads?). Curious about the new feature ;)
1
1
the goal is simple: a given cpu can access only the current kstack, #PF on everyone else's (modulo some complications when such 'foreign' kstack accesses are intended). basically this is similar to what you already have in userland between process stacks.
Jan 4, 2022 · 1:00 PM UTC
3
3