[SERVER-16346] Coverity analysis defect 46354: Data race condition Created: 28/Nov/14 Updated: 16/Jan/15 Resolved: 16/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Coverity Collector User | Assignee: | Asya Kamsky |
| Resolution: | Done | Votes: | 0 |
| Labels: | coverity | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Participants: |
| Description |
|
A new defect has been detected and assigned to asya in Coverity Connect. |
| Comments |
| Comment by Keith Bostic [ 28/Nov/14 ] |
|
I can't get to the report's link, I end up at the "Coverity Collect" login page and I can't get past it. That said, I don't think there needs to be any kind of lock around setting/clearing btree->checkpointing in bt_sync.c – Michael, I guess (technically), we're depending on the write happening before the __wt_evict_file_exclusive_XXX functions return, which might need a comment? |