From: Joe Lawrence <joe.lawrence@redhat.com>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@lists.ozlabs.org
Cc: live-patching@vger.kernel.org,
Ryan Sullivan <rysulliv@redhat.com>,
Nicholas Piggin <npiggin@gmail.com>
Subject: Re: Recent Power changes and stack_trace_save_tsk_reliable?
Date: Wed, 30 Aug 2023 17:47:35 -0400 [thread overview]
Message-ID: <cca0770c-1510-3a02-d0ba-82ee5a0ae4f2@redhat.com> (raw)
In-Reply-To: <87il8xxcg7.fsf@mail.lhotse>
On 8/30/23 02:37, Michael Ellerman wrote:
> Michael Ellerman <mpe@ellerman.id.au> writes:
>> Joe Lawrence <joe.lawrence@redhat.com> writes:
>>> Hi ppc-dev list,
>>>
>>> We noticed that our kpatch integration tests started failing on ppc64le
>>> when targeting the upstream v6.4 kernel, and then confirmed that the
>>> in-tree livepatching kselftests similarly fail, too. From the kselftest
>>> results, it appears that livepatch transitions are no longer completing.
>>
>> Hi Joe,
>>
>> Thanks for the report.
>>
>> I thought I was running the livepatch tests, but looks like somewhere
>> along the line my kernel .config lost CONFIG_TEST_LIVEPATCH=m, so I have
>> been running the test but it just skips. :/
>>
That config option is easy to drop if you use `make localmodconfig` to
try and expedite the builds :D Been there, done that too many times.
>> I can reproduce the failure, and will see if I can bisect it more
>> successfully.
>
> It's caused by:
>
> eed7c420aac7 ("powerpc: copy_thread differentiate kthreads and user mode threads")
>
> Which is obvious in hindsight :)
>
> The diff below fixes it for me, can you test that on your setup?
>
Thanks for the fast triage of this one. The proposed fix works well on
our setup. I have yet to try the kpatch integration tests with this,
but I can verify that all of the kernel livepatching kselftests now
happily run.
--
Joe
> A proper fix will need to be a bit bigger because the comments in there
> are all slightly wrong now since the above commit.
>
> Possibly we can also rework that code more substantially now that
> copy_thread() is more careful about setting things up, but that would be
> a follow-up.
>
> diff --git a/arch/powerpc/kernel/stacktrace.c b/arch/powerpc/kernel/stacktrace.c
> index 5de8597eaab8..d0b3509f13ee 100644
> --- a/arch/powerpc/kernel/stacktrace.c
> +++ b/arch/powerpc/kernel/stacktrace.c
> @@ -73,7 +73,7 @@ int __no_sanitize_address arch_stack_walk_reliable(stack_trace_consume_fn consum
> bool firstframe;
>
> stack_end = stack_page + THREAD_SIZE;
> - if (!is_idle_task(task)) {
> + if (!(task->flags & PF_KTHREAD)) {
> /*
> * For user tasks, this is the SP value loaded on
> * kernel entry, see "PACAKSAVE(r13)" in _switch() and
>
>
> cheers
>
next prev parent reply other threads:[~2023-08-30 21:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 15:12 Recent Power changes and stack_trace_save_tsk_reliable? Joe Lawrence
2023-08-30 0:32 ` Michael Ellerman
2023-08-30 6:37 ` Michael Ellerman
2023-08-30 21:47 ` Joe Lawrence [this message]
2023-09-20 14:16 ` Petr Mladek
2023-09-21 12:26 ` Michael Ellerman
2023-09-21 13:22 ` Joe Lawrence
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=cca0770c-1510-3a02-d0ba-82ee5a0ae4f2@redhat.com \
--to=joe.lawrence@redhat.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=live-patching@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=rysulliv@redhat.com \
/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).