Races in cache of opened security databases [CORE6450] #6683
Assignees
Comments
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Modified by: @AlexPeshkoffreporter: Alexander Peshkov [ alexpeshkoff ] => Pavel Zotov [ tabloid ] |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 4.0 RC 1 [ 10930 ] Fix Version: 3.0.8 [ 10960 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Cannot be tested Test Details: Test can not be implemented because of negligible probability to reproduce this error. |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: @pavel-zotov
When new sec db is added to cache there is small timeframe when empty covering, already added to the list of known DBs, is not locked. An attempt to use it caused segfault when running tests on FB4 but same may happen for 3.0.6 & 3.0.7.
Commits: fb99f96 8b70d33 8f49cd7 41a8fc5
====== Test Details ======
Test can not be implemented because of negligible probability to reproduce this error.
Bug appeared first time at nov-2020 during regular OLTP-EMUL runs on Linux, but source code had it since jan-2020 (letter from Alex, 19.11.2020 11:10).
The text was updated successfully, but these errors were encountered: