| 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, 12 Oct 2009 14:30:07 -0400 From: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca> To: Ingo Molnar <mingo@...e.hu> Cc: Thomas Gleixner <tglx@...utronix.de>, akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> Subject: Re: [patch 0/4] DEBUG_RCU_HEAD: Debug and fix racy call_rcu() users * Ingo Molnar (mingo@...e.hu) wrote: > > * Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca> wrote: > > > Here is a patchset, done on 2.6.30.9, which permits to detect and fix > > racy call_rcu() users. > > Nice idea - but any reason why this isnt using the debugojects > framework? That debugging framework is upstream already and allows this > kind of object lifetime debugging - in a much broader way. > Other than: it did not occur to me, no, there is no reason for not using debugobjects there. :-) As long as we can tag the object as - initialized - active - inactive And dump a nice fat warning when the object is activated twice, that should suffice. Now time is a bit short on my side, but I'll keep in mind to respin a version on top of debugobjects soon. Thanks, Mathieu > Ingo -- Mathieu Desnoyers OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68 -- 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