From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932070AbbCWNxQ (ORCPT <rfc822;w@1wt.eu>);
	Mon, 23 Mar 2015 09:53:16 -0400
Received: from mail-wi0-f178.google.com ([209.85.212.178]:35629 "EHLO
	mail-wi0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752451AbbCWNxL (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 23 Mar 2015 09:53:11 -0400
Date: Mon, 23 Mar 2015 14:53:06 +0100
From: Ingo Molnar <mingo@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Petr Mladek <pmladek@suse.cz>,
        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>,
        Ingo Molnar <mingo@redhat.com>, Jiri Kosina <jkosina@suse.cz>,
        linux-kernel@vger.kernel.org,
        "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH v3] kprobes: Disable Kprobe when ftrace arming fails
Message-ID: <20150323135306.GA25233@gmail.com>
References: <1426860127-7896-1-git-send-email-pmladek@suse.cz>
 <20150323085426.GB28965@gmail.com>
 <20150323101253.GN11869@pathway.suse.cz>
 <20150323103327.GA12213@gmail.com>
 <20150323123955.GE15177@pathway.suse.cz>
 <20150323093013.15b6070b@gandalf.local.home>
 <20150323133442.GC23145@gmail.com>
 <20150323094317.38dcb601@gandalf.local.home>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150323094317.38dcb601@gandalf.local.home>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


* Steven Rostedt <rostedt@goodmis.org> wrote:

> On Mon, 23 Mar 2015 14:34:42 +0100
> Ingo Molnar <mingo@kernel.org> wrote:
> > 
> > Even if it was documented (it isn't), it's pretty weird terminology - 
> > please use clearer formulations, like 'patched function' or 'unpatched 
> > function' or 'function with pending patch'. No need to redefine 
> > existing words in a weird fashion just to create the appearance of 
> > being special ...
> > 
> 
> I think it has to do with their RCU like patching functionality, 
> where some tasks are still executing the old function and others are 
> executing the new function. [...]

That would be the 'function with pending patch' state in my 
description above.

Thanks,

	Ingo