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: <20110401190812.GA16830@elte.hu>
Date:	Fri, 1 Apr 2011 21:08:12 +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:

> P.S.
>
> I asked for a backport of e5f15b45ddf3afa2bbbb10c7ea34fb32b6de0a0e to the 
> stable trees because I forgot to add "CC stable@...nel.org" to the commit 
> message and this commit is needed to fix a critical crash on boot on xen.

You are displaying a dangerously amateurish attitude towards quality control 
and you clealy have no idea what it takes to push fixes into -stable.

You forwarded a brand-new, visibly dangerous native kernel commit to -stable 
without Cc:-ing the maintainers and you have caused a native kernel regression 
that way. You are not maintaining the code in question and you have not 
committed the patch in question.

-stable team, please revert this commit. The whole issue obviously needs more 
testing and we'll forward a proper fix once it's available and tested.

	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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ