[CDRIVER-3381] Unsafe to call mongoc_read_concern_append / mongoc_write_concern_append on the same struct from multiple threads Created: 01/Oct/19 Updated: 10/Feb/23 |
|
| Status: | Backlog |
| Project: | C Driver |
| Component/s: | libmongoc |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Kaitlin Mahar | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | CDRIVER-4575 |
| Description |
|
Conversation with jmikola revealed that mongoc_read_concern_append and mongoc_write_concern_append may be unsafe to call on the same struct concurrently from multiple threads as the "freeze" functions that get called for these types do not use locks. Note this is not a problem for Swift as we don't call these methods at all, and manually encode our read concern / write concern types to bson_ts instead. |