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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090806122935.GB15314@elte.hu>
Date:	Thu, 6 Aug 2009 14:29:35 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Gautham R Shenoy <ego@...ibm.com>
Cc:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>, mingo@...hat.com,
	hpa@...or.com, linux-kernel@...r.kernel.org, tglx@...utronix.de,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:core/rcu] rcu: Add diagnostic check for a possible
	CPU-hotplug race


* Gautham R Shenoy <ego@...ibm.com> wrote:

> On Wed, Aug 05, 2009 at 06:26:45PM -0700, Paul E. McKenney wrote:
> > On Mon, Aug 03, 2009 at 05:56:18AM -0700, Paul E. McKenney wrote:
> > > On Mon, Aug 03, 2009 at 09:04:58AM +0200, Ingo Molnar wrote:
> > > > 
> > > > i've attached the full serial bootlog with the warning in it. This 
> > > > should address your question about what the order of initialization 
> > > > is, right?
> > > 
> > > It does, thank you!  This problem really is happening during boot.
> > > 
> > > > Let me know if you still would like me to run your diagnostic patch 
> > > > too.
> > > 
> > > Now that you mention it, you should probably let me test it a bit first.
> > 
> > And here is a tested and debugged version.  Diagnostic only, not for
> > inclusion, based on tip/core/rcu as of today (August 5th).
> > 
> > Gautham, have you been able to reproduce on your machines?  
> > Still cannot here.
> 
> I tried on a couple of machines yesterday, but I still couldn't 
> reproduce it with Ingo's config.

Paul, should i try your latest diagnostic patch in -tip testing, to 
see whether it triggers any new warning?

	Ingo
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ