dlm: improve plock logging if interrupted
authorAlexander Aring <aahringo@redhat.com>
Mon, 4 Apr 2022 20:06:34 +0000 (16:06 -0400)
committerDavid Teigland <teigland@redhat.com>
Wed, 6 Apr 2022 19:02:09 +0000 (14:02 -0500)
commitbcfad4265cedf3adcac355e994ef9771b78407bd
treec703241794a1da736c29e66873df87bf25b9ccf8
parenta800ba77fd285c6391a82819867ac64e9ab3af46
dlm: improve plock logging if interrupted

This patch changes the log level if a plock is removed when interrupted
from debug to info. Additional it signals now that the plock entity was
removed to let the user know what's happening.

If on a dev_write() a pending plock cannot be find it will signal that
it might have been removed because wait interruption.

Before this patch there might be a "dev_write no op ..." info message
and the users can only guess that the plock was removed before because
the wait interruption. To be sure that is the case we log both messages
on the same log level.

Let both message be logged on info layer because it should not happened
a lot and if it happens it should be clear why the op was not found.

Signed-off-by: Alexander Aring <aahringo@redhat.com>
Signed-off-by: David Teigland <teigland@redhat.com>
fs/dlm/plock.c