On Fri, Nov 24, 2017 at 06:23:44PM +0100, Ingo Molnar wrote:
> From: Andy Lutomirski <l...@kernel.org>
>
> That race has been fixed and code cleaned up for a while now.
>
> Signed-off-by: Andy Lutomirski <l...@kernel.org>
> Signed-off-by: Thomas Gleixner <t...@linutronix.de>
> Cc: Borislav Petkov <bpet...@suse.de>
> Cc: Brian Gerst <brge...@gmail.com>
> Cc: Dave Hansen <dave.han...@intel.com>
> Cc: Josh Poimboeuf <jpoim...@redhat.com>
> Cc: Linus Torvalds <torva...@linux-foundation.org>
> Cc: Peter Zijlstra <pet...@infradead.org>
> Link:
> https://lkml.kernel.org/r/12e75976dbbb7ece2b0a64238f1d3892dfed1e16.1511497875.git.l...@kernel.org
> Signed-off-by: Ingo Molnar <mi...@kernel.org>
> ---
> arch/x86/kernel/irq.c | 12 ------------
> 1 file changed, 12 deletions(-)
>
> diff --git a/arch/x86/kernel/irq.c b/arch/x86/kernel/irq.c
> index 49cfd9fe7589..68e1867cca80 100644
> --- a/arch/x86/kernel/irq.c
> +++ b/arch/x86/kernel/irq.c
> @@ -219,18 +219,6 @@ __visible unsigned int __irq_entry do_IRQ(struct pt_regs
> *regs)
> /* high bit used in ret_from_ code */
> unsigned vector = ~regs->orig_ax;
>
> - /*
> - * NB: Unlike exception entries, IRQ entries do not reliably
> - * handle context tracking in the low-level entry code. This is
> - * because syscall entries execute briefly with IRQs on before
> - * updating context tracking state, so we can take an IRQ from
> - * kernel mode with CONTEXT_USER. The low-level entry code only
> - * updates the context if we came from user mode, so we won't
> - * switch to CONTEXT_KERNEL. We'll fix that once the syscall
> - * code is cleaned up enough that we can cleanly defer enabling
> - * IRQs.
> - */
> -
> entering_irq();
>
> /* entering_irq() tells RCU that we're not quiescent. Check it. */
> --
Reviewed-by: Borislav Petkov <b...@suse.de>
Also, fixes like that should move to the top of the patchset.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
