Re: Memory exhaustion testing?

[David Rientjes <rientjes@google.com>]

On Tue, 17 Nov 2015, Jesper Dangaard Brouer wrote:

> I did manage to provoke/test the error path in kmem_cache_alloc_bulk(),
> by using fault-injection framework "fail_page_alloc".
> 
> But was a little hard to trigger SLUB errors with this, because SLUB
> retries after a failure, and second call to alloc_pages() is done with
> lower order.
> 
> If order is lowered to zero, then should_fail_alloc_page() will skip it.
> And just lowering /sys/kernel/debug/fail_page_alloc/min-order=0 is not
> feasible as even fork starts to fail.  I managed to work-around this by
> using "space" setting.
> 
> Created a script to ease this tricky invocation:
>  https://github.com/netoptimizer/prototype-kernel/blob/master/tests/fault-inject/fail01_kmem_cache_alloc_bulk.sh
> 

Any chance you could proffer some of your scripts in the form of patches 
to the tools/testing directory?  Anything that can reliably trigger rarely 
executed code is always useful.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>