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

[Herbert Xu]

On Mon, Aug 11, 2008 at 01:19:01PM -0700, Suresh Siddha wrote:
.
> we can't unconditionally do clts() in the process context. We have
> to disable pre-emption to avoid interactions with context switch and
> lazy restore. So there will be RT latency issues aswell.

Yes disabling preemption is the real killer.

This is just a quick band-aid.  Longer term we should add a task
flag that indicates the task is currently doing kernel FPU which
will tell the scheduler to clear TS the next time it's run.  That
way we won't need to disable preemtion or pollute the user task's
FPU used state.

Thanks,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx>
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 linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/