From: Kees Cook <keescook@chromium.org>
To: ltp@lists.linux.it
Subject: [LTP] [exec] 166d03c9ec: ltp.execveat02.fail
Date: Thu, 4 Jun 2020 15:45:46 -0700 [thread overview]
Message-ID: <202006041542.0720CB7A@keescook> (raw)
In-Reply-To: <20200525091420.GI12456@shao2-debian>
On Mon, May 25, 2020 at 05:14:20PM +0800, kernel test robot wrote:
> Greeting,
(Whoops, I missed this in my inbox.)
> <<<test_start>>>
> tag=execveat02 stime=1590373229
> cmdline="execveat02"
> contacts=""
> analysis=exit
> <<<test_output>>>
> tst_test.c:1246: INFO: Timeout per run is 0h 05m 00s
> execveat02.c:64: PASS: execveat() fails as expected: EBADF (9)
> execveat02.c:64: PASS: execveat() fails as expected: EINVAL (22)
> execveat02.c:61: FAIL: execveat() fails unexpectedly, expected: ELOOP: EACCES (13)
> execveat02.c:64: PASS: execveat() fails as expected: ENOTDIR (20)
I will go check on this. Looking at the expected result (ELOOP) I think
this just means the test needs adjustment because it's trying to
double-check for a pathological case, but it seems their test setup
trips the (now earlier) IS_SREG() test. But I'll double-check and report
back!
--
Kees Cook
next prev parent reply other threads:[~2020-06-04 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200518055457.12302-3-keescook@chromium.org>
2020-05-25 9:14 ` [LTP] [exec] 166d03c9ec: ltp.execveat02.fail kernel test robot
2020-06-04 22:45 ` Kees Cook [this message]
2020-06-05 2:57 ` 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=202006041542.0720CB7A@keescook \
--to=keescook@chromium.org \
--cc=ltp@lists.linux.it \
/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