From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Paul E. McKenney" Subject: Re: 2.6.26-rc9-git4: Reported regressions from 2.6.25 Date: Fri, 1 Aug 2008 14:09:49 -0700 Message-ID: <20080801210949.GJ14851@linux.vnet.ibm.com> References: <4yrA-dRoNlD.A.jcB.ny-cIB@albercik> <200807101725.36175.nickpiggin@yahoo.com.au> <20080710110213.GA6688@martell.zuzino.mipt.ru> <20080710173459.GA11648@elte.hu> <20080710180620.GA30844@elte.hu> Reply-To: paulmck-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <20080710180620.GA30844-X9Un+BFzKDI@public.gmane.org> Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Ingo Molnar Cc: Linus Torvalds , Alexey Dobriyan , Nick Piggin , "Rafael J. Wysocki" , Kamalesh Babulal , Linux Kernel Mailing List , Adrian Bunk , Andrew Morton , Natalie Protasevich , Kernel Testers List On Thu, Jul 10, 2008 at 08:06:20PM +0200, Ingo Molnar wrote: > > * Ingo Molnar wrote: > > > cool! :) > > > > (hm, could anyone please resend Nick's original mail? The original one > > is not in my lkml folder nor on lkml.org - only the quoted one.) > > ok, got the mail now now: > > | | Annoyed this wasn't a crazy obscure error in the algorithm I could > | | fix :) [...] > > Paul recently ran a formal proof against all sorts of RCU details (and > found and fixed a few obscure races that way that no-one ever > triggered), so i'd be quite surprised if we found anything in the core > algorithm :-) > > | | [...] I spent all day debugging it and had to make a special test > | | case (rcutorture didn't seem to trigger it), and a big RCU state > | | logging infrastructure to log millions of RCU state transitions and > | | events. Oh well. > > nice debugging! Indeed!!! > Acked-by: Ingo Molnar > > i'm wondering why rcutorture didnt trigger it. I do run !HOTPLUG + > RCU_PREEMPT kernels and never saw this. Nor did Paul. That aspect is > weird. Turns out that my environment was silently re-enabling HOTPLUG_CPU, so I only -thought- I was testing !CPU_HOTPLUG. Once I forced it to really disable HOTPLUG_CPU (by manually also specifying CONFIG_SUSPEND=n and CONFIG_HIBERNATION=n), then rcutorture complained within 10 seconds. Sigh!!! Thanx, Paul