From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] syscalls/prctl02: add more error tests
Date: Fri, 1 Nov 2019 09:49:34 +0100 [thread overview]
Message-ID: <20191101084933.GA14639@dell5510> (raw)
In-Reply-To: <1572512347-30116-1-git-send-email-xuyang2018.jy@cn.fujitsu.com>
Hi Xu,
> Signed-off-by: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
> static struct tst_test test = {
> .tcnt = ARRAY_SIZE(tcases),
> .test = verify_prctl,
> + .caps = (struct tst_cap []) {
> + TST_CAP(TST_CAP_DROP, CAP_SYS_ADMIN),
> + TST_CAP(TST_CAP_DROP, CAP_SETPCAP),
This fails on some old distros (Debian stable [1], CentOS 6 [2]),
but also on new (Fedora latest [3]):
undeclared identifier 'CAP_SETPCAP'
Could you please setup travis for your LTP fork and validate builds before
posting to ML?
BTW it'd be nice to have this feature in our patchwork [4], but not sure if this
is available and configurable on our patchwork instance (we don't host it).
Kind regards,
Petr
[1] https://travis-ci.org/pevik/ltp/jobs/605881703
[2] https://travis-ci.org/pevik/ltp/jobs/605881705
[3] https://travis-ci.org/pevik/ltp/jobs/605881704
[4] https://github.com/linux-test-project/ltp/issues/599
next prev parent reply other threads:[~2019-11-01 8:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 12:39 [LTP] [PATCH] syscalls/prctl02: add more error tests Yang Xu
2019-10-31 8:59 ` [LTP] [PATCH v2] " Yang Xu
2019-11-01 8:49 ` Petr Vorel [this message]
2019-11-01 11:24 ` Yang Xu
2019-11-01 12:59 ` [LTP] [PATCH v3] " Yang Xu
2019-11-07 14:54 ` Cyril Hrubis
2019-11-08 12:12 ` Yang Xu
2019-11-08 13:20 ` Yang Xu
2019-11-08 14:24 ` Cyril Hrubis
2019-11-11 8:59 ` [LTP] [PATCH v4] " Yang Xu
2019-11-11 16:31 ` Cyril Hrubis
2019-11-12 3:02 ` Yang Xu
[not found] ` <5DCA5206.3040508@cn.fujitsu.com>
2019-11-12 7:27 ` Yang Xu
2019-11-12 10:15 ` Cyril Hrubis
2019-11-12 10:31 ` Yang Xu
2019-11-13 5:23 ` [LTP] [PATCH v5] " Yang Xu
2019-11-13 10:33 ` Cyril Hrubis
2019-11-12 10:10 ` [LTP] [PATCH v4] " Cyril Hrubis
2019-11-12 10:25 ` Yang Xu
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=20191101084933.GA14639@dell5510 \
--to=pvorel@suse.cz \
--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