From: Carsten Haitzler <carsten.haitzler@foss.arm.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>, linux-kernel@vger.kernel.org
Cc: coresight@lists.linaro.org, mathieu.poirier@linaro.org,
mike.leach@linaro.org, leo.yan@linaro.org,
inux-perf-users@vger.kernel.org, acme@kernel.org
Subject: Re: [PATCH 01/12] perf test: Shell - Limit to only run executable scripts in tests
Date: Fri, 17 Dec 2021 17:18:49 +0000 [thread overview]
Message-ID: <6467eef9-0160-b7d1-9ef0-4867dd0d17e4@foss.arm.com> (raw)
In-Reply-To: <5ae9ef1d-76bb-6ff3-fa34-27e9399f0110@arm.com>
On 12/17/21 14:55, Suzuki K Poulose wrote:
> On 15/12/2021 16:03, 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.
>>
>> Signed-off-by: Carsten Haitzler <carsten.haitzler@arm.com>
>> ---
>> tools/perf/tests/builtin-test.c | 4 +++-
>> tools/perf/util/path.c | 12 ++++++++++++
>> tools/perf/util/path.h | 1 +
>> 3 files changed, 16 insertions(+), 1 deletion(-)
>>
>> diff --git a/tools/perf/tests/builtin-test.c
>> b/tools/perf/tests/builtin-test.c
>> index 8cb5a1c3489e..ece272b55587 100644
>> --- a/tools/perf/tests/builtin-test.c
>> +++ b/tools/perf/tests/builtin-test.c
>> @@ -295,7 +295,9 @@ static const char *shell_test__description(char
>> *description, size_t size,
>> #define for_each_shell_test(entlist, nr, base,
>> ent) \
>> for (int __i = 0; __i < nr && (ent = entlist[__i]); __i++) \
>> - if (!is_directory(base, ent) && ent->d_name[0] != '.')
>> + if (!is_directory(base, ent) && \
>> + is_executable_file(base, ent) && \
>> + ent->d_name[0] != '.')
>
> If we reorder the checks, we could potentially avoid a few
> syscalls for hidden items. i.e., if we do ent->d_name[0] != '.'
> first.
Could do that, thought this certainly is not a performance critical path
and the code certainly shows that and doesn't care - can fix that too.
>> 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);
>
> Should this be snprintf() for additional safety ?
Ylou're right - I was just following the existing pattern int he code
right above in is_directory() that uses sprintf :) I can fix both.
>> + if (stat(path, &st))
>> + return false;
>> +
>> + return !S_ISDIR(st.st_mode) && (st.st_mode & S_IXUSR);
>
> Otherwise looks good to me.
>
> Suzuki
next prev parent reply other threads:[~2021-12-17 17:18 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 16:03 carsten.haitzler
2021-12-15 16:03 ` [PATCH 02/12] perf test: Shell - only run .sh shell files to skip other files carsten.haitzler
2021-12-16 10:22 ` Daniel Thompson
2021-12-16 19:45 ` Carsten Haitzler
2021-12-17 15:00 ` Suzuki K Poulose
2021-12-17 17:22 ` Carsten Haitzler
2021-12-15 16:03 ` [PATCH 03/12] perf test: Use 3 digits for test numbering now we can have more tests carsten.haitzler
2021-12-21 12:35 ` Leo Yan
2021-12-21 20:51 ` Arnaldo Carvalho de Melo
2021-12-15 16:03 ` [PATCH 04/12] perf test: Add beginning of test infra + test to exercise coresight carsten.haitzler
2021-12-21 15:03 ` Leo Yan
2021-12-21 20:40 ` Arnaldo Carvalho de Melo
2022-01-04 15:15 ` Carsten Haitzler
2022-01-04 15:14 ` Carsten Haitzler
2022-01-19 16:58 ` James Clark
2022-02-04 10:21 ` Mike Leach
2021-12-15 16:03 ` [PATCH 05/12] perf test: Add coresight test to check all threads get some data logged carsten.haitzler
2022-01-03 7:07 ` Leo Yan
2022-01-04 15:01 ` Carsten Haitzler
2021-12-15 16:03 ` [PATCH 06/12] perf test: Add tests to re-use the thread loop test to check aux data carsten.haitzler
2022-02-04 10:36 ` Mike Leach
2021-12-15 16:03 ` [PATCH 07/12] perf test: Add simple bubblesort test for coresight " carsten.haitzler
2022-01-03 8:00 ` Leo Yan
2022-01-04 15:13 ` Carsten Haitzler
2022-01-12 9:54 ` Leo Yan
2021-12-15 16:03 ` [PATCH 08/12] perf test: Add threaded bubblesort tests for coresight carsten.haitzler
2021-12-15 16:04 ` [PATCH 09/12] perf test: Add add memcpy test for coresight quality checking carsten.haitzler
2022-02-04 10:43 ` Mike Leach
2021-12-15 16:04 ` [PATCH 10/12] perf test: Add threaded memcpy tests to check coresight aux data carsten.haitzler
2021-12-15 16:04 ` [PATCH 11/12] perf test: Add unrolled loop tests for " carsten.haitzler
2022-02-04 10:51 ` Mike Leach
2021-12-15 16:04 ` [PATCH 12/12] perf test: Add docs for coresight and related tests carsten.haitzler
2022-01-19 16:43 ` James Clark
2022-01-31 18:05 ` Carsten Haitzler
2022-02-04 14:50 ` Mike Leach
2022-03-09 12:25 ` Carsten Haitzler
2022-03-09 12:30 ` Carsten Haitzler
2021-12-17 14:55 ` [PATCH 01/12] perf test: Shell - Limit to only run executable scripts in tests Suzuki K Poulose
2021-12-17 17:18 ` Carsten Haitzler [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-15 12:53 carsten.haitzler
2021-12-15 13:27 ` James Clark
2021-12-15 16:00 ` 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=6467eef9-0160-b7d1-9ef0-4867dd0d17e4@foss.arm.com \
--to=carsten.haitzler@foss.arm.com \
--cc=acme@kernel.org \
--cc=coresight@lists.linaro.org \
--cc=inux-perf-users@vger.kernel.org \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@arm.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
all inboxes | Powered by JetHome®