SERVER-138619In Code Review

Refactor to harden in-flight OpCtx logic

Coverity issue SERVER-138382, pointed to the logic around managing in-flight OpCtx values as a potential use-after-free case. The analysis turned out to be a false positive and I don't see any risks in the current logic, but the current implementation is fragile and future refactors could break the assumptions currently in place. Here are a few possible strategies: * CancelableOperationContext ** This is seemingly not viable, or any sort of cancellation-token-style approach, as a hard {{mar

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue

No components specified.

Labels
Tags and classification

No labels assigned.