fs: dlm: don't use RCOM_NAMES for version detection
authorAlexander Aring <aahringo@redhat.com>
Tue, 1 Aug 2023 18:09:50 +0000 (14:09 -0400)
committerDavid Teigland <teigland@redhat.com>
Thu, 10 Aug 2023 15:33:03 +0000 (10:33 -0500)
commita3d85fcf268ea40c024e864b219b72516236d15b
tree4230698190384bd2d83dfae7cf7ea39a4b0ecce6
parent63e711b081609748d631fc3a08b14ba01c8e4f16
fs: dlm: don't use RCOM_NAMES for version detection

Currently RCOM_STATUS and RCOM_NAMES inclusive their replies are being
used to determine the DLM version. The RCOM_NAMES messages are triggered
in DLM recovery when calling dlm_recover_directory() only. At this time
the DLM version need to be determined. I ran some tests and did not
expirenced some issues. When the DLM version detection was developed
probably I run once in a case of RCOM_NAMES and the version was not
detected yet. However it seems to be not necessary.

For backwards compatibility we still need to accept RCOM_NAMES messages
which are not protected regarding the DLM message reliability layer aka
stateless message. This patch changes that RCOM_NAMES we are sending out
after this patch are not stateless anymore.

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