public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
	Tom Zanussi <tzanussi@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] tracing/filters: allow user-input to be integer-like string
Date: Mon, 13 Apr 2009 16:45:15 +0200	[thread overview]
Message-ID: <20090413144513.GF5977@nowhere> (raw)
In-Reply-To: <49E2A594.4060306@cn.fujitsu.com>

On Mon, Apr 13, 2009 at 10:38:12AM +0800, Li Zefan wrote:
> Suppose we would like to trace all tasks named '123', but this
> will fail:
>  # echo 'parent_comm == 123' > events/sched/sched_process_fork/filter
>  bash: echo: write error: Invalid argument
> 
> Don't guess the type of the filter pred in filter_parse(), but instead
> we check it in filter_add_pred().
> 
> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
> ---
>  kernel/trace/trace_events_filter.c |   26 +++++++++++++-------------
>  1 files changed, 13 insertions(+), 13 deletions(-)
> 
> diff --git a/kernel/trace/trace_events_filter.c b/kernel/trace/trace_events_filter.c
> index 9f8ecca..a63f965 100644
> --- a/kernel/trace/trace_events_filter.c
> +++ b/kernel/trace/trace_events_filter.c
> @@ -229,6 +229,7 @@ static int is_string_field(const char *type)
>  int filter_add_pred(struct ftrace_event_call *call, struct filter_pred *pred)
>  {
>  	struct ftrace_event_field *field;
> +	unsigned long long val;
>  
>  	field = find_event_field(call, pred->field_name);
>  	if (!field)
> @@ -237,14 +238,14 @@ int filter_add_pred(struct ftrace_event_call *call, struct filter_pred *pred)
>  	pred->offset = field->offset;
>  
>  	if (is_string_field(field->type)) {
> -		if (!pred->str_val)
> -			return -EINVAL;
>  		pred->fn = filter_pred_string;
>  		pred->str_len = field->size;
>  		return __filter_add_pred(call, pred);
>  	} else {
> -		if (pred->str_val)
> +		if (strict_strtoull(pred->str_val, 0, &val))
>  			return -EINVAL;
> +		pred->val = val;
> +		kfree(pred->str_val);


And you might also want to do
pred->str_val = NULL;
Otherwise filter_free_pred() may crash later:

void filter_free_pred(struct filter_pred *pred)
{
	if (!pred)
		return;

	kfree(pred->field_name);
	kfree(pred->str_val);
	kfree(pred);
}


Other than that, it looks good.

Thanks,
Frederic.



>  	}
>  
>  	switch (field->size) {
> @@ -351,12 +352,16 @@ oom:
>  	return -ENOMEM;
>  }
>  
> +/*
> + * The filter format can be
> + *   - 0, which means remove all filter preds
> + *   - [||/&&] <field> ==/!= <val>
> + */
>  int filter_parse(char **pbuf, struct filter_pred *pred)
>  {
> -	char *tmp, *tok, *val_str = NULL;
> +	char *tok, *val_str = NULL;
>  	int tok_n = 0;
>  
> -	/* field ==/!= number, or/and field ==/!= number, number */
>  	while ((tok = strsep(pbuf, " \n"))) {
>  		if (tok_n == 0) {
>  			if (!strcmp(tok, "0")) {
> @@ -419,15 +424,10 @@ int filter_parse(char **pbuf, struct filter_pred *pred)
>  	if (!pred->field_name)
>  		return -ENOMEM;
>  
> -	pred->val = simple_strtoull(val_str, &tmp, 0);
> -	if (tmp == val_str) {
> -		pred->str_val = kstrdup(val_str, GFP_KERNEL);
> -		if (!pred->str_val)
> -			return -ENOMEM;
> -	} else if (*tmp != '\0')
> -		return -EINVAL;
> +	pred->str_val = kstrdup(val_str, GFP_KERNEL);
> +	if (!pred->str_val)
> +		return -ENOMEM;
>  
>  	return 0;
>  }
>  
> -
> -- 
> 1.5.4.rc3
> 


  parent reply	other threads:[~2009-04-13 14:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13  2:38 [PATCH 1/3] tracing/filters: allow user-input to be integer-like string Li Zefan
2009-04-13  2:38 ` [PATCH 2/3] tracing/filters: disallow newline as delimeter Li Zefan
2009-04-13  2:39 ` [PATCH 3/3] tracing/filters: don't remove old filters when failed to write subsys->filter Li Zefan
2009-04-13 14:45 ` Frederic Weisbecker [this message]
2009-04-13 22:29   ` [PATCH 1/3] tracing/filters: allow user-input to be integer-like string Ingo Molnar
2009-04-14  4:21     ` Tom Zanussi
2009-04-14  6:24       ` Li Zefan
2009-04-14 11:04         ` Ingo Molnar

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=20090413144513.GF5977@nowhere \
    --to=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tzanussi@gmail.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