public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] syscalls/execveat01: new test to verify execveat unlinked fd
Date: Tue, 11 Sep 2018 11:24:37 -0400 (EDT)	[thread overview]
Message-ID: <1149740228.46962437.1536679477401.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1533111474.1176.4.camel@mtkswgap22>



----- Original Message -----
> + * DESCRIPTION
> + *     Check if an unlinked executable can run in overlayfs mount.
> + *     The regression is introduced from 8db6c34f1dbc ("Introduce v3
> + *     namespaced file capabilities"). in security/commoncap.c,
> + *     cap_inode_getsecurity() use d_find_alias() cause unhashed dentry
> + *     can't be found. The solution could use d_find_any_alias() instead of
> + *     d_find_alias().
> + *
> + *     From kernel 4.14, this case is expected fails, execveat shell
> + *     return EINVAL.
> + *
> + */

We should fix this for release. If EINVAL is expected behaviour,
test should give PASS.

It's failing with 4.18:

tst_test.c:1063: INFO: Timeout per run is 0h 05m 00s
execveat03.c:71: FAIL: execveat() returned unexpected errno: EINVAL

Summary:
passed   0
failed   1
skipped  0
warnings 0

Regards,
Jan

  parent reply	other threads:[~2018-09-11 15:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-01  8:17 [LTP] [PATCH v2] syscalls/execveat01: new test to verify execveat unlinked fd Eddie.Horng
2018-08-01 11:17 ` Li Wang
2018-08-01 12:53   ` Cyril Hrubis
2018-08-03  9:32   ` Eddie Horng
2018-08-06  9:26     ` Li Wang
2018-08-08 14:41       ` Cyril Hrubis
2018-08-08 14:48         ` Cyril Hrubis
2018-08-09  9:04 ` Cyril Hrubis
2018-08-10  9:32   ` Eddie Horng
2018-09-11 15:24 ` Jan Stancek [this message]
2018-09-12  1:44   ` Eddie Horng
2018-09-12  7:04     ` Jan Stancek

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=1149740228.46962437.1536679477401.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --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