| 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: Mon, 03 Mar 2008 13:42:40 +0100 From: Andi Kleen <andi@...stfloor.org> To: Thomas Gleixner <tglx@...utronix.de> Cc: LKML <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...ux-foundation.org>, Ingo Molnar <mingo@...e.hu>, Greg KH <greg@...ah.com>, chris.mason@...cle.com Subject: Re: [patch 0/2] object debugging infrastructure Thomas Gleixner <tglx@...utronix.de> writes: > > The debugobjects core code keeps track of operations on static and > dynamic objects by inserting them into a hashed list and sanity > checking them on object operations and providing additional checks > whenever kernel memory is freed. Nice idea to make this generic. If you push this it would be also good to consider some variant of the "crasher" code that is in SUSE Kernels to include with it. It was originally written by Chris Mason and it also makes it easier to stabilize such bugs. The basic idea is that a background thread allocates lots of slabs and pages always poisons them and checks them in the background. If someone corrupts memory that is noticed earlier then Basically it extends what your patchkit is doing to free memory too. Chris' old patch: http://firstfloor.org/~andi/crasher-26.diff (various variants of that have existed over time) -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