Re: selftests/livepatch: question about dmesg "signaling remaining tasks"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed 2025-01-15 08:32:12, laokz@xxxxxxxxxxx wrote:
> When do livepatch transition, kernel call klp_try_complete_transition() which in-turn might call klp_send_signals(). klp_send_signal() has the code:
> 
>         if (klp_signals_cnt == SIGNALS_TIMEOUT)
>                 pr_notice("signaling remaining tasks\n");
> 
> Do we need to match or filter out this message when check_result? And here klp_signals_cnt MUST EQUAL to SIGNALS_TIMEOUT, right?

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.

Best Regards,
Petr




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux Kernel]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux