linux-kernel - RE: Re: PROBLEM: [BISECTED] 2.6.35.5 xen domU panics just after the boot

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

Message-ID: <3B7AEC3C7FCC864282DFAC9A56A7BA363D81475787@UKLNDMAIL1.corp.amdocs.com>
Date:	Thu, 23 Sep 2010 16:23:55 +0100
From:	James Dingwall <james.dingwall@...ocs.com>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:	Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>
Subject: RE: Re: PROBLEM: [BISECTED] 2.6.35.5 xen domU panics just after the
 boot

> I was experiencing the same immediate crash with a null pointer
> dereference (log below) on boot with 2.6.35.5.  Reverting
> fb412a178502dc498430723b082a932f797e4763 also resolved the problem for
> me.

Checking the diff from this commit it looks like there is a typo in the patch.  With the following (probably mangled by my client) I get 2.6.35.5 to boot.  Suggest it should be a candidate for .32 and .35 stable trees.

--- drivers/xen/events.c.orig   2010-09-23 16:10:34.257124313 +0100
+++ drivers/xen/events.c        2010-09-23 16:10:44.326194462 +0100
@@ -935,7 +935,7 @@
 	.retrigger		= retrigger_dynirq,
 };

-static struct irq_chip en_percpu_chip __read_mostly = {
+static struct irq_chip xen_percpu_chip __read_mostly = {
 	.name			= "xen-percpu",

 	.disable		= disable_dynirq,

James
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp

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