From: "H. Peter Anvin" <hpa@linux.intel.com>
To: mingo@kernel.org, hpa@zytor.com, linux-kernel@vger.kernel.org,
jkosina@suse.cz, masami.hiramatsu.pt@hitachi.com,
rostedt@goodmis.org, tglx@linutronix.de, hpa@linux.intel.com,
fengguang.wu@intel.com
Cc: tip-bot for Jiri Kosina <tipbot@zytor.com>,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/core] kprobes/x86: Call out into INT3 handler directly instead of using notifier
Date: Wed, 24 Jul 2013 07:33:12 -0700 [thread overview]
Message-ID: <51EFE5A8.1060109@linux.intel.com> (raw)
In-Reply-To: <tip-17f41571bb2c4a398785452ac2718a6c5d77180e@git.kernel.org>
On 07/23/2013 08:55 PM, tip-bot for Jiri Kosina wrote:
> Commit-ID: 17f41571bb2c4a398785452ac2718a6c5d77180e
> Gitweb: http://git.kernel.org/tip/17f41571bb2c4a398785452ac2718a6c5d77180e
> Author: Jiri Kosina <jkosina@suse.cz>
> AuthorDate: Tue, 23 Jul 2013 10:09:28 +0200
> Committer: Ingo Molnar <mingo@kernel.org>
> CommitDate: Tue, 23 Jul 2013 10:12:57 +0200
>
> kprobes/x86: Call out into INT3 handler directly instead of using notifier
>
> In fd4363fff3d96 ("x86: Introduce int3 (breakpoint)-based
> instruction patching"), the mechanism that was introduced for
> notifying alternatives code from int3 exception handler that and
> exception occured was die_notifier.
>
> This is however problematic, as early code might be using jump
> labels even before the notifier registration has been performed,
> which will then lead to an oops due to unhandled exception. One
> of such occurences has been encountered by Fengguang:
>
Please note that putting this patch in perf/core means x86/jumplabel is
completely nonfunctional by itself.
-hpa
next prev parent reply other threads:[~2013-07-24 14:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-20 13:12 [x86] Kernel panic - not syncing: Fatal exception in interrupt Fengguang Wu
2013-07-21 0:23 ` H. Peter Anvin
2013-07-21 8:30 ` Jiri Kosina
2013-07-21 16:21 ` Fengguang Wu
2013-07-21 17:21 ` H. Peter Anvin
2013-07-22 11:18 ` Jiri Kosina
2013-07-22 1:07 ` Fengguang Wu
2013-07-22 11:14 ` [PATCH -tip/x86/jumplabel] x86: call out into int3 handler directly instead of using notifier Jiri Kosina
2013-07-22 11:24 ` Masami Hiramatsu
2013-07-22 20:53 ` H. Peter Anvin
2013-07-22 21:00 ` Jiri Kosina
2013-07-23 1:24 ` Masami Hiramatsu
2013-07-23 7:45 ` Ingo Molnar
2013-07-23 8:09 ` Jiri Kosina
2013-07-24 3:55 ` [tip:perf/core] kprobes/x86: Call out into INT3 " tip-bot for Jiri Kosina
2013-07-24 14:33 ` H. Peter Anvin [this message]
2013-07-29 9:06 ` Jiri Kosina
2013-07-29 9:14 ` H. Peter Anvin
2013-07-29 9:18 ` Jiri Kosina
2013-07-29 9:23 ` H. Peter Anvin
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=51EFE5A8.1060109@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=fengguang.wu@intel.com \
--cc=hpa@zytor.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tipbot@zytor.com \
/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.