linux-kernel - Re: [stable] 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]

Message-ID: <20100927061336.GA22721@kroah.com>
Date:	Sun, 26 Sep 2010 23:13:36 -0700
From:	Greg KH <greg@...ah.com>
To:	Kyle McMartin <kyle@...hat.com>
Cc:	James Dingwall <james.dingwall@...ocs.com>,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	stable@...nel.org
Subject: Re: [stable] PROBLEM: [BISECTED] 2.6.35.5 xen domU panics just
	after the boot

On Sun, Sep 26, 2010 at 10:40:44PM -0400, Kyle McMartin wrote:
> On Thu, Sep 23, 2010 at 04:23:55PM +0100, 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.
> > 
> 
> Greg, a spelling mistake cropped into this patch during 2.6.35.5 that
> James here points out. Adding you to CC since it seems to have missed
> stable 2.6.35.6...
> 
> Was in xen-use-percpu-interrupts-for-ipis-and-virqs.patch.

I don't understand, where did the error come from?  Was it in a patch I
applied, or did I mess up some patch?  Is the same problem upstream, and
if not, why not?

And finally, can you send this in a format that I can apply it?

thanks,

greg k-h
--
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/