diff options
| author | Alexander Aring <[email protected]> | 2023-08-01 18:09:50 +0000 |
|---|---|---|
| committer | David Teigland <[email protected]> | 2023-08-10 15:33:03 +0000 |
| commit | a3d85fcf268ea40c024e864b219b72516236d15b (patch) | |
| tree | 4230698190384bd2d83dfae7cf7ea39a4b0ecce6 /tools/perf/builtin-script.c | |
| parent | fs: dlm: create midcomms nodes when configure (diff) | |
| download | kernel-a3d85fcf268ea40c024e864b219b72516236d15b.tar.gz kernel-a3d85fcf268ea40c024e864b219b72516236d15b.zip | |
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 <[email protected]>
Signed-off-by: David Teigland <[email protected]>
Diffstat (limited to 'tools/perf/builtin-script.c')
0 files changed, 0 insertions, 0 deletions