Lars Ellenberg f479ea0661 drbd: send intermediate state change results to the peer
DRBD state changes schedule after_state_ch() actions to a worker thread,
which decides on the old and new states of that change, whether to send
an informational state update packet (P_STATE) to the peer.
If it decides to drbd_send_state(), it would however always send the
_curent_ state, which, if a second state change happens before the
after_state_ch() of the first ran, may "fast-forward" the peer's view
about this node.  In most cases that is harmless, but sometimes this can
confuse DRBD, for example into not actually starting a necessary resync
if you do a very tight detach/attach loop on a Connected Secondary.

Fix this by always sending the "new" state of the respective state
transition which scheduled this after_state_ch() work.

Signed-off-by: Philipp Reisner <philipp.reisner@linbit.com>
Signed-off-by: Lars Ellenberg <lars.ellenberg@linbit.com>
2012-05-09 15:15:56 +02:00
..
2012-01-03 22:54:07 -05:00
2012-01-14 15:07:24 -08:00
2011-08-08 11:40:15 +02:00
2012-03-28 18:30:03 +01:00
2012-03-22 10:47:50 -05:00
2011-12-12 12:42:12 +01:00
2011-12-10 19:52:46 +01:00
2012-04-16 18:34:12 -07:00
2012-03-28 18:30:03 +01:00
2012-01-05 08:34:29 +01:00