| 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: 23 Aug 2006 14:06:06 +0200 From: Andi Kleen <ak@...e.de> To: Akinobu Mita <mita@...aclelinux.com> Cc: akpm@...l.org, okuji@...ug.org, linux-kernel@...r.kernel.org Subject: Re: [patch 0/5] RFC: fault-injection capabilities Akinobu Mita <mita@...aclelinux.com> writes: > 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. Nice. The SUSE kernel has a crasher module that is also quite useful for testing. What it does basically is to always allocate/free memory and overwrite the memory and check if the memory hasn't been changed by someone else. Perhaps something like that could be incorporated into your framework too? I put a copy of the suse patch in http://www.firstfloor.org/~andi/crasher-26.diff > > In order to enable these fault-injection capabilities: However I'm not sure they're too useful right now. The problem is that they're too global and might render the system unusable. Have you considered adding some more filters, like uid/gid to fail only ( I think that would be useful because then it would be possible to run test suites with faults while keeping other parts of the system functional) or maybe even a list of callers to test? e.g. only failing for module foo would be nice. -Andi - 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/
Powered by blists - more mailing lists