Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754967Ab2BVV3e (ORCPT ); Wed, 22 Feb 2012 16:29:34 -0500 Received: from mail-we0-f174.google.com ([74.125.82.174]:59597 "EHLO mail-we0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752536Ab2BVV3c convert rfc822-to-8bit (ORCPT ); Wed, 22 Feb 2012 16:29:32 -0500 MIME-Version: 1.0 In-Reply-To: <20120222211928.GA4448@kroah.com> References: <20120222211928.GA4448@kroah.com> From: Linus Torvalds Date: Wed, 22 Feb 2012 13:29:11 -0800 X-Google-Sender-Auth: ggbKezzBGgEEiduDG0ujD-93Ims Message-ID: Subject: Re: [PATCH 0/5] i387: stable kernel backport To: Greg Kroah-Hartman Cc: stable@vger.kernel.org, Raphael Prevost , Suresh Siddha , Peter Anvin , Linux Kernel Mailing List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1003 Lines: 25 On Wed, Feb 22, 2012 at 1:19 PM, Greg Kroah-Hartman wrote: > > Thanks for doing the backport. ?Any ideas on how far back this problem > goes? The fundamental bug goes back forever, but happily afaik you can only *trigger* it by doing FPU accesses from interrupts, and nobody did that until the AES-NI instructions came about. So practically speaking it goes back to the introduction of CRYPTO_AES_NI_INTEL, in commit 54b6a1bd5364 ("crypto: aes-ni - Add support to Intel AES-NI instructions for x86_64 platform"). Which was merged into 2.6.30. So it still goes back pretty far. The good news is that I *think* the whole i387 handling code hasn't been touched much. But I didn't really check deeply. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/