[SERVER-85166] Fix edge case in bulkWrite errorsOnly reply processing Created: 12/Jan/24 Updated: 19/Jan/24 Resolved: 19/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sean Zimmerman | Assignee: | Sean Zimmerman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Repl 2024-01-22 | ||||
| Participants: | |||||
| Linked BF Score: | 148 | ||||
| Description |
|
In the existing errors only handling for bulkWrite we missed the case where you have an ordered:false write with errorsOnly:true and you get successful results after the last error message. This led to invalid memory access. To properly handle this we need to make sure that check for potential out of bounds access and avoid it. |
| Comments |
| Comment by Githook User [ 18/Jan/24 ] |
|
Author: {'name': 'seanzimm', 'email': '102551488+seanzimm@users.noreply.github.com', 'username': 'seanzimm'}Message: GitOrigin-RevId: 44abbd3d025fe9e2bb9b0f93ad082ccb8d120ba5 |