* slab_alloc_node with CONFIG_SLAB_FREELIST_HARDENED
@ 2021-05-11 15:52 Derrick McKee
0 siblings, 0 replies; only message in thread
From: Derrick McKee @ 2021-05-11 15:52 UTC (permalink / raw)
To: Linux Memory Management List
Cc: cl, penberg, rientjes, iamjoonsoo.kim, Andrew Morton
Hi,
I am trying to understand how slab_alloc_node works in mm/slub.c when
CONFIG_SLAB_FREELIST_HARDENED=y. It seems like in ___slab_alloc,
c->freelist gets assigned the result of get_freepointer, which, when
CONFIG_SLAB_FREELIST_HARDENED=y, returns a value XOR'd with a
per-cache random number. However, that XOR'd value is never seemingly
undone, and slab_alloc_node passes the XOR'd (and thus invalid)
pointer directly to get_freepointer. Does anyone know where the XOR
reversal is performed? Thanks.
--
Derrick McKee
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-05-11 15:52 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-05-11 15:52 slab_alloc_node with CONFIG_SLAB_FREELIST_HARDENED Derrick McKee
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.