On Wed, Feb 22, 2012 at 1:19 PM, Greg Kroah-Hartman
<[email protected]> 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 stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
