This patch will change to ignore unexpected for RCOM_NAMES/RCOM_STATUS
messages. Those message are there to provide a version detection because
those are messages which are exchanged as first to detect the dlm
version. Due some DLM behaviour and being still backwards compatible
those messages are not part of the new reliable DLM OPTS encapsulation
header. On the other hand those message have their own retransmit
handling with a sequence number match, means if the sequence number
doesn't match DLM RCOM application layer will filter it out. When we get
a unexpected non dlm opts msg we should allow them and DLM RCOM will
filter it out if the sequence number does not match.

Signed-off-by: Alexander Aring <aahri...@redhat.com>
---
 fs/dlm/midcomms.c | 12 ++----------
 1 file changed, 2 insertions(+), 10 deletions(-)

diff --git a/fs/dlm/midcomms.c b/fs/dlm/midcomms.c
index ecd81018d1cf..dbc998b2748b 100644
--- a/fs/dlm/midcomms.c
+++ b/fs/dlm/midcomms.c
@@ -606,16 +606,8 @@ dlm_midcomms_recv_node_lookup(int nodeid, const union 
dlm_packet *p,
                                case DLM_ESTABLISHED:
                                        break;
                                default:
-                                       /* some invalid state passive shutdown
-                                        * was failed, we try to reset and
-                                        * hope it will go on.
-                                        */
-                                       log_print("reset node %d because 
shutdown stuck",
-                                                 node->nodeid);
-
-                                       midcomms_node_reset(node);
-                                       node->state = DLM_ESTABLISHED;
-                                       break;
+                                       spin_unlock(&node->state_lock);
+                                       return NULL;
                                }
                                spin_unlock(&node->state_lock);
                        }
-- 
2.31.1

Reply via email to