mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: jolsa@redhat.com
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] tracing - correct module boundaries for ftrace_release
Date: Wed, 07 Oct 2009 13:14:03 -0400	[thread overview]
Message-ID: <1254935643.1696.172.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1254934835-363-3-git-send-email-jolsa@redhat.com>

On Wed, 2009-10-07 at 19:00 +0200, jolsa@redhat.com wrote:
> When the module is about the unload we release its call records.
> The ftrace_release function was given wrong values representing
> the module core boundaries, thus not releasing its call records.
> 
> Plus making ftrace_release function module specific.
> 

I'll take this version. Thanks! I'll get this ready for mainline urgent,
as well as push it off to stable.

-- Steve

> wbr,
> jirka
> 
> 
> Signed-off-by: Jiri Olsa <jolsa@redhat.com>
> ---
>  include/linux/ftrace.h |    2 +-
>  kernel/trace/ftrace.c  |   12 ++++--------
>  2 files changed, 5 insertions(+), 9 deletions(-)
> 
> diff --git a/include/linux/ftrace.h b/include/linux/ftrace.h
> index cd3d2ab..0b4f97d 100644
> --- a/include/linux/ftrace.h
> +++ b/include/linux/ftrace.h
> @@ -241,7 +241,7 @@ extern void ftrace_enable_daemon(void);
>  # define ftrace_set_filter(buf, len, reset)	do { } while (0)
>  # define ftrace_disable_daemon()		do { } while (0)
>  # define ftrace_enable_daemon()			do { } while (0)
> -static inline void ftrace_release(void *start, unsigned long size) { }
> +static inline void ftrace_release_mod(struct module *mod) {}
>  static inline int register_ftrace_command(struct ftrace_func_command *cmd)
>  {
>  	return -EINVAL;
> diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
> index 9a72853..559e552 100644
> --- a/kernel/trace/ftrace.c
> +++ b/kernel/trace/ftrace.c
> @@ -2608,19 +2608,17 @@ static int ftrace_convert_nops(struct module *mod,
>  }
>  
>  #ifdef CONFIG_MODULES
> -void ftrace_release(void *start, void *end)
> +void ftrace_release_mod(struct module *mod)
>  {
>  	struct dyn_ftrace *rec;
>  	struct ftrace_page *pg;
> -	unsigned long s = (unsigned long)start;
> -	unsigned long e = (unsigned long)end;
>  
> -	if (ftrace_disabled || !start || start == end)
> +	if (ftrace_disabled)
>  		return;
>  
>  	mutex_lock(&ftrace_lock);
>  	do_for_each_ftrace_rec(pg, rec) {
> -		if ((rec->ip >= s) && (rec->ip < e)) {
> +		if (within_module_core(rec->ip, mod)) {
>  			/*
>  			 * rec->ip is changed in ftrace_free_rec()
>  			 * It should not between s and e if record was freed.
> @@ -2652,9 +2650,7 @@ static int ftrace_module_notify(struct notifier_block *self,
>  				   mod->num_ftrace_callsites);
>  		break;
>  	case MODULE_STATE_GOING:
> -		ftrace_release(mod->ftrace_callsites,
> -			       mod->ftrace_callsites +
> -			       mod->num_ftrace_callsites);
> +		ftrace_release_mod(mod);
>  		break;
>  	}
>  


  reply	other threads:[~2009-10-07 17:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-07 17:00 [PATCH 0/2] tracing - wrong scale in ftrace_release jolsa
2009-10-07 17:00 ` [PATCH 1/2] tracing - correct module boundaries for ftrace_release jolsa
2009-10-07 17:00 ` [PATCH 2/2] " jolsa
2009-10-07 17:14   ` Steven Rostedt [this message]
2009-10-08 13:47   ` [tip:tracing/urgent] tracing: " tip-bot for jolsa@redhat.com

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=1254935643.1696.172.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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®