[SERVER-29529] Coverity analysis defect 101688: Missing unlock Created: 09/Jun/17 Updated: 27/Oct/23 Resolved: 09/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Coverity Collector User | Assignee: | Keith Bostic (Inactive) |
| Resolution: | Works as Designed | 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 |
|
Missing a release of a lock on a path Defect 101688 (STATIC_C)
File: /src/third_party/wiredtiger/src/btree/bt_split.c
|
| Comments |
| Comment by Keith Bostic (Inactive) [ 09/Jun/17 ] |
Agreed, I don't see a problem here.
Just a locked mutex. |
| Comment by Eric Milkie [ 09/Jun/17 ] |
|
I'm not sure why Coverity thinks this is a problem, as the point of the function is to lock the page. Is a WT "page lock" really just a locked mutex, or is a page lock a variable that is set to a "locked" state? |