summaryrefslogtreecommitdiffhomepage
path: root/pkg/waiter/waiter.go
diff options
context:
space:
mode:
authorMichael Pratt <mpratt@google.com>2019-06-21 12:25:24 -0700
committergVisor bot <gvisor-bot@google.com>2019-06-21 12:26:42 -0700
commitc0317b28cb3f8346ee81564ee477aafdf6283f45 (patch)
treebb91240172a173aba9ed799deab7026d8e197ee1 /pkg/waiter/waiter.go
parentf94653b3dea629f365ce5742b99bbcaa7673ded2 (diff)
Update pathNode documentation to reflect reality
Neither fidRefs or children are (directly) synchronized by mu. Remove the preconditions that say so. That said, the surrounding does enforce some synchronization guarantees (e.g., fidRef.renameChildTo does not atomically replace the child in the maps). I've tried to note the need for callers to do this synchronization. I've also renamed the maps to what are (IMO) clearer names. As is, it is not obvious that pathNode.fidRefs is a map of *child* fidRefs rather than self fidRefs. PiperOrigin-RevId: 254446965
Diffstat (limited to 'pkg/waiter/waiter.go')
0 files changed, 0 insertions, 0 deletions