Description of problem:
If the sanlock daemon receives a bad message from a client, it will respond by closing the client connection and releasing any resource leases that are held by the client. The client may continue running, using the leases, unaware of the problem. The sanlock daemon should just ignore bad messages and leave the client connection and leases in place.
One indication of this problem that would appear in /var/log/sanlock.log is:
"ci 2 recv 32 magic 0 vs 4282010" (message contains wrong magic number)
Version-Release number of selected component (if applicable):
Steps to Reproduce: