Mohammed EL Kadiri <[email protected]> writes: > Add documentation explaining when and how to use SLAB_NO_MERGE to > protect security-critical slab caches from cross-cache heap > exploitation. > > The document covers: > - Criteria for identifying caches that need isolation > - How the SLUB merge mechanism works and what prevents merging > - How to verify merge status on a running system > - The cross-cache attack class with CVE reference > - Tradeoffs (memory cost vs security benefit) > - Relationship to CONFIG_RANDOM_KMALLOC_CACHES, SLAB_TYPESAFE_BY_RCU, > and the slab_nomerge boot parameter > > This information was previously undocumented, requiring developers to > read mm/slab_common.c to understand when SLAB_NO_MERGE is appropriate. > > Signed-off-by: Mohammed EL Kadiri <[email protected]> > --- > Documentation/mm/index.rst | 1 + > Documentation/mm/slab-isolation.rst | 113 ++++++++++++++++++++++++++++ > 2 files changed, 114 insertions(+) > create mode 100644 Documentation/mm/slab-isolation.rst
Thank you for working to improve our documentation. Did you write this with machine assistance? Please review our documentation and adhere to our markup conventions. For example, function names should just be function(), with no additional markup. Thanks, jon
