From: David Drysdale <dmd@lurklurk.org>
To: David Drysdale <drysdale@google.com>,
schwab@linux-m68k.org, geert@linux-m68k.org
Cc: shuahkh@osg.samsung.com, akpm@linux-foundation.org,
linux-api@vger.kernel.org, linux-m68k@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH selftest fails!] m68k: Wire up execveat
Date: Mon, 22 Dec 2014 17:54:47 -0500 [thread overview]
Message-ID: <5498A137.6020707@lurklurk.org> (raw)
In-Reply-To: <CAHse=S-KzC5y8eC_ZFrbUJo0Ub5Qv8WeeXHdY1-F=HckAX=L=A@mail.gmail.com>
[Re-send from a different email address because I apparently can't send
plaintext from gMail on my phone.]
On 21 Dec 2014 09:37, "Andreas Schwab" <schwab@linux-m68k.org> wrote:
>
> Geert Uytterhoeven <geert@linux-m68k.org> writes:
>
> > Check success of execveat(5,
> 'xxxxxxxxxxxxxxxxxxxx...yyyyyyyyyyyyyyyyyyyy', 0)... [FAIL] (child 792
> exited with 126 not 127)
>
> POSIX says
> (http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_08_02):
>
> If a command is not found, the exit status shall be 127. If the
> command name is found, but it is not an executable utility, the exit
> status shall be 126.
>
> Andreas.
>
That sounds like a bit of a grey area -- is ENAMETOOLONG nearer to
ENOENT or EACCES? Maybe it's best to make the test allow either (given
that it's not a test of shell behaviour).
I can update the test to do that, but it probably won't be until the new
year I'm afraid.
David
prev parent reply other threads:[~2014-12-22 23:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-21 11:02 [PATCH selftest fails!] m68k: Wire up execveat Geert Uytterhoeven
2014-12-21 14:37 ` Andreas Schwab
[not found] ` <CAHse=S-KzC5y8eC_ZFrbUJo0Ub5Qv8WeeXHdY1-F=HckAX=L=A@mail.gmail.com>
2014-12-22 22:54 ` David Drysdale [this message]
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=5498A137.6020707@lurklurk.org \
--to=dmd@lurklurk.org \
--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 \
--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