From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: Petr Mladek <pmladek@suse.com>
Cc: jikos@kernel.org, mbenes@suse.cz, joe.lawrence@redhat.com,
shuah@kernel.org, mpe@ellerman.id.au, npiggin@gmail.com,
christophe.leroy@csgroup.eu, naveen@kernel.org,
live-patching@vger.kernel.org, linux-kselftest@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] selftests: livepatch: handle PRINTK_CALLER in check_result()
Date: Tue, 21 Jan 2025 16:48:37 +0530 [thread overview]
Message-ID: <c91cc2c5-2f82-43e8-a726-bebc4134ad32@linux.ibm.com> (raw)
In-Reply-To: <Z450ohzYtxVEMh1_@pathway.suse.cz>
On 1/20/25 9:36 PM, Petr Mladek wrote:
> On Sun 2025-01-19 22:02:38, Madhavan Srinivasan wrote:
>> Some arch configs (like ppc64) enable CONFIG_PRINTK_CALLER,
>> which adds the caller id as part of the dmesg. With recent
>> util-linux's update 467a5b3192f16 ('dmesg: add caller_id support')
>> the standard "dmesg" has been enhanced to print PRINTK_CALLER fields.
>>
>> Due to this, even though the expected vs observed are same,
>> end testcase results are failed.
>>
>> -% insmod test_modules/test_klp_livepatch.ko
>> -livepatch: enabling patch 'test_klp_livepatch'
>> -livepatch: 'test_klp_livepatch': initializing patching transition
>> -livepatch: 'test_klp_livepatch': starting patching transition
>> -livepatch: 'test_klp_livepatch': completing patching transition
>> -livepatch: 'test_klp_livepatch': patching complete
>> -% echo 0 > /sys/kernel/livepatch/test_klp_livepatch/enabled
>> -livepatch: 'test_klp_livepatch': initializing unpatching transition
>> -livepatch: 'test_klp_livepatch': starting unpatching transition
>> -livepatch: 'test_klp_livepatch': completing unpatching transition
>> -livepatch: 'test_klp_livepatch': unpatching complete
>> -% rmmod test_klp_livepatch
>> +[ T3659] % insmod test_modules/test_klp_livepatch.ko
>> +[ T3682] livepatch: enabling patch 'test_klp_livepatch'
>> +[ T3682] livepatch: 'test_klp_livepatch': initializing patching transition
>> +[ T3682] livepatch: 'test_klp_livepatch': starting patching transition
>> +[ T826] livepatch: 'test_klp_livepatch': completing patching transition
>> +[ T826] livepatch: 'test_klp_livepatch': patching complete
>> +[ T3659] % echo 0 > /sys/kernel/livepatch/test_klp_livepatch/enabled
>> +[ T3659] livepatch: 'test_klp_livepatch': initializing unpatching transition
>> +[ T3659] livepatch: 'test_klp_livepatch': starting unpatching transition
>> +[ T789] livepatch: 'test_klp_livepatch': completing unpatching transition
>> +[ T789] livepatch: 'test_klp_livepatch': unpatching complete
>> +[ T3659] % rmmod test_klp_livepatch
>>
>> ERROR: livepatch kselftest(s) failed
>> not ok 1 selftests: livepatch: test-livepatch.sh # exit=1
>>
>> Currently the check_result() handles the "[time]" removal from
>> the dmesg. Enhance the check to also handle removal of "[Thread Id]"
>> or "[CPU Id]".
>>
>> Signed-off-by: Madhavan Srinivasan <maddy@linux.ibm.com>
>
> Looks and works well:
>
> Reviewed-by: Petr Mladek <pmladek@suse.com>
> Tested-by: Petr Mladek <pmladek@suse.com>
>
> Best Regards,
> Petr
>
> PS: The merge window for 6.14 has started yesterday. Every change
> should spend at least few days in linux-next and I have already
> sent a pull request so it is kind of late for 6.14.
>
> If there is a demand, I could still queue it for 6.14 in the 2nd
> half of the merge window or for rc2. There is only small group
> of people interested into the livepatch selftests anyway.
Thanks. No urgency from my end.
next prev parent reply other threads:[~2025-01-21 11:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-19 16:32 [PATCH v2] selftests: livepatch: handle PRINTK_CALLER in check_result() Madhavan Srinivasan
2025-01-20 12:54 ` Miroslav Benes
2025-01-20 16:06 ` Petr Mladek
2025-01-21 11:18 ` Madhavan Srinivasan [this message]
2025-01-27 11:35 ` Petr Mladek
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=c91cc2c5-2f82-43e8-a726-bebc4134ad32@linux.ibm.com \
--to=maddy@linux.ibm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=pmladek@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).