Skip to content

Commit 0d43f16

Browse files
f - Clarify lock order tree docs
1 parent 5d5a813 commit 0d43f16

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

lightning/src/ln/channelmanager.rs

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -670,8 +670,10 @@ pub type SimpleRefChannelManager<'a, 'b, 'c, 'd, 'e, M, T, F, L> = ChannelManage
670670
//
671671
// Lock order:
672672
// The tree structure below illustrates the lock order requirements for the different locks of the
673-
// `ChannelManager`. If two or more locks on the same branch are held at the same time, locks
674-
// should be taken in the order of the lowest to the highest level in the tree.
673+
// `ChannelManager`. Locks can be held at the same time if they are on the same branch in the tree,
674+
// and should then be taken in the order of the lowest to the highest level in the tree.
675+
// Note that locks on different branches shall not be taken at the same time, as doing so will
676+
// create a new lock order for those specific locks in the order they were taken.
675677
//
676678
// Lock order tree:
677679
//

0 commit comments

Comments
 (0)