From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933435AbcLWJYl (ORCPT ); Fri, 23 Dec 2016 04:24:41 -0500 Received: from mx2.suse.de ([195.135.220.15]:56116 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750781AbcLWJYj (ORCPT ); Fri, 23 Dec 2016 04:24:39 -0500 Date: Fri, 23 Dec 2016 10:24:35 +0100 (CET) From: Miroslav Benes To: Josh Poimboeuf cc: Petr Mladek , Jessica Yu , Jiri Kosina , Linux Kernel Mailing List , live-patching@vger.kernel.org, Michael Ellerman , Heiko Carstens , x86@kernel.org, linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org, Vojtech Pavlik , Jiri Slaby , Chris J Arges , Andy Lutomirski , Ingo Molnar , Peter Zijlstra Subject: Re: [PATCH v3 13/15] livepatch: change to a per-task consistency model In-Reply-To: <20161221212505.dbxeddu2skmjmwiq@treble> Message-ID: References: <20161220173246.GC25166@pathway.suse.cz> <20161221212505.dbxeddu2skmjmwiq@treble> User-Agent: Alpine 2.20 (LSU 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > > diff --git a/kernel/livepatch/patch.c b/kernel/livepatch/patch.c > > > index 5efa262..e79ebb5 100644 > > > --- a/kernel/livepatch/patch.c > > > +++ b/kernel/livepatch/patch.c > > > @@ -29,6 +29,7 @@ > > > #include > > > #include > > > #include "patch.h" > > > +#include "transition.h" > > > > > > static LIST_HEAD(klp_ops); > > > > > > @@ -54,15 +55,53 @@ static void notrace klp_ftrace_handler(unsigned long ip, > > > { > > > struct klp_ops *ops; > > > struct klp_func *func; > > > + int patch_state; > > > > > > ops = container_of(fops, struct klp_ops, fops); > > > > > > rcu_read_lock(); > > > + > > > func = list_first_or_null_rcu(&ops->func_stack, struct klp_func, > > > stack_node); > > > - if (WARN_ON_ONCE(!func)) > > > + > > > + if (!func) > > > goto unlock; > > > > Why do you removed the WARN_ON_ONCE(), please? > > > > We still add the function on the stack before registering > > the ftrace handler. Also we unregister the ftrace handler > > before removing the the last entry from the stack. > > > > AFAIK, unregister_ftrace_function() calls rcu_synchronize()' > > to make sure that no-one is inside the handler once finished. > > Mirek knows more about it. > > Hm, this is news to me. Mirek, please share :-) Well, I think the whole thing is well described in emails I exchanged with Steven few months ago. See [1]. [1] http://lkml.kernel.org/r/alpine.LNX.2.00.1608081041060.10833@pobox.suse.cz > > If this is not true, we have a problem. For example, > > we call kfree(ops) after unregister_ftrace_function(); > > Agreed. TL;DR - we should be ok as long as we do not do crazy things in the handler, deliberate sleeping for example. WARN_ON_ONCE() may be crazy too. I think we discussed it long ago and we came to an agreement to remove it. Miroslav, very slowly going through the patch set