From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 3/3] iopl01: skip test if kernel is locked down
Date: Tue, 21 Jul 2020 17:29:32 +0200 [thread overview]
Message-ID: <20200721152932.GC13733@yuki.lan> (raw)
In-Reply-To: <20200720194920.22784-3-ernunes@redhat.com>
Hi!
> iopl is restricted under kernel lockdown.
>
> Signed-off-by: Erico Nunes <ernunes@redhat.com>
> ---
> testcases/kernel/syscalls/iopl/iopl01.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/testcases/kernel/syscalls/iopl/iopl01.c b/testcases/kernel/syscalls/iopl/iopl01.c
> index edf586cd1..4237d3f10 100644
> --- a/testcases/kernel/syscalls/iopl/iopl01.c
> +++ b/testcases/kernel/syscalls/iopl/iopl01.c
> @@ -42,6 +42,12 @@ static void verify_iopl(void)
> }
> }
>
> +static void setup(void)
> +{
> + /* iopl is restricted under kernel lockdown. */
> + tst_lockdown_skip();
> +}
> +
> static void cleanup(void)
> {
> /*
> @@ -54,6 +60,7 @@ static void cleanup(void)
> static struct tst_test test = {
> .test_all = verify_iopl,
> .needs_root = 1,
> + .setup = setup,
> .cleanup = cleanup,
> };
Here as well, shouldn't we add iopl03?
Or at least change the library so that we have a function that returns
if kernel is locked or not so that someone can write such test.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2020-07-21 15:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 19:49 [LTP] [PATCH 1/3] lib: add function to check for kernel lockdown Erico Nunes
2020-07-20 19:49 ` [LTP] [PATCH 2/3] ioperm01: skip test if kernel is locked down Erico Nunes
2020-07-21 15:26 ` Cyril Hrubis
2020-07-22 15:52 ` Erico Nunes
2020-07-20 19:49 ` [LTP] [PATCH 3/3] iopl01: " Erico Nunes
2020-07-21 15:29 ` Cyril Hrubis [this message]
2020-07-21 7:46 ` [LTP] [PATCH 1/3] lib: add function to check for kernel lockdown Li Wang
2020-07-21 8:57 ` Erico Nunes
2020-07-21 13:19 ` Li Wang
2020-07-22 15:52 ` Erico Nunes
2020-07-22 15:58 ` Cyril Hrubis
2020-07-23 7:51 ` Li Wang
2020-07-21 15:26 ` Cyril Hrubis
2020-07-22 15:52 ` Erico Nunes
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=20200721152932.GC13733@yuki.lan \
--to=chrubis@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