diff options
author | Andrew Chow <github@achow101.com> | 2023-05-18 11:02:09 -0400 |
---|---|---|
committer | Andrew Chow <github@achow101.com> | 2023-05-18 11:10:05 -0400 |
commit | 6cc136bbd36f859a16e469bb5c016d06c19bcd50 (patch) | |
tree | 8135be589d152bbaae74e0820df52a3454711231 /configure.ac | |
parent | ce2440e6802226ef8f89fa8fa8caf4fe42dfae54 (diff) | |
parent | 69d43905b7f1d4849dfaea1b5744ee473ccc8744 (diff) | |
download | bitcoin-6cc136bbd36f859a16e469bb5c016d06c19bcd50.tar.xz |
Merge bitcoin/bitcoin#27556: wallet: fix deadlock in bdb read write operation
69d43905b7f1d4849dfaea1b5744ee473ccc8744 test: add coverage for wallet read write db deadlock (furszy)
12daf6fcdcbf5c7f03038338d843df3877714b24 walletdb: scope bdb::EraseRecords under a single db txn (furszy)
043fcb0b053eee6021cc75e3d3f41097f52698c0 wallet: bugfix, GetNewCursor() misses to provide batch ptr to BerkeleyCursor (furszy)
Pull request description:
Decoupled from #26644 so it can closed in favor of #26715.
Basically, with bdb, we can't make a write operation while we are traversing the db with the same db handler. These two operations are performed in different txn contexts and cause a deadlock.
Added coverage by using `EraseRecords()` which is the simplest function that executes this process.
To replicate it, need bdb support and drop the first commit. The test will run forever.
ACKs for top commit:
achow101:
ACK 69d43905b7f1d4849dfaea1b5744ee473ccc8744
hebasto:
re-ACK 69d43905b7f1d4849dfaea1b5744ee473ccc8744
Tree-SHA512: b3773be78925f674e962f4a5c54b398a9d0cfe697148c01c3ec0d68281cc5c1444b38165960d219ef3cf1a57c8ce6427f44a876275958d49bbc0808486e19d7d
Diffstat (limited to 'configure.ac')
0 files changed, 0 insertions, 0 deletions