linux-kernel - 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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 23 Sep 2010 19:53:50 +0200
From:	Paweł Zuzelski <pawelz@...-linux.org>
To:	James Dingwall <james.dingwall@...ocs.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>
Subject: Re: PROBLEM: [BISECTED] 2.6.35.5 xen domU panics just after the
 boot

On Thu, 23 Sep 2010, James Dingwall wrote:

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

I confirm. This patch works for me. Thanks.

-- 
Regards,
Paweł Zuzelski
--
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/