Bug 1955813 - bad client message causes closed connection and released leases
Summary: bad client message causes closed connection and released leases
Keywords:
Status: POST
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: sanlock
Version: ---
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: beta
: ---
Assignee: David Teigland
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1952345
TreeView+ depends on / blocked
 
Reported: 2021-04-30 20:45 UTC by David Teigland
Modified: 2021-05-06 14:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)

Description David Teigland 2021-04-30 20:45:44 UTC
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):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:


Note You need to log in before you can comment on or make changes to this bug.