| 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
| ||
|
Message-Id: <200608311245.40578.ak@suse.de> Date: Thu, 31 Aug 2006 12:45:40 +0200 From: Andi Kleen <ak@...e.de> To: Akinobu Mita <mita@...aclelinux.com> Cc: linux-kernel@...r.kernel.org, akpm@...l.org, okuji@...ug.org Subject: Re: [patch 3/6] fault-injection capability for alloc_pages() On Thursday 31 August 2006 12:35, Akinobu Mita wrote: > On Thu, Aug 31, 2006 at 12:25:02PM +0200, Andi Kleen wrote: > > > I still think this will need some better filters to be useful. At least > > a optional uid filter perhaps (make sure to handle the interrupt case > > correctly, interrupts don't belong to the uid) , and perhaps an option to only > > fail GFP_ATOMIC. > > I wrote process filter. Oops sorry. I overlooked that. > Please patch 6/6. But I forgot to ignore > in_interrupt() case. Ok fine then. > > > With arbitary failing the system will just be unusable, right? Or would > > you run some system you use this way? @) > > > > Another possibility would be to look up __builtin_return_address(0) in > > the module table and allow failing only for a specific module. > > That will be useful. Thanks. It might unfortunately need architecture specific code. But I guess a i386 only implementation as start would be useful enough. -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