mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Jiri Kosina <jikos@kernel.org>
Cc: Jessica Yu <jeyu@redhat.com>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	Seth Jennings <sjenning@redhat.com>,
	Vojtech Pavlik <vojtech@suse.com>,
	Miroslav Benes <mbenes@suse.cz>, Petr Mladek <pmladek@suse.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Ingo Molnar <mingo@redhat.com>,
	live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] ftrace/module: remove ftrace module notifier
Date: Wed, 17 Feb 2016 15:36:33 -0500	[thread overview]
Message-ID: <20160217153633.231ea651@gandalf.local.home> (raw)
In-Reply-To: <alpine.LNX.2.00.1602172133240.22700@cbobk.fhfr.pm>

On Wed, 17 Feb 2016 21:35:29 +0100 (CET)
Jiri Kosina <jikos@kernel.org> wrote:

> On Tue, 16 Feb 2016, Jessica Yu wrote:
> 
> > Remove the ftrace module notifier in favor of directly calling
> > ftrace_module_enable() and ftrace_release_mod() in the module loader.
> > Hard-coding the function calls directly in the module loader removes
> > dependence on the module notifier call chain and provides better
> > visibility and control over what gets called when, which is important
> > to kernel utilities such as livepatch.
> > 
> > This fixes a notifier ordering issue in which the ftrace module notifier
> > (and hence ftrace_module_enable()) for coming modules was being called
> > after klp_module_notify(), which caused livepatch modules to initialize
> > incorrectly. This patch removes dependence on the module notifier call
> > chain in favor of hard coding the corresponding function calls in the
> > module loader. This ensures that ftrace and livepatch code get called in
> > the correct order on patch module load and unload.
> > 
> > Fixes: 5156dca34a3e ("ftrace: Fix the race between ftrace and insmod")
> > Signed-off-by: Jessica Yu <jeyu@redhat.com>
> > Reviewed-by: Steven Rostedt <rostedt@goodmis.org>  
> 
> Steven, I am going to assume that your Reviewed-by: still holds for the 
> patch even though it has been removed from the 4-patch series; if you 
> don't agree, please speak up. Otherwise, I am going to apply it and push 
> it to Linus for -rc5 still (as it fixes our regression).
> 

This week has been very busy. Did the patch change at all?

-- Steve

  reply	other threads:[~2016-02-17 20:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 22:32 Jessica Yu
2016-02-17  2:35 ` Josh Poimboeuf
2016-02-17  8:34 ` Miroslav Benes
2016-02-17 20:35 ` Jiri Kosina
2016-02-17 20:36   ` Steven Rostedt [this message]
2016-02-17 20:44     ` Jiri Kosina
2016-02-17 21:03       ` Steven Rostedt
2016-02-17 21:17 ` Jiri Kosina

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=20160217153633.231ea651@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=jeyu@redhat.com \
    --cc=jikos@kernel.org \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=live-patching@vger.kernel.org \
    --cc=mbenes@suse.cz \
    --cc=mingo@redhat.com \
    --cc=pmladek@suse.com \
    --cc=rusty@rustcorp.com.au \
    --cc=sjenning@redhat.com \
    --cc=vojtech@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®