[SERVER-63456] Evaluate WriteBlockBypass in ObObservers Created: 08/Feb/22 Updated: 29/Oct/23 Resolved: 09/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0-rc4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Jackson | Assignee: | Gabriel Marks |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Security 2022-02-21, Security 2022-03-07, Security 2022-03-21 | ||||||||
| Participants: | |||||||||
| Description |
|
When the global critical section is enabled, clients whose WriteBlockBypass is active should be exempt from the critical section. This implies that any OpObserver hooks must be provided with the client's OperationContext, and refuse to fail if the associated WriteBlockBypass is active. |
| Comments |
| Comment by Githook User [ 09/Mar/22 ] |
|
Author: {'name': 'Gabriel Marks', 'email': 'gabriel.marks@mongodb.com', 'username': 'marksg07'}Message: |