From: Joe Lawrence <joe.lawrence@redhat.com>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: jpoimboe@redhat.com, jikos@kernel.org, mbenes@suse.cz,
pmladek@suse.com, shuah@kernel.org,
live-patching@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] selftests: livepatch: Fix it to do root uid check and skip
Date: Mon, 16 Dec 2019 16:01:18 -0500 [thread overview]
Message-ID: <20191216210118.GA28841@redhat.com> (raw)
In-Reply-To: <20191216191840.15188-1-skhan@linuxfoundation.org>
On Mon, Dec 16, 2019 at 12:18:40PM -0700, Shuah Khan wrote:
> livepatch test configures the system and debug environment to run
> tests. Some of these actions fail without root access and test
> dumps several permission denied messages before it exits.
>
> Fix test-state.sh to call setup_config instead of set_dynamic_debug
> as suggested by Petr Mladek <pmladek@suse.com>
>
> Fix it to check root uid and exit with skip code instead.
>
> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
> ---
> tools/testing/selftests/livepatch/functions.sh | 15 ++++++++++++++-
> tools/testing/selftests/livepatch/test-state.sh | 3 +--
> 2 files changed, 15 insertions(+), 3 deletions(-)
>
> diff --git a/tools/testing/selftests/livepatch/functions.sh b/tools/testing/selftests/livepatch/functions.sh
> index 31eb09e38729..a6e3d5517a6f 100644
> --- a/tools/testing/selftests/livepatch/functions.sh
> +++ b/tools/testing/selftests/livepatch/functions.sh
> @@ -7,6 +7,9 @@
> MAX_RETRIES=600
> RETRY_INTERVAL=".1" # seconds
>
> +# Kselftest framework requirement - SKIP code is 4
> +ksft_skip=4
> +
> # log(msg) - write message to kernel log
> # msg - insightful words
> function log() {
> @@ -18,7 +21,16 @@ function log() {
> function skip() {
> log "SKIP: $1"
> echo "SKIP: $1" >&2
> - exit 4
> + exit $ksft_skip
> +}
> +
> +# root test
> +function is_root() {
> + uid=$(id -u)
> + if [ $uid -ne 0 ]; then
> + echo "skip all tests: must be run as root" >&2
> + exit $ksft_skip
> + fi
> }
>
> # die(msg) - game over, man
> @@ -62,6 +74,7 @@ function set_ftrace_enabled() {
> # for verbose livepatching output and turn on
> # the ftrace_enabled sysctl.
> function setup_config() {
> + is_root
> push_config
> set_dynamic_debug
> set_ftrace_enabled 1
> diff --git a/tools/testing/selftests/livepatch/test-state.sh b/tools/testing/selftests/livepatch/test-state.sh
> index dc2908c22c26..a08212708115 100755
> --- a/tools/testing/selftests/livepatch/test-state.sh
> +++ b/tools/testing/selftests/livepatch/test-state.sh
> @@ -8,8 +8,7 @@ MOD_LIVEPATCH=test_klp_state
> MOD_LIVEPATCH2=test_klp_state2
> MOD_LIVEPATCH3=test_klp_state3
>
> -set_dynamic_debug
> -
> +setup_config
>
> # TEST: Loading and removing a module that modifies the system state
>
> --
> 2.20.1
>
Thanks for fixing these, Shuah.
Acked-by: Joe Lawrence <joe.lawrence@redhat.com>
-- Joe
next prev parent reply other threads:[~2019-12-16 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 19:18 [PATCH v2] selftests: livepatch: Fix it to do root uid check and skip Shuah Khan
2019-12-16 21:01 ` Joe Lawrence [this message]
2019-12-17 9:02 ` Petr Mladek
2019-12-17 15:08 ` Shuah Khan
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=20191216210118.GA28841@redhat.com \
--to=joe.lawrence@redhat.com \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
/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;
as well as URLs for NNTP newsgroup(s).