Hi Miroslav,
On 1/17/2025 9:10 PM, Miroslav Benes wrote:
Hi,
Good question. Have you seen this message when running the selftests,
please?
I wonder which test could trigger it. I do not recall any test
livepatch where the transition might get blocked for too long.
There is the self test with a blocked transition ("busy target
module") but the waiting is stopped much earlier there.
The message probably might get printed when the selftests are
called on a huge and very busy system. But then we might get
into troubles also with other timeouts. So it would be nice
to know more details about when this happens.
We're trying to port livepatch to RISC-V. In my qemu virt VM in a cloud
environment, all tests passed except test-syscall.sh. Mostly it complained the
missed dmesg "signaling remaining tasks". I want to confirm from your experts
that in theory the failure is expected, or if we could filter out this
potential dmesg completely.
it might also mean that the implementation on risc-v is not complete yet.
If there are many unreliable stacktraces, for example, the live patching
infrastructure would retry many times which causes delays and you might
run into the message eventually. It pays off to enable dynamic_debug for
kernel/livepatch/ and see if there is anything suspicious in the output.
Yes, this is just an in-progress work and we'll try your suggestion to
help developing.
Thanks a lot,
laokz
