On 01/15, Rik van Riel wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 01/15/2015 02:20 PM, Oleg Nesterov wrote: > > math_state_restore() can race with kernel_fpu_begin() if irq comes > > right after __thread_fpu_begin(), __save_init_fpu() will overwrite > > fpu->state we are going to restore. > > > > Add 2 simple helpers, kernel_fpu_disable() and kernel_fpu_enable() > > which simply set/clear in_kernel_fpu, and change > > math_state_restore() to exclude kernel_fpu_begin() in between. > > > > Alternatively we could use local_irq_save/restore, but probably > > these new helpers can have more users. > > > > Perhaps they should disable/enable preemption themselves, in this > > case we can remove preempt_disable() in __restore_xstate_sig(). > > Given that math_state_restore does an implicit preempt_disable > through local_irq_disable,
Not really. do_device_not_available() calls it with irqs disabled, __restore_xstate_sig() calls it under preempt_disable(). > I am not sure whether adding an > explicit preempt_disable would be good or bad. Me too, but this code needs cleanups in any case imo, lets do this later. > Reviewed-by: Rik van Riel <r...@redhat.com> Thanks! I'll try to send another short series today, we need to remove __thread_has_fpu() from interrupted_kernel_fpu_idle() before we add TIF_LOAD_FPU. Oleg. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/