public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Akinobu Mita <mita@miraclelinux.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, okuji@enbug.org
Subject: Re: [PATCH] failslab - failmalloc for slab allocator
Date: Mon, 14 Aug 2006 18:18:39 +0800	[thread overview]
Message-ID: <20060814101839.GA8049@miraclelinux.com> (raw)
In-Reply-To: <20060813121702.78e72c1a.akpm@osdl.org>

On Sun, Aug 13, 2006 at 12:17:02PM -0700, Andrew Morton wrote:
> 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).

What shold I do for this?
Should we have faul-injection capability in generic_make_request()
like this patch?

Index: work-failmalloc/block/ll_rw_blk.c
===================================================================
--- work-failmalloc.orig/block/ll_rw_blk.c
+++ work-failmalloc/block/ll_rw_blk.c
@@ -3077,6 +3077,9 @@ end_io:
 		if (unlikely(test_bit(QUEUE_FLAG_DEAD, &q->queue_flags)))
 			goto end_io;
 
+		if (should_fail(&fail_make_request, bio->bi_size))
+			goto end_io;
+
 		/*
 		 * If this device has partitions, remap block n
 		 * of partition p to block n+start(p) of the disk.


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

I'll make it configurable at runtime with using debugfs.


      reply	other threads:[~2006-08-14 10:18 UTC|newest]

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

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=20060814101839.GA8049@miraclelinux.com \
    --to=mita@miraclelinux.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --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