Messages in this thread | | | Date | Sat, 9 Aug 2008 11:54:13 -0700 | From | Suresh Siddha <> | Subject | Re: Kernel oops with 2.6.26, padlock and ipsec: probably problem with fpu state changes |
| |
On Sat, Aug 09, 2008 at 11:12:19AM -0700, Suresh Siddha wrote: > In this padlock case with the patch, we may encounter a nested > kernel_fpu_begin() and end() > but this is ok, as the padlock is not actually touching fpu/sse registers.
I take this back. kernel_fpu_end() is unconditionally doing stts(). So, nesting of kernel_fpu_begin/end() is not ok.
| |