From: NAMIT GUPTA <gupta.namit@samsung.com>
To: "rostedt@goodmis.org" <rostedt@goodmis.org>
Cc: "mingo@redhat.com" <mingo@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
PANKAJ MISHRA <pankaj.m@samsung.com>,
AMIT SAHRAWAT <a.sahrawat@samsung.com>
Subject: RE: [PATCH v2] ftrace/module: Move ftrace_release_mod to ddebug_cleanup label
Date: Thu, 28 Dec 2017 05:14:19 +0000 [thread overview]
Message-ID: <20171228051419epcms5p1ba575801dccdf1ebbefa956a80be231d@epcms5p1> (raw)
In-Reply-To: <1513079672-13652-1-git-send-email-gupta.namit@samsung.com>
Hello Steve,
As per the discussion I sent patch v2.
Please find.
Thanks,
Namit Gupta
--------- Original Message ---------
Sender : NAMIT GUPTA <gupta.namit@samsung.com> ./Senior Chief Engineer/SRI-Delhi-Platform S/W 1 Team/Samsung Electronics
Date : 2017-12-12 17:29 (GMT+5:30)
Title : [PATCH v2] ftrace/module: Move ftrace_release_mod to ddebug_cleanup label
ftrace_module_init happen after dynamic_debug_setup, it is desired that
cleanup should be called after this label however in current implementation
it is called in free module label,ie:even though ftrace in not initialized,
from so many fail case ftrace_release_mod() will be called and unnecessary
traverse the whole list.
In below patch we moved ftrace_release_mod() from free_module label to
ddebug_cleanup label. that is the best possible location, other solution
is to make new label to ftrace_release_mod() but since ftrace_module_init()
is not return with minimum changes it should be in ddebug_cleanup label.
Signed-off-by: Namit Gupta <gupta.namit@samsung.com>
---
kernel/module.c | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/kernel/module.c b/kernel/module.c
index 0d1cb8d..4be966a 100644
--- a/kernel/module.c
+++ b/kernel/module.c
@@ -3523,6 +3523,7 @@ static int load_module(struct load_info *info, const char __user *uargs,
unset_module_core_ro_nx(mod);
ddebug_cleanup:
+ ftrace_release_mod(mod);
dynamic_debug_remove(info->debug);
synchronize_sched();
kfree(mod->args);
@@ -3541,12 +3542,6 @@ static int load_module(struct load_info *info, const char __user *uargs,
synchronize_rcu();
mutex_unlock(&module_mutex);
free_module:
- /*
- * Ftrace needs to clean up what it initialized.
- * This does nothing if ftrace_module_init() wasn't called,
- * but it must be called outside of module_mutex.
- */
- ftrace_release_mod(mod);
/* Free lock-classes; relies on the preceding sync_rcu() */
lockdep_free_key_range(mod->module_core, mod->core_size);
--
1.9.1
next prev parent reply other threads:[~2017-12-28 6:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20171212115859epcas5p1c80cacda05c36d4ef2607df2450d4aa3@epcas5p1.samsung.com>
2017-12-12 11:54 ` Namit Gupta
[not found] ` <CGME20171212115859epcas5p1c80cacda05c36d4ef2607df2450d4aa3@epcms5p1>
2017-12-28 5:14 ` NAMIT GUPTA [this message]
2017-12-28 16:28 ` Steven Rostedt
2017-12-28 16:32 ` Steven Rostedt
2017-12-29 0:36 ` Jessica Yu
2017-12-29 0:57 ` Steven Rostedt
2017-12-29 1:02 ` Jessica Yu
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=20171228051419epcms5p1ba575801dccdf1ebbefa956a80be231d@epcms5p1 \
--to=gupta.namit@samsung.com \
--cc=a.sahrawat@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pankaj.m@samsung.com \
--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 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®