linux-kernel - Re: [PATCH urgent] x86: Save cr4 to mmu_cr4

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:	Mon, 4 Apr 2011 16:47:59 +0100
From:	Stefano Stabellini <stefano.stabellini@...citrix.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Stefano Stabellini <Stefano.Stabellini@...citrix.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	"x86@...nel.org" <x86@...nel.org>,
	"yinghai@...nel.org" <yinghai@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Greg KH <gregkh@...e.de>,
	"lkml20101129@...ton.leun.net" <lkml20101129@...ton.leun.net>,
	stable kernel team <stable@...nel.org>,
	Jeremy Fitzhardinge <Jeremy.Fitzhardinge@...rix.com>
Subject: Re: [PATCH urgent] x86: Save cr4 to mmu_cr4_features at boot time

On Mon, 4 Apr 2011, Ingo Molnar wrote:
> 
> * Stefano Stabellini <stefano.stabellini@...citrix.com> wrote:
> 
> > Just to clarify the situation the patch "x86-64: finish cleanup_highmaps()'s 
> > job wrt. _brk_end" was backported to the stable trees [...]
> 
> There's no commit with such a title upstream - there's not even one that is 
> close. Could you cite the sha1 you refer to?

The commit id upstream is 498343967613183611ac37dccb2846496d954c06


> > [...] (including Jeremy's 2.6.32 xen tree because he pulled from 2.6.32.y) 
> > breaking boot on xen.
> 
> Basing upstream-relevant trees on stable backported sha1's is a very, very bad 
> idea.

We are not using Jeremy's 2.6.32 tree for development anymore, we
develop on upstream directly.


> > Yinghai's patch plus another patch of mine fix that breakage and that is why 
> > I ask for it to be backported.
> 
> So it fixes a commit that is nowhere to be found upstream?

It fixes 498343967613183611ac37dccb2846496d954c06, if you are interested
in all the details of the conversation with Yinghai and Peter, here are
a couple of links to the lkml archives:

https://lkml.org/lkml/2011/1/31/232
https://lkml.org/lkml/2011/2/28/410

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