mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Jiri Olsa <jolsa@redhat.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org
Subject: Re: x86: Allow vmalloc faults from NMI context
Date: Thu, 10 Apr 2014 15:40:51 -0400	[thread overview]
Message-ID: <20140410154051.4d709272@gandalf.local.home> (raw)
In-Reply-To: <20140410144003.GF13658@twins.programming.kicks-ass.net>

On Thu, 10 Apr 2014 16:40:03 +0200
Peter Zijlstra <peterz@infradead.org> wrote:

> Jiri reported he hit vmalloc_faults()'s:
> 
>   WARN_ON_ONCE(in_nmi());
> 
> The patch that added this ebc8827f75954 ("x86: Barf when vmalloc and
> kmemcheck faults happen in NMI") explains that this was done in order to
> avoid faults from NMI to cause nested NMIs.
> 
> We have, however, completely fixed this issue and can now safely take
> faults from NMI context.
> 
> Therefore remove this warning. We must still leave the kmemcheck warn in
> place since kmemcheck itself can't deal with NMI context yet.
> 

Yay, finally....

Link: http://lkml.kernel.org/p/20131015163906.342d8ffa@gandalf.local.home

-- Steve

> Signed-off-by: Peter Zijlstra <peterz@infradead.org>
> ---
>  arch/x86/mm/fault.c | 4 ----
>  1 file changed, 4 deletions(-)
> 
> diff --git a/arch/x86/mm/fault.c b/arch/x86/mm/fault.c
> index 8e5722992677..d0234cdf70f1 100644
> --- a/arch/x86/mm/fault.c
> +++ b/arch/x86/mm/fault.c
> @@ -271,8 +271,6 @@ static noinline __kprobes int vmalloc_fault(unsigned long address)
>  	if (!(address >= VMALLOC_START && address < VMALLOC_END))
>  		return -1;
>  
> -	WARN_ON_ONCE(in_nmi());
> -
>  	/*
>  	 * Synchronize this task's top level page-table
>  	 * with the 'reference' page table.
> @@ -369,8 +367,6 @@ static noinline __kprobes int vmalloc_fault(unsigned long address)
>  	if (!(address >= VMALLOC_START && address < VMALLOC_END))
>  		return -1;
>  
> -	WARN_ON_ONCE(in_nmi());
> -
>  	/*
>  	 * Copy kernel mappings over when needed. This can also
>  	 * happen within a race in page table update. In the later


      reply	other threads:[~2014-04-10 19:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10 14:40 Peter Zijlstra
2014-04-10 19:40 ` Steven Rostedt [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140410154051.4d709272@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=fweisbec@gmail.com \
    --cc=hpa@zytor.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®