From: Petr Mladek <pmladek@suse.com>
To: "Ricardo B. Marlière" <rbm@suse.com>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
Joe Lawrence <joe.lawrence@redhat.com>,
Shuah Khan <shuah@kernel.org>,
live-patching@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org,
Marcos Paulo de Souza <mpdesouza@suse.com>
Subject: Re: [PATCH] selftests/livepatch: Ignore NO_SUPPORT line in dmesg
Date: Wed, 20 Aug 2025 13:56:56 +0200 [thread overview]
Message-ID: <aKW4CApORh7o73nz@pathway.suse.cz> (raw)
In-Reply-To: <20250819-selftests-lp_taint_flag-v1-1-a94a62a47683@suse.com>
On Tue 2025-08-19 14:37:01, Ricardo B. Marlière wrote:
> Some systems might disable unloading a livepatch and when running tests on
> them they fail like the following:
>
> $ ./run_kselftest.sh -c livepatch
> TAP version 13
> 1..8
> # selftests: livepatch: test-livepatch.sh
> # TEST: basic function patching ... not ok
> #
> # --- expected
> # +++ result
> # @@ -5,6 +5,7 @@ livepatch: 'test_klp_livepatch': starting
> # livepatch: 'test_klp_livepatch': completing patching transition
> # livepatch: 'test_klp_livepatch': patching complete
> # % echo 0 > /sys/kernel/livepatch/test_klp_livepatch/enabled
> # +livepatch: attempt to disable live patch test_klp_livepatch, setting
> NO_SUPPORT taint flag
> # livepatch: 'test_klp_livepatch': initializing unpatching transition
> # livepatch: 'test_klp_livepatch': starting unpatching transition
> # livepatch: 'test_klp_livepatch': completing unpatching transition
> #
> # ERROR: livepatch kselftest(s) failed
This seems to be a SUSE-specific feature. The upstream kernel does not
even know the NO_SUPPORT taint flag.
This patch is not for upstream. But we should add it into SUSE
kernel sources.
Best Regards,
Petr
prev parent reply other threads:[~2025-08-20 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 17:37 [PATCH] selftests/livepatch: Ignore NO_SUPPORT line in dmesg Ricardo B. Marlière
2025-08-19 19:36 ` Ricardo B. Marlière
2025-08-20 11:56 ` Petr Mladek [this message]
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=aKW4CApORh7o73nz@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mpdesouza@suse.com \
--cc=rbm@suse.com \
--cc=shuah@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;
as well as URLs for NNTP newsgroup(s).