public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <shuah@kernel.org>
To: Andy Lutomirski <luto@kernel.org>, Shuah Khan <shuahkh@osg.samsung.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	"open list:KERNEL SELFTEST FRAMEWORK" 
	<linux-kselftest@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Shuah Khan <shuah@kernel.org>,
	Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH] selftests: capabilities: convert error output to TAP13 ksft framework
Date: Thu, 27 Jul 2017 14:32:16 -0600	[thread overview]
Message-ID: <18b89f2d-8219-e8bd-3de7-350aa96feed2@kernel.org> (raw)
In-Reply-To: <CALCETrV1-ZmOp1DWowhiO+qYPvM1f7t9GpsLh8W81cgPR=ThRQ@mail.gmail.com>

On 07/27/2017 12:50 PM, Andy Lutomirski wrote:
> On Wed, Jul 26, 2017 at 2:18 PM, Shuah Khan <shuahkh@osg.samsung.com> wrote:
>> Convert errx() and err() usage to appropriate TAP13 ksft API.
>>
>> Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
>> ---
>>  tools/testing/selftests/capabilities/test_execve.c | 105 ++++++++++++---------
>>  .../testing/selftests/capabilities/validate_cap.c  |   9 +-
>>  2 files changed, 65 insertions(+), 49 deletions(-)
>>
>> diff --git a/tools/testing/selftests/capabilities/test_execve.c b/tools/testing/selftests/capabilities/test_execve.c
>> index 7c38233292b0..cf6778441381 100644
>> --- a/tools/testing/selftests/capabilities/test_execve.c
>> +++ b/tools/testing/selftests/capabilities/test_execve.c
>> @@ -1,7 +1,6 @@
>>  #define _GNU_SOURCE
>>
>>  #include <cap-ng.h>
>> -#include <err.h>
>>  #include <linux/capability.h>
>>  #include <stdbool.h>
>>  #include <string.h>
>> @@ -39,29 +38,32 @@ static void vmaybe_write_file(bool enoent_ok, char *filename, char *fmt, va_list
>>         int buf_len;
>>
>>         buf_len = vsnprintf(buf, sizeof(buf), fmt, ap);
>> -       if (buf_len < 0) {
>> -               err(1, "vsnprintf failed");
>> -       }
>> -       if (buf_len >= sizeof(buf)) {
>> -               errx(1, "vsnprintf output truncated");
>> -       }
>> +       if (buf_len < 0)
>> +               ksft_exit_fail_msg("vsnprintf failed - %s\n", strerror(errno));
> 
> Could this not be a hypothetical ksft_exit_fail_msg_err or similar?
> Or a shorter name like ksft_fatal_err()?
> 
> 

Is there a reason to add _err() suffix?

ksft_exit_fail_msg() is a generic routine for a test to exit
with a test failure and print a message. The message doesn't
necessarily need to be a standard error message such as the
one err() or errx() or strerror() generate.

In some cases test could fail with a standard error condition,
but not always. In that context, it doesn't make sense to add
_err suffix. I leveraged this generic function to replace err()
and errx() usages adding strerror() not loose the important
information.

thanks,
-- Shuah

  reply	other threads:[~2017-07-27 20:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-26 21:18 [PATCH] selftests: capabilities: convert error output to TAP13 ksft framework Shuah Khan
2017-07-27 18:50 ` Andy Lutomirski
2017-07-27 20:32   ` Shuah Khan [this message]
2017-07-28  2:13     ` Andy Lutomirski
2017-07-28 15:41       ` Shuah Khan
2017-07-28 21:39         ` Shuah Khan
2017-08-04 21:46           ` Shuah Khan

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=18b89f2d-8219-e8bd-3de7-350aa96feed2@kernel.org \
    --to=shuah@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=shuahkh@osg.samsung.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