From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Paul E. McKenney" Subject: Re: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ] Date: Fri, 19 Apr 2013 14:39:54 -0700 Message-ID: <20130419213953.GN3479@linux.vnet.ibm.com> References: <517198A7.8020904@surriel.com> <1366402328.5317.9.camel@buesod1.americas.hpqcorp.net> Reply-To: paulmck@linux.vnet.ibm.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Linus Torvalds Cc: Sedat Dilek , Davidlohr Bueso , Rik van Riel , Daniel Vetter , Stephen Rothwell , linux-next , Linux Kernel Mailing List , the arch/x86 maintainers , Ingo Molnar , Thomas Gleixner , Paul McKenney , DRI , Dave Airlie , Emmanuel Benisty List-Id: linux-next.vger.kernel.org On Fri, Apr 19, 2013 at 02:24:10PM -0700, Linus Torvalds wrote: > On Fri, Apr 19, 2013 at 2:09 PM, Sedat Dilek wrote: > > > > I have applied all three patches and see still call-traces. > > New are apparmor related messages. > > Can you try the crazy rcu double-free debug hack? > > See > > https://lkml.org/lkml/2013/3/30/113 > > and I'm re-attaching the ugly-ass crazy hack patch here too.. > > Linus For whatever it is worth, CONFIG_DEBUG_OBJECTS_RCU_HEAD=y is intended to detect RCU double-freeing. But if it isn't helping for whatever reason, please let me know! Thanx, Paul