From: Jesper Dangaard Brouer <brouer@redhat.com>
To: David Rientjes <rientjes@google.com>
Cc: linux-mm <linux-mm@kvack.org>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
brouer@redhat.com
Subject: Re: Memory exhaustion testing?
Date: Fri, 20 Nov 2015 14:09:16 +0100 [thread overview]
Message-ID: <20151120140916.33ec7896@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1511191239001.7151@chino.kir.corp.google.com>
On Thu, 19 Nov 2015 12:40:50 -0800 (PST)
David Rientjes <rientjes@google.com> wrote:
> 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.
Perhaps that is a good idea.
I think should move the directory location in my git-repo
prototype-kernel[1] to reflect this directory layout, like I do with
real kernel stuff. And when we are happy with the quality of the
scripts we can "move" it to the kernel. (Like I did with my pktgen
tests[4], now located in samples/pktgen/).
A question; where should/could we place the kernel module
slab_bulk_test04_exhaust_mem[1] that my fail01 script depends on?
BTW, I've also added a script for testing NULL handling in normal
kmem_cache_alloc() call see[3].
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
Author of http://www.iptv-analyzer.org
LinkedIn: http://www.linkedin.com/in/brouer
[1] https://github.com/netoptimizer/prototype-kernel/
[2] https://github.com/netoptimizer/prototype-kernel/blob/master/kernel/mm/slab_bulk_test04_exhaust_mem.c
[3] https://github.com/netoptimizer/prototype-kernel/blob/master/tests/fault-inject/fail02_kmem_cache_alloc.sh
[4] https://github.com/netoptimizer/network-testing/tree/master/pktgen
--
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>
next prev parent reply other threads:[~2015-11-20 13:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 20:55 Jesper Dangaard Brouer
2015-11-13 22:54 ` David Rientjes
2015-11-16 14:24 ` Jesper Dangaard Brouer
2015-11-17 13:21 ` Jesper Dangaard Brouer
2015-11-19 20:40 ` David Rientjes
2015-11-20 13:09 ` Jesper Dangaard Brouer [this message]
2015-11-20 23:23 ` David Rientjes
2015-11-20 23:28 ` Andrew Morton
2015-11-14 8:23 ` Tetsuo Handa
2015-11-16 14:43 ` Jesper Dangaard Brouer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151120140916.33ec7896@redhat.com \
--to=brouer@redhat.com \
--cc=linux-mm@kvack.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=rientjes@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox