From: Carsten Haitzler <carsten.haitzler@foss.arm.com>
To: James Clark <james.clark@arm.com>
Cc: coresight@lists.linaro.org, mike.leach@linaro.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 01/12] perf test: Shell - Limit to only run executable scripts in tests
Date: Wed, 15 Dec 2021 16:00:43 +0000 [thread overview]
Message-ID: <bc3ead54-032a-efc7-49d4-91702daf4d64@foss.arm.com> (raw)
In-Reply-To: <80b77a6f-3997-ff90-72b5-5613829a98ae@arm.com>
On 12/15/21 13:27, James Clark wrote:
>
>
> On 15/12/2021 12:53, carsten.haitzler@foss.arm.com wrote:
>> From: Carsten Haitzler <carsten.haitzler@arm.com>
>>
>> Perf test's shell runner will just run everything in the tests
>> directory (as long as it's not another directory or does not begin
>> with a dot), but sometimes you find files in there that are not shell
>> scripts - perf.data output for example if you do some testing and then
>> the next time you run perf test it tries to run these. Check the files
>> are executable so they are actually intended to be test scripts and
>> not just some "random junk" files there.
>>
>
> Hi Carsten,
>
> Because these apply to tools/perf files rather than the coresight drivers
> they will need to apply to Arnaldo's perf/core branch. At the moment I'm
> getting merge conflicts so I can't test and review them.
>
> I also think you would have to do to: linux-perf-users@vger.kernel.org and acme@kernel.org
I will send updated versions of the series and include the above -
though perf-users does describe itself for users and not development,
thus I skipped it. I should get the full list then of everyone
> James
>
>> Signed-off-by: Carsten Haitzler <carsten.haitzler@arm.com>
>> ---
>> tools/perf/tests/builtin-test.c | 2 +-
>> tools/perf/util/path.c | 12 ++++++++++++
>> tools/perf/util/path.h | 1 +
>> 3 files changed, 14 insertions(+), 1 deletion(-)
>>
>> diff --git a/tools/perf/tests/builtin-test.c b/tools/perf/tests/builtin-test.c
>> index c4b888f18e9c..1a7e21e5acf1 100644
>> --- a/tools/perf/tests/builtin-test.c
>> +++ b/tools/perf/tests/builtin-test.c
>> @@ -512,7 +512,7 @@ static const char *shell_test__description(char *description, size_t size,
>>
>> #define for_each_shell_test(dir, base, ent) \
>> while ((ent = readdir(dir)) != NULL) \
>> - if (!is_directory(base, ent) && ent->d_name[0] != '.')
>> + if (!is_directory(base, ent) && is_executable_file(base, ent) && ent->d_name[0] != '.')
>>
>> static const char *shell_tests__dir(char *path, size_t size)
>> {
>> diff --git a/tools/perf/util/path.c b/tools/perf/util/path.c
>> index caed0336429f..7dde8c230ae8 100644
>> --- a/tools/perf/util/path.c
>> +++ b/tools/perf/util/path.c
>> @@ -92,3 +92,15 @@ bool is_directory(const char *base_path, const struct dirent *dent)
>>
>> return S_ISDIR(st.st_mode);
>> }
>> +
>> +bool is_executable_file(const char *base_path, const struct dirent *dent)
>> +{
>> + char path[PATH_MAX];
>> + struct stat st;
>> +
>> + sprintf(path, "%s/%s", base_path, dent->d_name);
>> + if (stat(path, &st))
>> + return false;
>> +
>> + return !S_ISDIR(st.st_mode) && (st.st_mode & S_IXUSR);
>> +}
>> diff --git a/tools/perf/util/path.h b/tools/perf/util/path.h
>> index 083429b7efa3..d94902c22222 100644
>> --- a/tools/perf/util/path.h
>> +++ b/tools/perf/util/path.h
>> @@ -12,5 +12,6 @@ int path__join3(char *bf, size_t size, const char *path1, const char *path2, con
>>
>> bool is_regular_file(const char *file);
>> bool is_directory(const char *base_path, const struct dirent *dent);
>> +bool is_executable_file(const char *base_path, const struct dirent *dent);
>>
>> #endif /* _PERF_PATH_H */
>>
next prev parent reply other threads:[~2021-12-15 16:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 12:53 carsten.haitzler
2021-12-15 12:53 ` [PATCH 02/12] perf test: Shell - only run .sh shell files to skip other files carsten.haitzler
2021-12-15 12:54 ` [PATCH 03/12] perf test: Use 3 digits for test numbering now we can have more tests carsten.haitzler
2021-12-15 12:54 ` [PATCH 04/12] perf test: Add beginning of test infra + test to exercise coresight carsten.haitzler
2021-12-15 12:54 ` [PATCH 05/12] perf test: Add coresight test to check all threads get some data logged carsten.haitzler
2021-12-15 12:54 ` [PATCH 06/12] perf test: Add tests to re-use the thread loop test to check aux data carsten.haitzler
2021-12-15 12:54 ` [PATCH 07/12] perf test: Add simple bubblesort test for coresight " carsten.haitzler
2021-12-15 12:54 ` [PATCH 08/12] perf test: Add threaded bubblesort tests for coresight carsten.haitzler
2021-12-15 12:54 ` [PATCH 09/12] perf test: Add add memcpy test for coresight quality checking carsten.haitzler
2021-12-15 12:54 ` [PATCH 10/12] perf test: Add threaded memcpy tests to check coresight aux data carsten.haitzler
2021-12-15 12:54 ` [PATCH 11/12] perf test: Add unrolled loop tests for " carsten.haitzler
2021-12-15 12:54 ` [PATCH 12/12] perf test: Add docs for coresight and related tests carsten.haitzler
2021-12-15 13:27 ` [PATCH 01/12] perf test: Shell - Limit to only run executable scripts in tests James Clark
2021-12-15 16:00 ` Carsten Haitzler [this message]
2021-12-15 16:03 carsten.haitzler
2021-12-17 14:55 ` Suzuki K Poulose
2021-12-17 17:18 ` Carsten Haitzler
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=bc3ead54-032a-efc7-49d4-91702daf4d64@foss.arm.com \
--to=carsten.haitzler@foss.arm.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.leach@linaro.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
all inboxes | Powered by JetHome®