From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Aring Date: Wed, 22 Jun 2022 14:45:05 -0400 Subject: [Cluster-devel] [PATCH RESEND v5.19-rc3 02/20] fs: dlm: remove may interrupted message In-Reply-To: <20220622184523.1886869-1-aahringo@redhat.com> References: <20220622184523.1886869-1-aahringo@redhat.com> Message-ID: <20220622184523.1886869-3-aahringo@redhat.com> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Commit bcfad4265ced ("dlm: improve plock logging if interrupted") shall improve the printout to give the user a reason why a dlm plock op function was not found anymore when the kernel dlm op side was sending a operation request to the user space. However this situation was still confusing users about those messages. A new approach will avoid such message and if they occur there is a bug. Signed-off-by: Alexander Aring --- fs/dlm/plock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/dlm/plock.c b/fs/dlm/plock.c index 7cab5d27132b..32eda1f43d22 100644 --- a/fs/dlm/plock.c +++ b/fs/dlm/plock.c @@ -443,7 +443,7 @@ static ssize_t dev_write(struct file *file, const char __user *u, size_t count, else wake_up(&recv_wq); } else - log_print("%s: no op %x %llx - may got interrupted?", __func__, + log_print("%s: no op %x %llx", __func__, info.fsid, (unsigned long long)info.number); return count; } -- 2.31.1