From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Jessica Yu <jeyu@redhat.com>
Cc: Seth Jennings <sjenning@redhat.com>,
Jiri Kosina <jikos@kernel.org>, Vojtech Pavlik <vojtech@suse.com>,
Miroslav Benes <mbenes@suse.cz>,
Rusty Russell <rusty@rustcorp.com.au>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] ftrace/module: remove ftrace module notifier
Date: Mon, 8 Feb 2016 11:31:54 -0600 [thread overview]
Message-ID: <20160208173154.GA23106@treble.redhat.com> (raw)
In-Reply-To: <1454728097-7106-2-git-send-email-jeyu@redhat.com>
On Fri, Feb 05, 2016 at 10:08:16PM -0500, 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.
>
> Signed-off-by: Jessica Yu <jeyu@redhat.com>
This is also fixing the bug described in the cover letter, so it would
be good to add a description of that here and a corresponding "Fixes:"
tag.
--
Josh
next prev parent reply other threads:[~2016-02-08 17:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 3:08 [PATCH v3 0/2] Fix ordering of ftrace/livepatch calls on module load and unload Jessica Yu
2016-02-06 3:08 ` [PATCH v3 1/2] ftrace/module: remove ftrace module notifier Jessica Yu
2016-02-08 14:18 ` Petr Mladek
2016-02-08 17:31 ` Josh Poimboeuf [this message]
2016-02-06 3:08 ` [PATCH v3 2/2] livepatch/module: remove livepatch " Jessica Yu
2016-02-08 14:30 ` Petr Mladek
2016-02-08 17:48 ` [PATCH v3 0/2] Fix ordering of ftrace/livepatch calls on module load and unload Josh Poimboeuf
2016-02-08 17:58 ` Jessica Yu
2016-02-08 18:00 ` 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=20160208173154.GA23106@treble.redhat.com \
--to=jpoimboe@redhat.com \
--cc=jeyu@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--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 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.