diff options
| author | MarcoFalke <[email protected]> | 2018-04-27 21:47:27 -0400 |
|---|---|---|
| committer | MarcoFalke <[email protected]> | 2018-04-27 21:47:29 -0400 |
| commit | 3315007e03f5cc6c89a221ec7e0bc09a89858304 (patch) | |
| tree | 2a489e08c129d9054f6d0495bdea20a41118bbd6 /src/httpserver.cpp | |
| parent | Merge #13090: Remove Safe mode (achow101) (diff) | |
| parent | Add compile time checking for all cs_KeyStore runtime locking assertions (diff) | |
| download | discoin-3315007e03f5cc6c89a221ec7e0bc09a89858304.tar.xz discoin-3315007e03f5cc6c89a221ec7e0bc09a89858304.zip | |
Merge #13077: Add compile time checking for all cs_KeyStore runtime locking assertions
66dc662c8a Add compile time checking for all cs_KeyStore runtime locking assertions (practicalswift)
Pull request description:
Add compile time checking for all `cs_KeyStore` runtime locking assertions.
This PR is a subset of #12665. The PR was broken up to make reviewing easier.
The intention is that literally all `EXCLUSIVE_LOCKS_REQUIRED`/`LOCKS_EXCLUDED`:s added in this PR should follow either directly or indirectly from `AssertLockHeld(…)`/`AssertLockNotHeld(…)`:s already existing in the repo.
Consider the case where function `A(…)` contains `AssertLockHeld(cs_foo)` (without
first locking `cs_foo` in `A`), and that `B(…)` calls `A(…)` (without first locking `cs_main`):
* It _directly_ follows that: `A(…)` should have an `EXCLUSIVE_LOCKS_REQUIRED(cs_foo)` annotation.
* It _indirectly_ follows that: `B(…)` should have an `EXCLUSIVE_LOCKS_REQUIRED(cs_foo)` annotation.
Tree-SHA512: 84ee5459e7f75f9affaa4275cb760576ab0e26da8a48b9a4a59b51a25418fe4b862ba832cb01312479a8c9b0e38ee8b6c4076bcbbd73213346d09ec2057fc9f1
Diffstat (limited to 'src/httpserver.cpp')
0 files changed, 0 insertions, 0 deletions