From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Jiri Olsa" <jolsa@kernel.org>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Wang Nan" <wangnan0@huawei.com>, "He Kuang" <hekuang@huawei.com>,
"Michal Marek" <mmarek@suse.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Stephane Eranian" <eranian@google.com>,
"Paul Turner" <pjt@google.com>,
"David Carrillo-Cisneros" <davidcc@google.com>,
"Tzvetomir Stoyanov" <tstoyanov@vmware.com>
Subject: Re: [PATCH] tools lib traceevent: Fix "robust" test of do_generate_dynamic_list_file
Date: Mon, 19 Aug 2019 11:39:50 -0300 [thread overview]
Message-ID: <20190819143950.GD29674@kernel.org> (raw)
In-Reply-To: <20190805130150.25acfeb1@gandalf.local.home>
Em Mon, Aug 05, 2019 at 01:01:50PM -0400, Steven Rostedt escreveu:
> [
> Not sure why I wasn't Cc'd on the original patch (or the one before that)
> but I guess I need to add tools/lib/traceevent under MAINTAINERs for
> perhaps tracing?
> ]
>
> From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
>
> The tools/lib/traceevent/Makefile had a test added to it to detect a failure
> of the "nm" when making the dynamic list file (whatever that is). The
> problem is that the test sorts the values "U W w" and some versions of sort
> will place "w" ahead of "W" (even though it has a higher ASCII value, and
> break the test.
>
> Add 'tr "w" "W"' to merge the two and not worry about the ordering.
Thanks, applied.
- Arnaldo
> Cc: stable@vger.kernel.org
> Fixes: 6467753d61399 ("tools lib traceevent: Robustify do_generate_dynamic_list_file")
> Reported-by: Tzvetomir Stoyanov <tstoyanov@vmware.com>
> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> ---
> tools/lib/traceevent/Makefile | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/lib/traceevent/Makefile b/tools/lib/traceevent/Makefile
> index 3292c290654f..8352d53dcb5a 100644
> --- a/tools/lib/traceevent/Makefile
> +++ b/tools/lib/traceevent/Makefile
> @@ -266,8 +266,8 @@ endef
>
> define do_generate_dynamic_list_file
> symbol_type=`$(NM) -u -D $1 | awk 'NF>1 {print $$1}' | \
> - xargs echo "U W w" | tr ' ' '\n' | sort -u | xargs echo`;\
> - if [ "$$symbol_type" = "U W w" ];then \
> + xargs echo "U w W" | tr 'w ' 'W\n' | sort -u | xargs echo`;\
> + if [ "$$symbol_type" = "U W" ];then \
> (echo '{'; \
> $(NM) -u -D $1 | awk 'NF>1 {print "\t"$$2";"}' | sort -u;\
> echo '};'; \
> --
> 2.20.1
--
- Arnaldo
prev parent reply other threads:[~2019-08-19 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 17:01 [PATCH] tools lib traceevent: Fix "robust" test of do_generate_dynamic_list_file Steven Rostedt
2019-08-13 21:21 ` Steven Rostedt
2019-08-13 21:35 ` Arnaldo Carvalho de Melo
2019-08-19 14:39 ` Arnaldo Carvalho de Melo [this message]
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=20190819143950.GD29674@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=davidcc@google.com \
--cc=eranian@google.com \
--cc=hekuang@huawei.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mmarek@suse.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=rostedt@goodmis.org \
--cc=tstoyanov@vmware.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wangnan0@huawei.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