| 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
| ||
|
Date: Thu, 24 Aug 2006 14:41:48 -0400
From: Valdis.Kletnieks@...edu
To: Akinobu Mita <mita@...aclelinux.com>
Cc: linux-kernel@...r.kernel.org, akpm@...l.org, okuji@...ug.org
Subject: Re: [patch 0/5] RFC: fault-injection capabilities
On Wed, 23 Aug 2006 20:32:43 +0900, Akinobu Mita said:
> For example about kmalloc failures:
>
> /debug/failslab/probability
>
> specifies how often it should fail in percent.
As others have noted, the *right* semantics for this is being able to inject a
1% or higher rate in the code you're interested in, while maintaining a 0
injection rate for things outside the module under test. Maybe a /debug/
failslab/address_start and address_end, and a userspace helper that peeks at a
System.map and injects the right values - then it's a simple compare of the
high/low addresses provided against the caller address.
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists