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@...>
Date: Saturday, August 9, 2008 - 9:31 am

On Fri, Aug 08, 2008 at 04:11:21PM -0700, Suresh Siddha wrote:

Even if there wasn't one before, there is going to be one now
because as you pointed out yourself, if we get an inbound IPsec
packet between any kernel_fpu_begin/kernel_fpu_end area, we could
get a nested kernel_fpu_end which puts us back to square one wrt
to the original race.

So clearly we need to think more about this issue.

Unless we can come up with a new solution quickly, I recommend
that we back out the FPU changes.

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, 9:31 am)