rust-lightning/lightning
Wilmer Paulino ed38eac1a3
Release short_to_chan_info lock throughout forwarding_channel_not_found
Not doing so caused a lock order inversion between the locks
`ChannelManager::best_block` and `ChannelManager::short_to_chan_info`
after the addition of `test_trigger_lnd_force_close`.

It turns out that we were holding the `short_to_chan_info` for longer
than needed when processing HTLC forwards. We only need to acquire it to
quickly obtain channel info, and there aren't any other locks within
`forwarding_channel_not_found` that depend on it being held.
2023-10-18 11:25:27 -07:00
..
src Release short_to_chan_info lock throughout forwarding_channel_not_found 2023-10-18 11:25:27 -07:00
Cargo.toml Bump crate versions to 0.0.117/invoice 0.25 2023-10-03 23:00:48 +00:00