linux-kernel - Re: [stable] Change 5c371b31be3203 in stable breaks Xen

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: <20081126000340.GB1091@kroah.com>
Date:	Tue, 25 Nov 2008 16:03:40 -0800
From:	Greg KH <greg@...ah.com>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Ian Campbell <ijc@...lion.org.uk>,
	Daniel Schröder <mail@...hroeder.info>,
	Ingo Molnar <mingo@...e.hu>, Yinghai Lu <yinghai@...nel.org>,
	Stable Kernel <stable@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [stable] Change 5c371b31be3203 in stable breaks Xen

On Tue, Nov 25, 2008 at 03:25:50PM -0800, Jeremy Fitzhardinge wrote:
> Ian Campbell wrote:
> > On Tue, 2008-11-25 at 13:26 -0800, Jeremy Fitzhardinge wrote:
> >   
> >> I have a report of Xen breaking between 2.6.27.5 and .6.  I bisected
> >> it 
> >> down to change:
> >>
> >> commit 5c371b31be32033b0a4a993431484da8a2305369
> >> Author: Yinghai Lu <yhlu.kernel@...il.com>
> >> Date:   Mon Sep 22 02:52:26 2008 -0700
> >>
> >>     x86: fix CONFIG_X86_RESERVE_LOW_64K=y
> >>    
> >>     commit 2216d199b1430d1c0affb1498a9ebdbd9c0de439 upstream
> >>     
> >
> > Looks like 5dc64a3442b98eaa0e3730c35fcf00cf962a93e7 might be needed in
> > stable too?
> >   
> 
> Ah, yes, that looks like the right fix.  I'll see if it helps.

If so, let us know and we will add it to the next -stable release.

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/