linux-kernel - Re: [PATCH -mm] fault-injection: reject-failure-if-any-caller-lies-within-specified range

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20061120195208.GA18077@APFDCB5C>
Date:	Tue, 21 Nov 2006 04:52:08 +0900
From:	Akinobu Mita <akinobu.mita@...il.com>
To:	Don Mullis <dwm@...r.net>
Cc:	linux-kernel@...r.kernel.org, ak@...e.de, akpm <akpm@...l.org>
Subject: Re: [PATCH -mm] fault-injection: reject-failure-if-any-caller-lies-within-specified range

On Mon, Nov 20, 2006 at 11:24:22AM -0800, Don Mullis wrote:
> > This test is a little intentional.
> > (Normal I/O may fail, but journal commit I/O doesn't fail)
> 
> I'm not sure in what sense the test could be called "intentional".

Because make_fault_request just injects failures randomly. there is no
difference between normal I/O and journal commit I/O.

The problem is the make_fault_request doesn't have clever setting such as
md/faulty module can simulate broken sectors.

> The patch raises the default stacktrace-depth from 10 to 32, and
> although there is indeed no guarantee this is enough, in practice I
> found the filesystem became hopelessly scrambled before ever hitting one
> of the kjournald cases again.

You can set /debug/fail_make_request/times smaller value so that
you can see what happened in filesystem before kjournald hits failure.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/