From: Waiman Long <waiman.long@hp.com>
To: mingo@kernel.org, hpa@zytor.com, linux-kernel@vger.kernel.org,
waiman.long@hp.com, torvalds@linux-foundation.org,
peterz@infradead.org, acme@ghostprotocols.net,
luto@amacapital.net, akpm@linux-foundation.org,
tglx@linutronix.de, scott.norton@hp.com, aswin@hp.com
Cc: tip-bot for Peter Zijlstra <tipbot@zytor.com>,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/core] x86, mm, perf: Allow recursive faults from interrupts
Date: Fri, 17 Jan 2014 13:10:06 -0500 [thread overview]
Message-ID: <52D971FE.9030008@hp.com> (raw)
In-Reply-To: <tip-c026b3591e4f2a4993df773183704bb31634e0bd@git.kernel.org>
On 01/16/2014 08:39 AM, tip-bot for Peter Zijlstra wrote:
> Commit-ID: c026b3591e4f2a4993df773183704bb31634e0bd
> Gitweb: http://git.kernel.org/tip/c026b3591e4f2a4993df773183704bb31634e0bd
> Author: Peter Zijlstra<peterz@infradead.org>
> AuthorDate: Fri, 10 Jan 2014 21:06:03 +0100
> Committer: Ingo Molnar<mingo@kernel.org>
> CommitDate: Thu, 16 Jan 2014 09:19:48 +0100
>
> x86, mm, perf: Allow recursive faults from interrupts
>
> Waiman managed to trigger a PMI while in a emulate_vsyscall() fault,
> the PMI in turn managed to trigger a fault while obtaining a stack
> trace. This triggered the sig_on_uaccess_error recursive fault logic
> and killed the process dead.
>
> Fix this by explicitly excluding interrupts from the recursive fault
> logic.
>
> Reported-and-Tested-by: Waiman Long<waiman.long@hp.com>
> Fixes: e00b12e64be9 ("perf/x86: Further optimize copy_from_user_nmi()")
> Cc: Aswin Chandramouleeswaran<aswin@hp.com>
> Cc: Scott J Norton<scott.norton@hp.com>
> Cc: Linus Torvalds<torvalds@linux-foundation.org>
> Cc: Andy Lutomirski<luto@amacapital.net>
> Cc: Arnaldo Carvalho de Melo<acme@ghostprotocols.net>
> Cc: Andrew Morton<akpm@linux-foundation.org>
> Signed-off-by: Peter Zijlstra<peterz@infradead.org>
> Link: http://lkml.kernel.org/r/20140110200603.GJ7572@laptop.programming.kicks-ass.net
> Signed-off-by: Ingo Molnar<mingo@kernel.org>
> ---
> arch/x86/mm/fault.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
>
Will that be picked up by Linus as it is a 3.13 regression?
-Longman
next prev parent reply other threads:[~2014-01-17 18:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 15:29 SIGSEGV when using "perf record -g" with 3.13-rc* kernel Waiman Long
2014-01-10 16:58 ` Peter Zijlstra
2014-01-10 17:02 ` Peter Zijlstra
2014-01-10 17:41 ` Peter Zijlstra
2014-01-10 18:54 ` Andy Lutomirski
2014-01-10 19:43 ` Waiman Long
2014-01-10 19:56 ` Andy Lutomirski
2014-01-10 20:12 ` Peter Zijlstra
2014-01-10 20:06 ` Peter Zijlstra
2014-01-10 20:28 ` Andy Lutomirski
2014-01-15 15:33 ` Waiman Long
2014-01-16 13:39 ` [tip:perf/core] x86, mm, perf: Allow recursive faults from interrupts tip-bot for Peter Zijlstra
2014-01-17 18:10 ` Waiman Long [this message]
2014-01-17 19:17 ` Andy Lutomirski
2014-01-17 20:08 ` Waiman Long
2014-01-17 21:07 ` Andy Lutomirski
2014-01-10 19:37 ` SIGSEGV when using "perf record -g" with 3.13-rc* kernel Waiman Long
2014-01-10 20:10 ` Peter Zijlstra
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=52D971FE.9030008@hp.com \
--to=waiman.long@hp.com \
--cc=acme@ghostprotocols.net \
--cc=akpm@linux-foundation.org \
--cc=aswin@hp.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=scott.norton@hp.com \
--cc=tglx@linutronix.de \
--cc=tipbot@zytor.com \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.