public inbox for live-patching@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Joe Lawrence <joe.lawrence@redhat.com>, linuxppc-dev@lists.ozlabs.org
Cc: live-patching@vger.kernel.org,
	Joe Lawrence <joe.lawrence@redhat.com>,
	Ryan Sullivan <rysulliv@redhat.com>
Subject: Re: Recent Power changes and stack_trace_save_tsk_reliable?
Date: Wed, 30 Aug 2023 10:32:15 +1000	[thread overview]
Message-ID: <87o7ipxtdc.fsf@mail.lhotse> (raw)
In-Reply-To: <ZO4K6hflM/arMjse@redhat.com>

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. :/

I can reproduce the failure, and will see if I can bisect it more
successfully.

cheers

  reply	other threads:[~2023-08-30  0:33 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 [this message]
2023-08-30  6:37   ` Michael Ellerman
2023-08-30 21:47     ` Joe Lawrence
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=87o7ipxtdc.fsf@mail.lhotse \
    --to=mpe@ellerman.id.au \
    --cc=joe.lawrence@redhat.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=live-patching@vger.kernel.org \
    --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