> On 29 Oct 2024, at 21:45, Thom Brown <t...@linux.com> wrote:
>
> It clearly checks for interrupts, but when I saw this issue happen, it
> wasn't interruptible.
Perhaps, that was different multixacts?
When I was observing this pathology on Standby, it was a stream of different
reads encountering different multis.
Either way startup can cancel locking process on it's own. Or is it the case
that cancel was not enough, did you actually need termination, not cancel?
Thanks!
Best regards, Andrey Borodin.
