From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Thu, 23 Feb 2012 23:52:27 +0100 From: Willy Tarreau To: "H. Peter Anvin" Cc: Linus Torvalds , Greg Kroah-Hartman , stable@vger.kernel.org, Raphael Prevost , Suresh Siddha , Linux Kernel Mailing List Subject: Re: [PATCH 0/5] i387: stable kernel backport Message-ID: <20120223225227.GD1306@1wt.eu> References: <20120223200905.GA5475@kroah.com> <4F46A1C4.90506@zytor.com> <20120223204832.GA30322@kroah.com> <4F46A6EC.8050804@zytor.com> <20120223211016.GA16275@kroah.com> <20120223215242.GA1306@1wt.eu> <20120223222733.GB1306@1wt.eu> <4F46C253.106@zytor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F46C253.106@zytor.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: On Thu, Feb 23, 2012 at 02:48:51PM -0800, H. Peter Anvin wrote: > On 02/23/2012 02:38 PM, Linus Torvalds wrote: > > > > You'd still need an x86-32 machine to test on, because x86-64 was > > immune to this issue. > > > > But yeah, the impact of this seems to be small enough that for older > > kernels (which are likely used on older systems for maintenance > > anyway) disabling AES-NI on x86-32 really might be the way to go. > > > > That would really suck for users of encrypted hard disks. Peter, do you really think there are that many ? I think I only saw AES-NI on recent 64-bit capable chips, and it's been a while that users have been installing 64-bit distros on such machines. Note that I'm not advocating for breaking existing setups, just that I'm surprized by this combination (aes-ni + 32-bit). Willy