linux-kernel - Re: Warning in during hotplug on 2.6.27-rc2-git5

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] [day] [month] [year] [list]

Message-Id: <200808181842.26099.rjw@sisk.pl>
Date:	Mon, 18 Aug 2008 18:42:24 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	"Langsdorf, Mark" <mark.langsdorf@....com>
Cc:	"Andi Kleen" <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
	"Greg KH" <greg@...ah.com>, "Ingo Molnar" <mingo@...e.hu>,
	"Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: Warning in during hotplug on 2.6.27-rc2-git5

On Monday, 18 of August 2008, Langsdorf, Mark wrote:
> > > > > I'm still seeing it on 2.6.27-rc2, even with the 
> > > > > patch here http://lkml.org/lkml/2008/7/30/171 and the
> > > > > wbinvd_halt code patch applied.  Maybe something else
> > > > > broke in some of the recent hotplug changes?
> >
> > I have a couple of questions, then:
> > - Does it fail identically for all CPUs or for CPU4 and above only?
> > - Did previous kernels, most importantly 2.6.26, work correctly?
> 
> It turns out 2.6.26 also fails.

OK, so I'll drop the bug from the list of recent regressions.

> It is only failing for CPU4+, I'm not sure why that would be significant.

Because I cannot reproduce it on a single-socket AMD quad-core. :-)

> > Also, can you please attach dmesg output, including the 
> > offlining of a CPU that would later lead to the problem
> > with cpu_up(), to the Bugzilla entry at
> > http://bugzilla.kernel.org/show_bug.cgi?id=11337 ?
> 
> I did.

Thanks.  I think we can further debug this using Bugzilla if you don't mind.

Best,
Rafael
--
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/