On 6/14/24 4:40 AM, Chengming Zhou wrote: > On 2024/6/12 06:52, Christoph Lameter (Ampere) wrote: >> On Mon, 10 Jun 2024, Vlastimil Babka wrote: >> >>> Even if some security people enable parts of slub debugging for security >>> people it is my impression they would rather panic/reboot or have memory >>> leaked than trying to salvage the slab page? (CC Kees) >> >> In the past these resilience features have been used to allow the continued operation of a broken kernel. >> >> So first the Kernel crashed with some obscure oops in the allocator due to metadata corruption. >> >> One can then put a slub_debug option on the kernel command line which will result in detailed error reports on what caused the corruption. It will also activate resilience measures that will often allow the continued operation until a fix becomes available. > > This reminds me that we can't toggle slub_debug options for kmem_cache in runtime, > I'm wondering is it useful to be able to enable/disable debug options in runtime? > We can implement this feature by using per-slab debug options, so per-slab has > independent execution path, in which some slabs with debug options enabled go > the slow path, while others can still go fast path. Many of the debug options change the layout of objects in slabs (i.e. affect calculate_sizes()) so it would be very complicated to change things in runtime. Also the cache might be merged with other ones if it boots without debug... I don't think it would be feasible at all. > No sure if it's useful in some cases? Maybe KFENCE is enough? Just my random thoughts. > > Thanks.
