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]

Message-ID: <20110404151132.GC11475@elte.hu>
Date:	Mon, 4 Apr 2011 17:11:32 +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>
Subject: Re: [PATCH urgent] x86: Save cr4 to mmu_cr4_features at boot time


* 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?

> [...] (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.

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

> I didn't mean for the backport to be done right now, I just wanted to
> notify the stable maintainers that the particular commit should be
> backported at some point.
> 
> I didn't mean to overstep your authority in any way.

It's not about overstepping authority - it's about not breaking the native 
kernel on millions of boxes.

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/