https://ankitkdev.com/tags/slab/Recent content in Slab on ankit_kdevHugoen-usWed, 04 Feb 2026 16:45:19 +0530https://ankitkdev.com/blog/debug-slub-memory/Wed, 04 Feb 2026 16:45:19 +0530https://ankitkdev.com/blog/debug-slub-memory/<h1 id="introduction">Introduction</h1> <p>Memory corruption can occur due to various bugs or defects: Uninitialized Memory Reads (UMR), Use After Free (UAF), Use After Return (UAR), double-free, memory leakage, or illegal Out Of Bounds (OOB) accesses that attempt to work upon (read/write/ execute) illegal memory regions.</p> <p>Since memory is dynamically allocated and freed via the kernel&rsquo;s engine – the page allocator. This can lead to serious wastage (internal fragmentation) of memory. To mitigate this, the slab allocator (or slab cache) is layered upon it, serving two primary tasks – providing fragments of pages efficiently (within the kernel, allocation requests for small pieces of memory, from a few bytes to a couple of kilobytes), and serving as a cache for commonly used data structures.</p>