Skip to content

Commit efc63e8

Browse files
committed
Block the mon update removing a preimage until upstream mon writes
When we forward a payment and receive an `update_fulfill_htlc` message from the downstream channel, we immediately claim the HTLC on the upstream channel, before even doing a `commitment_signed` dance on the downstream channel. This implies that our `ChannelMonitorUpdate`s "go out" in the right order - first we ensure we'll get our money by writing the preimage down, then we write the update that resolves giving money on the downstream node. This is safe as long as `ChannelMonitorUpdate`s complete in the order in which they are generated, but of course looking forward we want to support asynchronous updates, which may complete in any order. Thus, here, we enforce the correct ordering by blocking the downstream `ChannelMonitorUpdate` until the upstream one completes. Like the `PaymentSent` event handling we do so only for the `revoke_and_ack` `ChannelMonitorUpdate`, ensuring the preimage-containing upstream update has a full RTT to complete before we actually manage to slow anything down.
1 parent cb923c6 commit efc63e8

File tree

3 files changed

+216
-34
lines changed

3 files changed

+216
-34
lines changed

lightning/src/ln/chanmon_update_fail_tests.rs

Lines changed: 136 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3067,18 +3067,27 @@ fn test_blocked_chan_preimage_release() {
30673067
check_added_monitors(&nodes[1], 1); // We generate only a preimage monitor update
30683068
assert!(nodes[1].node.get_and_clear_pending_msg_events().is_empty());
30693069

3070-
// Finish the CS dance between nodes[0] and nodes[1].
3071-
do_commitment_signed_dance(&nodes[1], &nodes[0], &as_htlc_fulfill_updates.commitment_signed, false, false);
3070+
// Finish the CS dance between nodes[0] and nodes[1]. Note that until the final RAA CS is held
3071+
// until the full set of `ChannelMonitorUpdate`s on the nodes[1] <-> nodes[2] channel are
3072+
// complete, while the preimage that we care about ensuring is on disk did make it there above,
3073+
// the holding logic doesn't care about the type of update, it just cares that there is one.
3074+
nodes[1].node.handle_commitment_signed(&nodes[0].node.get_our_node_id(), &as_htlc_fulfill_updates.commitment_signed);
3075+
check_added_monitors(&nodes[1], 1);
3076+
let (a, raa) = do_main_commitment_signed_dance(&nodes[1], &nodes[0], false);
3077+
assert!(a.is_none());
3078+
3079+
nodes[1].node.handle_revoke_and_ack(&nodes[0].node.get_our_node_id(), &raa);
30723080
check_added_monitors(&nodes[1], 0);
3081+
assert!(nodes[1].node.get_and_clear_pending_msg_events().is_empty());
30733082

30743083
let events = nodes[1].node.get_and_clear_pending_events();
30753084
assert_eq!(events.len(), 3);
30763085
if let Event::PaymentSent { .. } = events[0] {} else { panic!(); }
30773086
if let Event::PaymentPathSuccessful { .. } = events[2] {} else { panic!(); }
30783087
if let Event::PaymentForwarded { .. } = events[1] {} else { panic!(); }
30793088

3080-
// The event processing should release the last RAA update.
3081-
check_added_monitors(&nodes[1], 1);
3089+
// The event processing should release the last RAA updates on both channels.
3090+
check_added_monitors(&nodes[1], 2);
30823091

30833092
// When we fetch the next update the message getter will generate the next update for nodes[2],
30843093
// generating a further monitor update.
@@ -3089,3 +3098,126 @@ fn test_blocked_chan_preimage_release() {
30893098
do_commitment_signed_dance(&nodes[2], &nodes[1], &bs_htlc_fulfill_updates.commitment_signed, false, false);
30903099
expect_payment_sent(&nodes[2], payment_preimage_2, None, true, true);
30913100
}
3101+
3102+
fn do_test_inverted_mon_completion_order(complete_bc_commitment_dance: bool) {
3103+
// When we forward a payment and receive an `update_fulfill_htlc` message from the downstream
3104+
// channel, we immediately claim the HTLC on the upstream channel, before even doing a
3105+
// `commitment_signed` dance on the downstream channel. This implies that our
3106+
// `ChannelMonitorUpdate`s "go out" in the right order - first we ensure we'll get our money,
3107+
// then we write the update that resolves giving money on the downstream node. This is safe as
3108+
// long as `ChannelMonitorUpdate`s complete in the order in which they are generated, but of
3109+
// course this may not be the case. For asynchronous update writes, we have to ensure monitor
3110+
// updates can block each other, preventing the inversion all together.
3111+
let chanmon_cfgs = create_chanmon_cfgs(3);
3112+
let node_cfgs = create_node_cfgs(3, &chanmon_cfgs);
3113+
3114+
let persister;
3115+
let new_chain_monitor;
3116+
let nodes_1_deserialized;
3117+
3118+
let node_chanmgrs = create_node_chanmgrs(3, &node_cfgs, &[None, None, None]);
3119+
let mut nodes = create_network(3, &node_cfgs, &node_chanmgrs);
3120+
3121+
let chan_id_ab = create_announced_chan_between_nodes(&nodes, 0, 1).2;
3122+
let chan_id_bc = create_announced_chan_between_nodes(&nodes, 1, 2).2;
3123+
3124+
// Route a payment from A, through B, to C, then claim it on C. Once we pass B the
3125+
// `update_fulfill_htlc` we have a monitor update for both of B's channels. We complete the one
3126+
// on the B<->C channel but leave the A<->B monitor update pending, then reload B.
3127+
let (payment_preimage, payment_hash, _) = route_payment(&nodes[0], &[&nodes[1], &nodes[2]], 100_000);
3128+
3129+
let mon_ab = get_monitor!(nodes[1], chan_id_ab).encode();
3130+
3131+
nodes[2].node.claim_funds(payment_preimage);
3132+
check_added_monitors(&nodes[2], 1);
3133+
expect_payment_claimed!(nodes[2], payment_hash, 100_000);
3134+
3135+
chanmon_cfgs[1].persister.set_update_ret(ChannelMonitorUpdateStatus::InProgress);
3136+
let cs_updates = get_htlc_update_msgs(&nodes[2], &nodes[1].node.get_our_node_id());
3137+
nodes[1].node.handle_update_fulfill_htlc(&nodes[2].node.get_our_node_id(), &cs_updates.update_fulfill_htlcs[0]);
3138+
3139+
// B generates a new monitor update for the A <-> B channel, but doesn't send the new messages
3140+
// for it since the monitor update is marked in-progress.
3141+
check_added_monitors(&nodes[1], 1);
3142+
assert!(nodes[1].node.get_and_clear_pending_msg_events().is_empty());
3143+
3144+
// Now step the Commitment Signed Dance between B and C forward a bit (or fully), ensuring we
3145+
// won't get the preimage when the nodes reconnect, at which point we have to ensure we get it
3146+
// from the ChannelMonitor.
3147+
nodes[1].node.handle_commitment_signed(&nodes[2].node.get_our_node_id(), &cs_updates.commitment_signed);
3148+
check_added_monitors(&nodes[1], 1);
3149+
if complete_bc_commitment_dance {
3150+
let (bs_revoke_and_ack, bs_commitment_signed) = get_revoke_commit_msgs!(nodes[1], nodes[2].node.get_our_node_id());
3151+
nodes[2].node.handle_revoke_and_ack(&nodes[1].node.get_our_node_id(), &bs_revoke_and_ack);
3152+
check_added_monitors(&nodes[2], 1);
3153+
nodes[2].node.handle_commitment_signed(&nodes[1].node.get_our_node_id(), &bs_commitment_signed);
3154+
check_added_monitors(&nodes[2], 1);
3155+
let cs_raa = get_event_msg!(nodes[2], MessageSendEvent::SendRevokeAndACK, nodes[1].node.get_our_node_id());
3156+
3157+
// At this point node B still hasn't persisted the `ChannelMonitorUpdate` with the
3158+
// preimage in the A <-> B channel, which will prevent it from persisting the
3159+
// `ChannelMonitorUpdate` here to avoid "losing" the preimage.
3160+
nodes[1].node.handle_revoke_and_ack(&nodes[2].node.get_our_node_id(), &cs_raa);
3161+
check_added_monitors(&nodes[1], 0);
3162+
assert!(nodes[1].node.get_and_clear_pending_msg_events().is_empty());
3163+
}
3164+
3165+
// Now reload node B
3166+
let manager_b = nodes[1].node.encode();
3167+
3168+
let mon_bc = get_monitor!(nodes[1], chan_id_bc).encode();
3169+
reload_node!(nodes[1], &manager_b, &[&mon_ab, &mon_bc], persister, new_chain_monitor, nodes_1_deserialized);
3170+
3171+
nodes[0].node.peer_disconnected(&nodes[1].node.get_our_node_id());
3172+
nodes[2].node.peer_disconnected(&nodes[1].node.get_our_node_id());
3173+
3174+
// If we used the latest ChannelManager to reload from, we should have both channels still
3175+
// live. The B <-> C channel's final RAA ChannelMonitorUpdate must still be blocked as
3176+
// before - the ChannelMonitorUpdate for the A <-> B channel hasn't completed.
3177+
// When we call `timer_tick_occurred` we will get that monitor update back, which we'll
3178+
// complete after reconnecting to our peers.
3179+
persister.set_update_ret(ChannelMonitorUpdateStatus::InProgress);
3180+
nodes[1].node.timer_tick_occurred();
3181+
check_added_monitors(&nodes[1], 1);
3182+
assert!(nodes[1].node.get_and_clear_pending_msg_events().is_empty());
3183+
3184+
// Now reconnect B to both A and C. If the B <-> C commitment signed dance wasn't run to
3185+
// the end go ahead and do that, though the -2 in `reconnect_nodes` indicates that we
3186+
// expect to *not* receive the final RAA ChannelMonitorUpdate.
3187+
if complete_bc_commitment_dance {
3188+
reconnect_nodes(ReconnectArgs::new(&nodes[1], &nodes[2]));
3189+
} else {
3190+
let mut reconnect_args = ReconnectArgs::new(&nodes[1], &nodes[2]);
3191+
reconnect_args.pending_htlc_adds = (0, -2);
3192+
reconnect_args.pending_raa = (false, true);
3193+
reconnect_nodes(reconnect_args);
3194+
}
3195+
3196+
reconnect_nodes(ReconnectArgs::new(&nodes[0], &nodes[1]));
3197+
3198+
// (Finally) complete the A <-> B ChannelMonitorUpdate, ensuring the preimage is durably on
3199+
// disk in the proper ChannelMonitor, unblocking the B <-> C ChannelMonitor updating
3200+
// process.
3201+
let (outpoint, _, ab_update_id) = nodes[1].chain_monitor.latest_monitor_update_id.lock().unwrap().get(&chan_id_ab).unwrap().clone();
3202+
nodes[1].chain_monitor.chain_monitor.channel_monitor_updated(outpoint, ab_update_id).unwrap();
3203+
3204+
// When we fetch B's HTLC update messages here (now that the ChannelMonitorUpdate has
3205+
// completed), it will also release the final RAA ChannelMonitorUpdate on the B <-> C
3206+
// channel.
3207+
let bs_updates = get_htlc_update_msgs(&nodes[1], &nodes[0].node.get_our_node_id());
3208+
check_added_monitors(&nodes[1], 1);
3209+
3210+
nodes[0].node.handle_update_fulfill_htlc(&nodes[1].node.get_our_node_id(), &bs_updates.update_fulfill_htlcs[0]);
3211+
do_commitment_signed_dance(&nodes[0], &nodes[1], &bs_updates.commitment_signed, false, false);
3212+
3213+
expect_payment_forwarded!(nodes[1], &nodes[0], &nodes[2], Some(1_000), false, false);
3214+
3215+
// Finally, check that the payment was, ultimately, seen as sent by node A.
3216+
expect_payment_sent(&nodes[0], payment_preimage, None, true, true);
3217+
}
3218+
3219+
#[test]
3220+
fn test_inverted_mon_completion_order() {
3221+
do_test_inverted_mon_completion_order(true);
3222+
do_test_inverted_mon_completion_order(false);
3223+
}

lightning/src/ln/channelmanager.rs

Lines changed: 52 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -628,7 +628,6 @@ pub(crate) enum RAAMonitorUpdateBlockingAction {
628628
}
629629

630630
impl RAAMonitorUpdateBlockingAction {
631-
#[allow(unused)]
632631
fn from_prev_hop_data(prev_hop: &HTLCPreviousHopData) -> Self {
633632
Self::ForwardedPaymentInboundClaim {
634633
channel_id: prev_hop.outpoint.to_channel_id(),
@@ -5087,11 +5086,14 @@ where
50875086
self.pending_outbound_payments.finalize_claims(sources, &self.pending_events);
50885087
}
50895088

5090-
fn claim_funds_internal(&self, source: HTLCSource, payment_preimage: PaymentPreimage, forwarded_htlc_value_msat: Option<u64>, from_onchain: bool, next_channel_outpoint: OutPoint) {
5089+
fn claim_funds_internal(&self, source: HTLCSource, payment_preimage: PaymentPreimage, forwarded_htlc_value_msat: Option<u64>, from_onchain: bool, next_channel_counterparty_node_id: Option<PublicKey>, next_channel_outpoint: OutPoint) {
50915090
match source {
50925091
HTLCSource::OutboundRoute { session_priv, payment_id, path, .. } => {
50935092
debug_assert!(self.background_events_processed_since_startup.load(Ordering::Acquire),
50945093
"We don't support claim_htlc claims during startup - monitors may not be available yet");
5094+
if let Some(pubkey) = next_channel_counterparty_node_id {
5095+
debug_assert_eq!(pubkey, path.hops[0].pubkey);
5096+
}
50955097
let ev_completion_action = EventCompletionAction::ReleaseRAAChannelMonitorUpdate {
50965098
channel_funding_outpoint: next_channel_outpoint,
50975099
counterparty_node_id: path.hops[0].pubkey,
@@ -5102,6 +5104,7 @@ where
51025104
},
51035105
HTLCSource::PreviousHopData(hop_data) => {
51045106
let prev_outpoint = hop_data.outpoint;
5107+
let completed_blocker = RAAMonitorUpdateBlockingAction::from_prev_hop_data(&hop_data);
51055108
let res = self.claim_funds_from_hop(hop_data, payment_preimage,
51065109
|htlc_claim_value_msat| {
51075110
if let Some(forwarded_htlc_value) = forwarded_htlc_value_msat {
@@ -5117,7 +5120,17 @@ where
51175120
next_channel_id: Some(next_channel_outpoint.to_channel_id()),
51185121
outbound_amount_forwarded_msat: forwarded_htlc_value_msat,
51195122
},
5120-
downstream_counterparty_and_funding_outpoint: None,
5123+
downstream_counterparty_and_funding_outpoint:
5124+
if let Some(node_id) = next_channel_counterparty_node_id {
5125+
Some((node_id, next_channel_outpoint, completed_blocker))
5126+
} else {
5127+
// We can only get `None` here if we are processing a
5128+
// `ChannelMonitor`-originated event, in which case we
5129+
// don't care about ensuring we wake the downstream
5130+
// channel's monitor updating - the channel is already
5131+
// closed.
5132+
None
5133+
},
51215134
})
51225135
} else { None }
51235136
});
@@ -5902,13 +5915,27 @@ where
59025915
match peer_state.channel_by_id.entry(msg.channel_id) {
59035916
hash_map::Entry::Occupied(mut chan) => {
59045917
let res = try_chan_entry!(self, chan.get_mut().update_fulfill_htlc(&msg), chan);
5918+
if let HTLCSource::PreviousHopData(prev_hop) = &res.0 {
5919+
peer_state.actions_blocking_raa_monitor_updates.entry(msg.channel_id)
5920+
.or_insert_with(Vec::new)
5921+
.push(RAAMonitorUpdateBlockingAction::from_prev_hop_data(&prev_hop));
5922+
}
5923+
// Note that we do not need to push an `actions_blocking_raa_monitor_updates`
5924+
// entry here, even though we *do* need to block the next RAA coming in from
5925+
// generating a monitor update which we let fly. We do this instead in the
5926+
// `claim_funds_internal` by attaching a `ReleaseRAAChannelMonitorUpdate`
5927+
// action to the event generated when we "claim" the sent payment. This is
5928+
// guaranteed to all complete before we process the RAA even though there is no
5929+
// lock held through that point as we aren't allowed to see another P2P message
5930+
// from the counterparty until we return, but `claim_funds_internal` runs
5931+
// first.
59055932
funding_txo = chan.get().context.get_funding_txo().expect("We won't accept a fulfill until funded");
59065933
res
59075934
},
59085935
hash_map::Entry::Vacant(_) => return Err(MsgHandleErrInternal::send_err_msg_no_close(format!("Got a message for a channel from the wrong node! No such channel for the passed counterparty_node_id {}", counterparty_node_id), msg.channel_id))
59095936
}
59105937
};
5911-
self.claim_funds_internal(htlc_source, msg.payment_preimage.clone(), Some(forwarded_htlc_value), false, funding_txo);
5938+
self.claim_funds_internal(htlc_source, msg.payment_preimage.clone(), Some(forwarded_htlc_value), false, Some(*counterparty_node_id), funding_txo);
59125939
Ok(())
59135940
}
59145941

@@ -6094,6 +6121,23 @@ where
60946121
})
60956122
}
60966123

6124+
#[cfg(any(test, feature = "_test_utils"))]
6125+
pub(crate) fn test_raa_monitor_updates_held(&self, counterparty_node_id: PublicKey,
6126+
channel_id: [u8; 32])
6127+
-> bool {
6128+
let per_peer_state = self.per_peer_state.read().unwrap();
6129+
if let Some(peer_state_mtx) = per_peer_state.get(&counterparty_node_id) {
6130+
let mut peer_state_lck = peer_state_mtx.lock().unwrap();
6131+
let peer_state = &mut *peer_state_lck;
6132+
6133+
if let Some(chan) = peer_state.channel_by_id.get(&channel_id) {
6134+
return self.raa_monitor_updates_held(&peer_state.actions_blocking_raa_monitor_updates,
6135+
chan.context.get_funding_txo().unwrap(), counterparty_node_id);
6136+
}
6137+
}
6138+
false
6139+
}
6140+
60976141
fn internal_revoke_and_ack(&self, counterparty_node_id: &PublicKey, msg: &msgs::RevokeAndACK) -> Result<(), MsgHandleErrInternal> {
60986142
let (htlcs_to_fail, res) = {
60996143
let per_peer_state = self.per_peer_state.read().unwrap();
@@ -6291,7 +6335,7 @@ where
62916335
MonitorEvent::HTLCEvent(htlc_update) => {
62926336
if let Some(preimage) = htlc_update.payment_preimage {
62936337
log_trace!(self.logger, "Claiming HTLC with preimage {} from our monitor", log_bytes!(preimage.0));
6294-
self.claim_funds_internal(htlc_update.source, preimage, htlc_update.htlc_value_satoshis.map(|v| v * 1000), true, funding_outpoint);
6338+
self.claim_funds_internal(htlc_update.source, preimage, htlc_update.htlc_value_satoshis.map(|v| v * 1000), true, counterparty_node_id, funding_outpoint);
62956339
} else {
62966340
log_trace!(self.logger, "Failing HTLC with hash {} from our monitor", log_bytes!(htlc_update.payment_hash.0));
62976341
let receiver = HTLCDestination::NextHopChannel { node_id: counterparty_node_id, channel_id: funding_outpoint.to_channel_id() };
@@ -9027,6 +9071,7 @@ where
90279071
// downstream chan is closed (because we don't have a
90289072
// channel_id -> peer map entry).
90299073
counterparty_opt.is_none(),
9074+
counterparty_opt.cloned().or(monitor.get_counterparty_node_id()),
90309075
monitor.get_funding_txo().0))
90319076
} else { None }
90329077
} else {
@@ -9296,12 +9341,12 @@ where
92969341
channel_manager.fail_htlc_backwards_internal(&source, &payment_hash, &reason, receiver);
92979342
}
92989343

9299-
for (source, preimage, downstream_value, downstream_closed, downstream_funding) in pending_claims_to_replay {
9344+
for (source, preimage, downstream_value, downstream_closed, downstream_node_id, downstream_funding) in pending_claims_to_replay {
93009345
// We use `downstream_closed` in place of `from_onchain` here just as a guess - we
93019346
// don't remember in the `ChannelMonitor` where we got a preimage from, but if the
93029347
// channel is closed we just assume that it probably came from an on-chain claim.
93039348
channel_manager.claim_funds_internal(source, preimage, Some(downstream_value),
9304-
downstream_closed, downstream_funding);
9349+
downstream_closed, downstream_node_id, downstream_funding);
93059350
}
93069351

93079352
//TODO: Broadcast channel update for closed channels, but only after we've made a

0 commit comments

Comments
 (0)