linux-kernel - Re: [OOPS] [XEN] OOPS early after boot on master

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1245050039.5782.867.camel@localhost.localdomain>
Date:	Mon, 15 Jun 2009 08:13:59 +0100
From:	Ian Campbell <Ian.Campbell@...rix.com>
To:	Bryan Donlan <bdonlan@...il.com>
CC:	Jeremy Fitzhardinge <jeremy@...p.org>,
	LKML <linux-kernel@...r.kernel.org>,
	<xen-devel@...ts.xensource.com>
Subject: Re: [OOPS] [XEN] OOPS early after boot on master

On Thu, 2009-06-11 at 18:55 -0400, Bryan Donlan wrote:
> On further analysis, it seems that that's a red herring - disabling PV
> spinlocks just makes it occur less often, I think... I'm currently
> still bisecting it; it's complicated by other OOPS-causing bugs having
> existed in the interim, but it definitely existed before the
> introduction of CONFIG_PARAVIRT_SPINLOCKS.

It's worth bearing in mind that prior to CONFIG_PARAVIRT_SPINLOCKS the
pv spinlock functionality was already present but not optional so it's
not unlikely that an issue with pv spinlocks could predate the addition
of the option.

Ian.


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