Re: Kernel oops with 2.6.26, padlock and ipsec: probably problem with fpu state changes

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Suresh Siddha <suresh.b.siddha@...>
Cc: H. Peter Anvin <hpa@...>, Wolfgang Walter <wolfgang.walter@...>, netdev@vger.kernel.org <netdev@...>, linux-kernel@vger.kernel.org <linux-kernel@...>, Ingo Molnar <mingo@...>, viro@ZenIV.linux.org.uk <viro@...>, vegard.nossum@gmail.com <vegard.nossum@...>, austin zhang <austin_zhang@...>
Date: Saturday, August 9, 2008 - 10:29 am

On Sat, Aug 09, 2008 at 08:38:30AM +0800, Herbert Xu wrote:

OK I take that back, Intel (and AMD) processors are equally affected
by this.  For a start, the newly added Intel crc32c driver suffers
from exactly the same problem since the instruction used is also
SSE.

According to

	http://softwarecommunity.intel.com/articles/eng/3788.htm

the Intel AES instructions are also SSE so they too will suffer
from this.

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: Kernel oops with 2.6.26, padlock and ipsec: probably pro..., Herbert Xu, (Sat Aug 9, 10:29 am)