weaveworks / weave

Simple, resilient multi-host containers networking and more.
https://www.weave.works
Apache License 2.0
6.62k stars 671 forks source link

proto: protect field access with proto to avoid possible data race #3986

Open yanke-xu opened 1 year ago

yanke-xu commented 1 year ago

Fixed inconsistency and also potential data race in weave/vendor/github.com/gogo/protobuf/proto/table_unmarshal.go: u.reqFields is read/written 4 times in weave/vendor/github.com/gogo/protobuf/proto/table_unmarshal.go; 3 out of 4 times it is protected by u.lock; 1 out of 4 times it is read without a Lock, which is in func unmarshal() on L260. A data race may happen when unmarshal() and other func computeUnmarshalInfo() are called in parallel.

In order to avoid potential data race here, I use u.lock.RLock(); defer u.lock.RUnlock() to make sure that all usages of items is in critical section.