public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Irina Tirdea <irina.tirdea@gmail.com>,
	mingo@redhat.com, acme@ghostprotocols.net,
	a.p.zijlstra@chello.nl, rostedt@goodmis.org, paulus@samba.org,
	dsahern@gmail.com, namhyung.kim@lge.com,
	linux-kernel@vger.kernel.org,
	Irina Tirdea <irina.tirdea@intel.com>
Subject: Re: [PATCH 1/4] perf tools: remove sscanf extension %as
Date: Wed, 19 Sep 2012 12:20:11 +0900	[thread overview]
Message-ID: <505939EB.8080004@hitachi.com> (raw)
In-Reply-To: <87ligd8j46.fsf@sejong.aot.lge.com>

(2012/09/14 10:54), Namhyung Kim wrote:
> Hi Irina,
> 
> (Adding Masami to Cc)

Thanks Irina and Namhyung :)

> On Fri, 14 Sep 2012 01:07:40 +0300, Irina Tirdea wrote:
>> From: Irina Tirdea <irina.tirdea@intel.com>
>>
>> perf uses sscanf extension %as to read and allocate a
>> string in the same step. This is a non-standard extension
>> only present in new versions of glibc.
>>
>> Replacing the use of sscanf and %as with strtok_r calls
>> in order to parse a given string into its components.
>> This is needed in Android since bionic does not support
>> %as extension for sscanf.
>>
>> Signed-off-by: Irina Tirdea <irina.tirdea@intel.com>
>> ---
>>  tools/perf/util/probe-event.c       |   25 ++++++++++++++++++-------
>>  tools/perf/util/trace-event-parse.c |   18 ++++++++----------
>>  2 files changed, 26 insertions(+), 17 deletions(-)
>>
>> diff --git a/tools/perf/util/probe-event.c b/tools/perf/util/probe-event.c
>> index 4ce04c2..685ddcf 100644
>> --- a/tools/perf/util/probe-event.c
>> +++ b/tools/perf/util/probe-event.c
>> @@ -1100,6 +1100,7 @@ static int parse_probe_trace_command(const char *cmd,
>>  	struct probe_trace_point *tp = &tev->point;
>>  	char pr;
>>  	char *p;
>> +	char *argv0_str = NULL, *fmt, *fmt1_str, *fmt2_str, *fmt3_str;
>>  	int ret, i, argc;
>>  	char **argv;
>>  
>> @@ -1116,14 +1117,19 @@ static int parse_probe_trace_command(const char *cmd,
>>  	}
>>  
>>  	/* Scan event and group name. */
>> -	ret = sscanf(argv[0], "%c:%a[^/ \t]/%a[^ \t]",
>> -		     &pr, (float *)(void *)&tev->group,
>> -		     (float *)(void *)&tev->event);
>> -	if (ret != 3) {
>> +	argv0_str = strdup(argv[0]);
> 
> It seems you need to check return value of strdup.

Agreed.

>> +	fmt1_str = strtok_r(argv0_str, ":", &fmt);
>> +	fmt2_str = strtok_r(NULL, "/", &fmt);
>> +	fmt3_str = strtok_r(NULL, " \t", &fmt);
>> +	if (fmt1_str == NULL || strlen(fmt1_str) != 1 || fmt2_str == NULL
>> +	    || fmt3_str == NULL) {
>>  		semantic_error("Failed to parse event name: %s\n", argv[0]);
>>  		ret = -EINVAL;
>>  		goto out;
>>  	}
>> +	pr = fmt1_str[0];
>> +	tev->group = strdup(fmt2_str);
>> +	tev->event = strdup(fmt3_str);
>>  	pr_debug("Group:%s Event:%s probe:%c\n", tev->group, tev->event, pr);
>>  
>>  	tp->retprobe = (pr == 'r');
>> @@ -1135,10 +1141,13 @@ static int parse_probe_trace_command(const char *cmd,
>>  		p++;
>>  	} else
>>  		p = argv[1];
>> -	ret = sscanf(p, "%a[^+]+%lu", (float *)(void *)&tp->symbol,
>> -		     &tp->offset);
>> -	if (ret == 1)
>> +	fmt1_str = strtok_r(p, "+", &fmt);
>> +	tp->symbol = strdup(fmt1_str);
> 
> Probably here too - although the original code didn't but I think it's
> needed.

right, it should be fixed.

>> +	fmt2_str = strtok_r(NULL, "", &fmt);
>> +	if (fmt2_str == NULL)
>>  		tp->offset = 0;
>> +	else
>> +		tp->offset = strtoul(fmt2_str, NULL, 10);
>>  
>>  	tev->nargs = argc - 2;
>>  	tev->args = zalloc(sizeof(struct probe_trace_arg) * tev->nargs);
>> @@ -1162,6 +1171,8 @@ static int parse_probe_trace_command(const char *cmd,
>>  	}
>>  	ret = 0;
>>  out:
>> +	if (argv0_str)
>> +		free(argv0_str);
> 
> The free() can handle a NULL pointer safely.

I don't care about it, since there are already lots of "if (ptr) free(ptr)"
style code ;)

> 
>>  	argv_free(argv);
>>  	return ret;
>>  }

Thank you!

-- 
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com



  reply	other threads:[~2012-09-19  3:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-13 22:07 [PATCH 0/4] perf tools: runtime fixes for Android Irina Tirdea
2012-09-13 22:07 ` [PATCH 1/4] perf tools: remove sscanf extension %as Irina Tirdea
2012-09-14  1:54   ` Namhyung Kim
2012-09-19  3:20     ` Masami Hiramatsu [this message]
2012-09-20 19:13       ` Irina Tirdea
2012-09-20 20:37   ` [PATCH v2 1/1] " irina.tirdea
2012-09-21 15:29     ` Arnaldo Carvalho de Melo
2012-09-24  7:13     ` Masami Hiramatsu
2012-09-27  5:35     ` [tip:perf/core] " tip-bot for Irina Tirdea
2012-09-13 22:07 ` [PATCH 2/4] perf stat: add compile-time option to disable --big-num Irina Tirdea
2012-09-14  5:40   ` Ingo Molnar
2012-09-20 19:17     ` Irina Tirdea
2012-09-23 21:48   ` [PATCH v2 1/1] perf stat: implement --big-num grouping Irina Tirdea
2012-09-13 22:07 ` [PATCH 3/4] perf archive: remove -f from the rm command Irina Tirdea
2012-09-19 15:19   ` [tip:perf/core] perf archive: Remove " tip-bot for Irina Tirdea
2012-09-13 22:07 ` [PATCH 4/4] perf archive: make f the last parameter for tar Irina Tirdea
2012-09-19 15:20   ` [tip:perf/core] perf archive: Make 'f' " tip-bot for Irina Tirdea

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=505939EB.8080004@hitachi.com \
    --to=masami.hiramatsu.pt@hitachi.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=dsahern@gmail.com \
    --cc=irina.tirdea@gmail.com \
    --cc=irina.tirdea@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung.kim@lge.com \
    --cc=namhyung@kernel.org \
    --cc=paulus@samba.org \
    --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