Messages in this thread | | | Subject | Re: [PATCH v4] kmemleak: survive in a low-memory situation | From | Pekka Enberg <> | Date | Thu, 28 Mar 2019 08:05:31 +0200 |
| |
Hi,
On 27/03/2019 2.59, Qian Cai wrote: > Unless there is a brave soul to reimplement the kmemleak to embed it's > metadata into the tracked memory itself in a foreseeable future, this > provides a good balance between enabling kmemleak in a low-memory > situation and not introducing too much hackiness into the existing > code for now.
Unfortunately I am not that brave soul, but I'm wondering what the complication here is? It shouldn't be too hard to teach calculate_sizes() in SLUB about a new SLAB_KMEMLEAK flag that reserves spaces for the metadata.
- Pekka
| |