Skip to content

Commit c96ab57

Browse files
committed
Make sure individual mutexes are constructed on different lines
Our lockdep logic (on Windows) identifies a mutex based on which line it was constructed on. Thus, if we have two mutexes constructed on the same line it will generate false positives.
1 parent d50db3b commit c96ab57

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

lightning/src/ln/channelmanager.rs

+4-1
Original file line numberDiff line numberDiff line change
@@ -7532,7 +7532,10 @@ where
75327532
}
75337533
}
75347534

7535-
let pending_outbounds = OutboundPayments { pending_outbound_payments: Mutex::new(pending_outbound_payments.unwrap()), retry_lock: Mutex::new(()) };
7535+
let pending_outbounds = OutboundPayments {
7536+
pending_outbound_payments: Mutex::new(pending_outbound_payments.unwrap()),
7537+
retry_lock: Mutex::new(())
7538+
};
75367539
if !forward_htlcs.is_empty() || pending_outbounds.needs_abandon() {
75377540
// If we have pending HTLCs to forward, assume we either dropped a
75387541
// `PendingHTLCsForwardable` or the user received it but never processed it as they

0 commit comments

Comments
 (0)