From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3 2/2] syscalls/iopl, ioperm: Check for SecureBoot lockdown
Date: Tue, 10 Nov 2020 12:51:46 +0100 [thread overview]
Message-ID: <20201110115146.GC10788@pevik> (raw)
In-Reply-To: <20201109164605.25965-2-mdoucha@suse.cz>
Hi,
> SecureBoot implies integrity lockdown even if tst_lockdown_enabled() cannot
> check lockdown status directly. Udpate skip condition in ioperm() and iopl()
> tests.
Reviewed-by: Petr Vorel <pvorel@suse.cz>
...
> + /* ioperm() is restricted under kernel lockdown. */
> + if (tst_lockdown_enabled() || tst_secureboot_enabled() > 0)
> + tst_brk(TCONF, "Kernel is locked down, skip this test");
> +
I wonder if this could be interesting for docparse to have this functionality
exposed as a struct tst_test flag:
.tst_lockdown_restricted = 1
Kind regards,
Petr
next prev parent reply other threads:[~2020-11-10 11:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 16:46 [LTP] [PATCH v3 1/2] Add tst_secureboot_enabled() helper function Martin Doucha
2020-11-09 16:46 ` [LTP] [PATCH v3 2/2] syscalls/iopl, ioperm: Check for SecureBoot lockdown Martin Doucha
2020-11-10 5:54 ` Li Wang
2020-11-10 8:52 ` Cyril Hrubis
2020-11-10 9:16 ` Li Wang
2020-11-10 10:23 ` Petr Vorel
2020-11-10 11:51 ` Petr Vorel [this message]
2020-11-10 11:55 ` Cyril Hrubis
2020-11-10 11:49 ` [LTP] [PATCH v3 1/2] Add tst_secureboot_enabled() helper function Petr Vorel
2020-11-10 11:52 ` Martin Doucha
2020-11-10 12:04 ` Petr Vorel
2020-11-12 14:21 ` Cyril Hrubis
2020-11-12 14:57 ` Martin Doucha
2020-11-12 17:43 ` Petr Vorel
2020-11-13 6:02 ` Li Wang
2020-11-13 15:24 ` Cyril Hrubis
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=20201110115146.GC10788@pevik \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.