]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
dlm: improve plock logging if interrupted
authorAlexander Aring <aahringo@redhat.com>
Mon, 4 Apr 2022 20:06:34 +0000 (16:06 -0400)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 30 Aug 2023 14:18:10 +0000 (16:18 +0200)
commit33e9c610e337ae6f31fa8a3ad169df043140a3cf
tree09ea858b09d4629999e5310bf6547d9b7af37390
parentd9ce077f8b1f731407e6b612b03bba464fd18d9b
dlm: improve plock logging if interrupted

[ Upstream commit bcfad4265cedf3adcac355e994ef9771b78407bd ]

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>
Stable-dep-of: 57e2c2f2d94c ("fs: dlm: fix mismatch of plock results from userspace")
Signed-off-by: Sasha Levin <sashal@kernel.org>
fs/dlm/plock.c