From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: Kees Cook <keescook@chromium.org>, Shuah Khan <shuah@kernel.org>
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
Eric Biederman <ebiederm@xmission.com>,
kernel@collabora.com, kernel-janitors@vger.kernel.org,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] selftest/exec: conform test to TAP format output
Date: Tue, 5 Mar 2024 11:26:52 +0500 [thread overview]
Message-ID: <2fc8f4d5-0906-46dd-8b71-9425dc96b000@collabora.com> (raw)
In-Reply-To: <202403041256.80EDE9BA2@keescook>
On 3/5/24 1:58 AM, Kees Cook wrote:
> On Mon, Mar 04, 2024 at 08:59:24PM +0500, Muhammad Usama Anjum wrote:
>> Conform the layout, informational and status messages to TAP. No
>> functional change is intended other than the layout of output messages.
>>
>> Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
>> ---
>> tools/testing/selftests/exec/load_address.c | 34 +++++++++------------
>> 1 file changed, 15 insertions(+), 19 deletions(-)
>>
>> diff --git a/tools/testing/selftests/exec/load_address.c b/tools/testing/selftests/exec/load_address.c
>> index d487c2f6a6150..17e3207d34ae7 100644
>> --- a/tools/testing/selftests/exec/load_address.c
>> +++ b/tools/testing/selftests/exec/load_address.c
>> @@ -5,6 +5,7 @@
>> #include <link.h>
>> #include <stdio.h>
>> #include <stdlib.h>
>> +#include "../kselftest.h"
>>
>> struct Statistics {
>> unsigned long long load_address;
>> @@ -41,28 +42,23 @@ int main(int argc, char **argv)
>> unsigned long long misalign;
>> int ret;
>>
>> + ksft_print_header();
>> + ksft_set_plan(1);
>> +
>> ret = dl_iterate_phdr(ExtractStatistics, &extracted);
>> - if (ret != 1) {
>> - fprintf(stderr, "FAILED\n");
>> - return 1;
>> - }
>> + if (ret != 1)
>> + ksft_exit_fail_msg("FAILED: dl_iterate_phdr\n");
>
> I'm for this series, but I do note a weird glitch in the ksft API.
> ksft_exit_fail_msg does:
>
> va_start(args, msg);
> printf("Bail out! ");
> errno = saved_errno;
> vprintf(msg, args);
> va_end(args);
>
> "Bail out!" is not very descriptive. I think I'd rather this should be:
>
> "FAILED: "
>
> and then that added prefix doesn't need to be added everywhere in this
> patch, nor the "error: " prefix in the next patch.
If we want to make this change, FAILED should be removed from all the
tests. We should do it in separate patch. I've taken note and will do it
separate from this series.
--
BR,
Muhammad Usama Anjum
next prev parent reply other threads:[~2024-03-05 6:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 15:59 [PATCH 1/3] selftests/exec: Add the overall result line accourding to TAP Muhammad Usama Anjum
2024-03-04 15:59 ` [PATCH 2/3] selftest/exec: conform test to TAP format output Muhammad Usama Anjum
2024-03-04 20:58 ` Kees Cook
2024-03-05 6:26 ` Muhammad Usama Anjum [this message]
2024-03-04 15:59 ` [PATCH 3/3] selftests/exec: " Muhammad Usama Anjum
2024-03-04 20:55 ` [PATCH 1/3] selftests/exec: Add the overall result line accourding to TAP Kees Cook
2024-03-11 17:10 ` Muhammad Usama Anjum
2024-03-13 19:05 ` Kees Cook
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=2fc8f4d5-0906-46dd-8b71-9425dc96b000@collabora.com \
--to=usama.anjum@collabora.com \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuah@kernel.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