mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Akinobu Mita <mita@miraclelinux.com>
Cc: linux-kernel@vger.kernel.org, okuji@enbug.org
Subject: Re: [PATCH] failslab - failmalloc for slab allocator
Date: Sun, 13 Aug 2006 12:17:02 -0700	[thread overview]
Message-ID: <20060813121702.78e72c1a.akpm@osdl.org> (raw)
In-Reply-To: <20060813102219.GA8784@miraclelinux.com>

On Sun, 13 Aug 2006 18:22:19 +0800
Akinobu Mita <mita@miraclelinux.com> wrote:

> This patch is not intended for inclusion. But I could find
> several interesting crashes.
> 
> The idea behind failslab is to demonstrate what really happens if
> slab allocation fails. The idea of failslab is completely taken
> from failmalloc (http://www.nongnu.org/failmalloc/).
> 
> boot option:
> 
> failslab=<probability>,<interval>,<times>,<space>
> 
> <probability>
> 	specifies how often it should fail in percent.
> <interval>
> 	specifies the interval of failures.
> <times>
> 	specifies how many times failures may happen at most.
> <space>
> 	specifies the size of free space where memory can be allocated
> 	safely in bytes.
> 
> examples:
> 
> failslab=100,10,-1,0
> 
> slab allocation (kmalloc, kmem_cache_alloc,..) fails once per 10 times.

We would benefit from having some faul-injection capabilities in the
mainline kernel.

- kmalloc failures

- alloc_pages() failures

- disk IO errors (there are rumours of a DM module for this, but I
  haven't seen it).

They would need to be lightweight, clean and enabled/configured at runtime,
not at boot time.

This would end up being a fairly complex project.

  parent reply	other threads:[~2006-08-13 19:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-13 10:22 Akinobu Mita
2006-08-13 10:28 ` Akinobu Mita
2006-08-13 19:17 ` Andrew Morton [this message]
2006-08-14 10:18   ` Akinobu Mita

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=20060813121702.78e72c1a.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mita@miraclelinux.com \
    --cc=okuji@enbug.org \
    /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

Powered by JetHome