[SERVER-35253] `dbHash` can take locks in MODE_S while in a transaction Created: 25/May/18 Updated: 29/Oct/23 Resolved: 29/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage, Testing Infrastructure |
| Affects Version/s: | 4.0.0-rc0 |
| Fix Version/s: | 4.0.0-rc1, 4.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Max Hirschhorn |
| 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 | ||||||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||||||
| Steps To Reproduce: |
|
||||||||||||||||
| Sprint: | TIG 2018-06-04 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||
| Description |
|
However, the dbHash only performs lock conversion if the command specifies an atClusterTime as part of its read concern. Thus a client can now:
The server will crash on the CRUD operation when this invariant fires, noticing the MODE_IX request while the operation context already holds the lock in MODE_S. |
| Comments |
| Comment by Githook User [ 29/May/18 ] |
|
Author: {'username': 'visemet', 'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com'}Message: (cherry picked from commit 52976ef70f1fa991c9b30ba5e0e45fb8e2a1a1d8) |
| Comment by Githook User [ 29/May/18 ] |
|
Author: {'username': 'visemet', 'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com'}Message: |
| Comment by Githook User [ 29/May/18 ] |
|
Author: {'username': 'visemet', 'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com'}Message: |