The method treats pipeline and execPipeline as pairs: if one is set, the other should also be set. However, they are never set atomically. For example, if buildPipeline throws, the pipeline will be set while execPipeline will remain unset. When the transient error callback gets executed here it can end up accessing an uninitialized variable.
- related to
-
SERVER-131603 Fix null pointer dereference in ReshardingTxnCloner when a transient error lands between building the pipeline and execPipeline
-
- Closed
-