From: Shuah Khan <shuahkh@osg.samsung.com>
To: David Drysdale <drysdale@google.com>,
linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Andreas Schwab <schwab@linux-m68k.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-m68k@vger.kernel.org, linux-api@vger.kernel.org,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH] selftests/exec: allow shell return code of 126
Date: Mon, 05 Jan 2015 12:03:39 -0700 [thread overview]
Message-ID: <54AAE00B.1020809@osg.samsung.com> (raw)
In-Reply-To: <1420456786-5989-1-git-send-email-drysdale@google.com>
On 01/05/2015 04:19 AM, David Drysdale wrote:
> When the shell fails to invoke a script because its path name
> is too long (ENAMETOOLONG), most shells return 127 to indicate
> command not found. However, some systems report 126 (which POSIX
> suggests should indicate a non-executable file) for this case,
> so allow that too.
>
> Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Signed-off-by: David Drysdale <drysdale@google.com>
> ---
> tools/testing/selftests/exec/execveat.c | 28 ++++++++++++++++++++++------
> 1 file changed, 22 insertions(+), 6 deletions(-)
>
> diff --git a/tools/testing/selftests/exec/execveat.c b/tools/testing/selftests/exec/execveat.c
> index d273624c93a6..0d940c6e26bd 100644
> --- a/tools/testing/selftests/exec/execveat.c
> +++ b/tools/testing/selftests/exec/execveat.c
> @@ -62,7 +62,7 @@ static int _check_execveat_fail(int fd, const char *path, int flags,
> }
>
> static int check_execveat_invoked_rc(int fd, const char *path, int flags,
> - int expected_rc)
> + int expected_rc, int expected_rc2)
This logic doesn't scale well if there other expected return
values to account for. Please think about a re-write to handle
multiple expected return codes.
> {
> int status;
> int rc;
> @@ -99,9 +99,19 @@ static int check_execveat_invoked_rc(int fd, const char *path, int flags,
> return 1;
> }
> if (WEXITSTATUS(status) != expected_rc) {
> - printf("[FAIL] (child %d exited with %d not %d)\n",
> - child, WEXITSTATUS(status), expected_rc);
> - return 1;
> + if (expected_rc != expected_rc2) {
Please collapse expected_rc and expected_rc2 checks. You can rephrase
the error message to work for both cases.
thanks,
-- Shuah
--
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@osg.samsung.com | (970) 217-8978
next prev parent reply other threads:[~2015-01-05 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 11:19 David Drysdale
2015-01-05 11:35 ` Geert Uytterhoeven
2015-01-05 19:03 ` Shuah Khan [this message]
2015-01-06 8:23 ` David Drysdale
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=54AAE00B.1020809@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=akpm@linux-foundation.org \
--cc=drysdale@google.com \
--cc=geert@linux-m68k.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schwab@linux-m68k.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
Powered by JetHome