tipc: Fix node lock reclamation issues in broadcast link reception
authorAllan Stephens <allan.stephens@windriver.com>
Wed, 26 Oct 2011 19:33:44 +0000 (15:33 -0400)
committerPaul Gortmaker <paul.gortmaker@windriver.com>
Mon, 6 Feb 2012 21:59:17 +0000 (16:59 -0500)
commit8a275a6a30ba871eb34ea41c1fbb507039f4c0dc
tree249a3987649b2e7c35c5099071ecaf1355308c80
parent57732560d1aa7d454d10e557f8959d19d1454174
tipc: Fix node lock reclamation issues in broadcast link reception

Fixes a pair of problems in broadcast link message reception code
relating to the reclamation of the node lock after consuming an
in-sequence message.

1) Now retests to see if the sending node is still up after reclaiming
   the node lock, and bails out if it is non-operational.

2) Now manipulates the node's deferred message queue only after
   reclaiming the node lock, rather than using queue head pointer
   information that was cached previously.

Signed-off-by: Allan Stephens <allan.stephens@windriver.com>
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
net/tipc/bcast.c