All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Petr Mladek <pmladek@suse.cz>
Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	"David S. Miller" <davem@davemloft.net>,
	Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
	Ananth NMavinakayanahalli <ananth@in.ibm.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ingo Molnar <mingo@redhat.com>, Jiri Kosina <jkosina@suse.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] kprobes: Disable Kprobe when ftrace arming fails
Date: Mon, 23 Mar 2015 09:54:26 +0100	[thread overview]
Message-ID: <20150323085426.GB28965@gmail.com> (raw)
In-Reply-To: <1426860127-7896-1-git-send-email-pmladek@suse.cz>


* Petr Mladek <pmladek@suse.cz> wrote:

> arm_kprobe_ftrace() could fail, especially after introducing ftrace 
> IPMODIFY flag and LifePatching. But this situation is not properly 
> handled.

s/LifePatching/LivePatching?

Why not fix live patching to still allow kprobes that worked before?

Thanks,

	Ingo

  reply	other threads:[~2015-03-23  8:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20 14:02 [PATCH v3] kprobes: Disable Kprobe when ftrace arming fails Petr Mladek
2015-03-23  8:54 ` Ingo Molnar [this message]
2015-03-23 10:12   ` Petr Mladek
2015-03-23 10:33     ` Ingo Molnar
2015-03-23 12:39       ` Petr Mladek
2015-03-23 13:30         ` Steven Rostedt
2015-03-23 13:34           ` Ingo Molnar
2015-03-23 13:43             ` Steven Rostedt
2015-03-23 13:53               ` Ingo Molnar
2015-03-23 13:58                 ` Steven Rostedt
2015-03-23 16:38                   ` Petr Mladek
2015-03-23 16:43               ` Paul E. McKenney
2015-03-23 23:32                 ` Jiri Kosina
2015-03-23 22:36             ` Jiri Kosina
2015-03-24  7:59               ` Petr Mladek
2015-03-24 13:36                 ` Steven Rostedt

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=20150323085426.GB28965@gmail.com \
    --to=mingo@kernel.org \
    --cc=ananth@in.ibm.com \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=davem@davemloft.net \
    --cc=fweisbec@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@redhat.com \
    --cc=pmladek@suse.cz \
    --cc=rostedt@goodmis.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.