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 18:25:16 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Stefano Stabellini <stefano.stabellini@...citrix.com>
Cc:	"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


* Stefano Stabellini <stefano.stabellini@...citrix.com> wrote:

> 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

That commit is from the v2.6.30 era:

 |
 | commit 498343967613183611ac37dccb2846496d954c06
 | Author:     Jan Beulich <jbeulich@...ell.com>
 | AuthorDate: Wed May 6 13:06:47 2009 +0100
 | Commit:     H. Peter Anvin <hpa@...or.com>
 | CommitDate: Thu May 7 21:51:34 2009 -0700
 |
 |    x86-64: finish cleanup_highmaps()'s job wrt. _brk_end
 |

... i.e. the bug is almost 2 years and 8 -stable cycles old!

Peter very consciously did not mark the fix for this commit as -stable 
material. It was ineligible for -stable for multiple reasons: it by no means 
fixed a 2.6.39 regression and the fix was literally just a few days old.

Thanks,

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