DLM: fix NULL pointer dereference in send_to_sock()
The writequeue and writequeue_lock member of othercon was not initialized. If lowcomms_state_change() is called from network layer, othercon->swork may be scheduled. In this case, send_to_sock() will generate a NULL pointer reference. We avoid this problem by correctly initializing writequeue and writequeue_lock member of othercon. Signed-off-by:Tadashi Miyauchi <miyauchi@toshiba-tops.co.jp> Signed-off-by:
Tsutomu Owa <tsutomu.owa@toshiba.co.jp> Signed-off-by:
David Teigland <teigland@redhat.com>
Showing
Please register or sign in to comment