From: Joe Lawrence <joe.lawrence@redhat.com>
To: live-patching@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] selftests/livepatch: push and pop dynamic debug config
Date: Thu, 18 Jul 2019 16:42:25 -0400 [thread overview]
Message-ID: <e5027867-88db-fa45-6767-286f3b7b86ad@redhat.com> (raw)
In-Reply-To: <20190718202948.3404-1-joe.lawrence@redhat.com>
On 7/18/19 4:29 PM, Joe Lawrence wrote:
> The livepatching self-tests tweak the dynamic debug config to verify
> the kernel log during the tests. Enhance set_dynamic_debug() so that
> the config changes are restored when the script exits.
>
> Note this functionality needs to keep in sync with:
> - dynamic_debug input/output formatting
> - functions affected by set_dynamic_debug()
>
> For example, push_dynamic_debug() transforms:
> kernel/livepatch/transition.c:530 [livepatch]klp_init_transition =_ "'%s': initializing %s transition\012"
> to:
> file kernel/livepatch/transition.c line 530 =_
>
> Signed-off-by: Joe Lawrence <joe.lawrence@redhat.com>
> ---
> .../testing/selftests/livepatch/functions.sh | 26 ++++++++++++++-----
> 1 file changed, 20 insertions(+), 6 deletions(-)
>
> diff --git a/tools/testing/selftests/livepatch/functions.sh b/tools/testing/selftests/livepatch/functions.sh
> index de5a504ffdbc..860f27665ebd 100644
> --- a/tools/testing/selftests/livepatch/functions.sh
> +++ b/tools/testing/selftests/livepatch/functions.sh
> @@ -29,13 +29,27 @@ function die() {
> exit 1
> }
>
> -# set_dynamic_debug() - setup kernel dynamic debug
> -# TODO - push and pop this config?
> +function push_dynamic_debug() {
> + DYNAMIC_DEBUG=$(grep '^kernel/livepatch' /sys/kernel/debug/dynamic_debug/control | \
> + awk -F'[: ]' '{print "file " $1 " line " $2 " " $4}')
> +}
> +
> +function pop_dynamic_debug() {
> + if [[ -n "$DYNAMIC_DEBUG" ]]; then
> + echo -n "$DYNAMIC_DEBUG" > /sys/kernel/debug/dynamic_debug/control
> + fi
> +}
> +
> +# set_dynamic_debug() - save the current dynamic debug config and tweak
> +# it for the self-tests. Set a script exit trap
> +# that restores the original config.
> function set_dynamic_debug() {
> - cat << EOF > /sys/kernel/debug/dynamic_debug/control
> -file kernel/livepatch/* +p
> -func klp_try_switch_task -p
> -EOF
> + push_dynamic_debug
> + trap pop_dynamic_debug EXIT INT TERM HUP
> + cat <<-EOF > /sys/kernel/debug/dynamic_debug/control
> + file kernel/livepatch/* +p
> + func klp_try_switch_task -p
> + EOF
> }
>
> # loop_until(cmd) - loop a command until it is successful or $MAX_RETRIES,
>
I took a stab as this while working on "[PATCH v2] selftests/livepatch:
add test skip handling", which this applies on top of.
It works for me, though I feel that the
/sys/kernel/debug/dynamic_debug/control output to input translation is
brittle. It would be nice to have some kind of mass export/import
capability for that interface.
-- Joe
next prev parent reply other threads:[~2019-07-18 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 20:29 [PATCH] selftests/livepatch: push and pop dynamic debug config Joe Lawrence
2019-07-18 20:42 ` Joe Lawrence [this message]
2019-07-19 10:46 ` Petr Mladek
2019-07-30 17:31 ` Joe Lawrence
2019-07-30 21:26 ` shuah
2019-07-30 21:52 ` shuah
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=e5027867-88db-fa45-6767-286f3b7b86ad@redhat.com \
--to=joe.lawrence@redhat.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=live-patching@vger.kernel.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