All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	David Ahern <dsahern@gmail.com>, Jiri Olsa <jolsa@redhat.com>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH perf/core 2/8] [BUGFIX] perf probe: Remove all probes matches given pattern at once
Date: Wed, 22 Apr 2015 21:27:52 +0900	[thread overview]
Message-ID: <553793C8.6070007@hitachi.com> (raw)
In-Reply-To: <20150422073343.GB21451@danjae.kornet>

(2015/04/22 16:33), Namhyung Kim wrote:
> Hi Masami,
> 
> On Tue, Apr 21, 2015 at 08:42:00PM +0900, Masami Hiramatsu wrote:
>> @@ -2760,14 +2762,17 @@ int del_perf_probe_events(struct strlist *dellist)
>>  
>>  		pr_debug("Group: %s, Event: %s\n", group, event);
>>  
>> +		ret = ret2 = -ENOENT;
>>  		if (namelist)
>>  			ret = del_trace_probe_event(kfd, buf, namelist);
>>  
>> -		if (unamelist && ret != 0)
>> -			ret = del_trace_probe_event(ufd, buf, unamelist);
>> +		if (unamelist)
>> +			ret2 = del_trace_probe_event(ufd, buf, unamelist);
>>  
>> -		if (ret != 0)
>> -			pr_info("Info: Event \"%s\" does not exist.\n", buf);
>> +		/* Since we can remove probes which already removed, no error  */
>> +		if (ret != 0 && ret2 != 0)
>> +			pr_debug("Event \"%s\" does not exist.\n", buf);
> 
> I think it'd be better checking 'ret == -ENOENT && ret2 == -ENOENT'
> here since del_trace_probe_event() can return other error codes.

Indeed. BTW, this code is replaced by patch 5/8, so I'll update it too.

Thanks!


-- 
Masami HIRAMATSU
Linux Technology Research Center, System Productivity Research Dept.
Center for Technology Innovation - Systems Engineering
Hitachi, Ltd., Research & Development Group
E-mail: masami.hiramatsu.pt@hitachi.com



  reply	other threads:[~2015-04-22 12:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 11:41 [PATCH perf/core 0/8] perf-probe: Add filtering features Masami Hiramatsu
2015-04-21 11:41 ` [PATCH perf/core 1/8] [BUGFIX] perf probe: Make --funcs option exclusive Masami Hiramatsu
2015-04-21 11:42 ` [PATCH perf/core 2/8] [BUGFIX] perf probe: Remove all probes matches given pattern at once Masami Hiramatsu
2015-04-22  7:33   ` Namhyung Kim
2015-04-22 12:27     ` Masami Hiramatsu [this message]
2015-04-21 11:42 ` [PATCH perf/core 3/8] perf probe: Accept multiple filter options Masami Hiramatsu
2015-04-21 11:42 ` [PATCH perf/core 4/8] perf probe: Accept filter argument for --list Masami Hiramatsu
2015-04-21 11:42 ` [PATCH perf/core 5/8] perf probe: Allow to use filter on --del command Masami Hiramatsu
2015-04-22 13:56   ` Namhyung Kim
2015-04-23 13:10     ` Masami Hiramatsu
2015-04-21 11:42 ` [PATCH perf/core 6/8] perf probe: Accept filter argument for --funcs Masami Hiramatsu
2015-04-21 11:42 ` [PATCH perf/core 7/8] perf probe: Remove redundant cleanup of params.filter Masami Hiramatsu
2015-04-21 11:42 ` [PATCH perf/core 8/8] perf probe: Cleanup and consolidate command parsers Masami Hiramatsu

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=553793C8.6070007@hitachi.com \
    --to=masami.hiramatsu.pt@hitachi.com \
    --cc=acme@kernel.org \
    --cc=dsahern@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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 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.