Doug / smarc-fsl-linux-kernel

09 Dec, 2006

4 commits

  • 5d0ffa2b8   [PATCH] fault-injection: Correct, disambiguate, and reformat documentation ... Browse Code »

    Correct, disambiguate, and reformat documentation.

    Signed-off-by: Don Mullis
    Cc: Akinobu Mita
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Don Mullis
     
  • 329409aed   [PATCH] fault injection: stacktrace filtering ... Browse Code »

    This patch provides stacktrace filtering feature.

    The stacktrace filter allows failing only for the caller you are
    interested in.

    For example someone may want to inject kmalloc() failures into
    only e100 module. they want to inject not only direct kmalloc() call,
    but also indirect allocation, too.

    - e100_poll --> netif_receive_skb --> packet_rcv_spkt --> skb_clone
    --> kmem_cache_alloc

    This patch enables to detect function calls like this by stacktrace
    and inject failures. The script Documentaion/fault-injection/failmodule.sh
    helps it.

    The range of text section of loaded e100 is expected to be
    [/sys/module/e100/sections/.text, /sys/module/e100/sections/.exit.text)

    So failmodule.sh stores these values into /debug/failslab/address-start
    and /debug/failslab/address-end. The maximum stacktrace depth is specified
    by /debug/failslab/stacktrace-depth.

    Please see the example that demonstrates how to inject slab allocation
    failures only for a specific module
    in Documentation/fault-injection/fault-injection.txt

    [dwm@meer.net: reject failure if any caller lies within specified range]
    Signed-off-by: Akinobu Mita
    Signed-off-by: Don Mullis
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Akinobu Mita
     
  • 8a8b6502f   [PATCH] fault-injection capability for kmalloc ... Browse Code »

    This patch provides fault-injection capability for kmalloc.

    Boot option:

    failslab=,,,

    -- specifies the interval of failures.

    -- specifies how often it should fail in percent.

    -- specifies the size of free space where memory can be
    allocated safely in bytes.

    -- specifies how many times failures may happen at most.

    Debugfs:

    /debug/failslab/interval
    /debug/failslab/probability
    /debug/failslab/specifies
    /debug/failslab/times
    /debug/failslab/ignore-gfp-highmem
    /debug/failslab/ignore-gfp-wait

    Example:

    failslab=10,100,0,-1

    slab allocation (kmalloc(), kmem_cache_alloc(),..) fails once per 10 times.

    Cc: Pekka Enberg
    Signed-off-by: Akinobu Mita
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Akinobu Mita
     
  • de1ba09b2   [PATCH] fault injection: documentation and scripts ... Browse Code »

    This patch set provides some fault-injection capabilities.

    - kmalloc() failures

    - alloc_pages() failures

    - disk IO errors

    We can see what really happens if those failures happen.

    In order to enable these fault-injection capabilities:

    1. Enable relevant config options (CONFIG_FAILSLAB, CONFIG_PAGE_ALLOC,
    CONFIG_MAKE_REQUEST) and if you want to configure them via debugfs,
    enable CONFIG_FAULT_INJECTION_DEBUG_FS.

    2. Build and boot with this kernel

    3. Configure fault-injection capabilities behavior by boot option or debugfs

    - Boot option

    failslab=
    fail_page_alloc=
    fail_make_request=

    - Debugfs

    /debug/failslab/*
    /debug/fail_page_alloc/*
    /debug/fail_make_request/*

    Please refer to the Documentation/fault-injection/fault-injection.txt
    for details.

    4. See what really happens.

    Signed-off-by: Akinobu Mita
    Signed-off-by: Don Mullis
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Akinobu Mita