Connect to database that contains broken pages can lead to FB crash [CORE6528] #6755
Comments
Modified by: @pavel-zotovAttachment: broken.fdb.7z [ 13571 ] Attachment: dump-when-connect-to-broken-DB.7z [ 13572 ] Attachment: stack-trace-when-connect-to-broken-DB.7z [ 13573 ] |
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
|
Commented by: @AlexPeshkoff Segfault was caused cause engine code absolutely trusted index root page, i.e. offsets pointing out of page were not checked. I've added minimum correctness check when reading such page. May be other pages also require that. |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 4.0.0 [ 10931 ] Fix Version: 3.0.8 [ 10960 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Deferred Test Details: Test implemented but not yet committed to fbt-repo. |
|
::: test details ::: PS. |
Submitted by: @pavel-zotov
Attachments:
broken.fdb.7z
dump-when-connect-to-broken-DB.7z
stack-trace-when-connect-to-broken-DB.7z
Attached .7z files can illustrate the problem:
1) broken.fdb.7z - database which has some pages with arbitrary typed characters (near the beginning of file);
2) stack-trace-when-connect-to-broken-DB.7z and dump-when-connect-to-broken-DB.7z -- stack trace and dump when trying to connect to this DB (checked on LI-V4.0.0.2394)
Commits: f507390 d3ae9f4 98fadc5 81c563d 2573f14 3c99c75
====== Test Details ======
Test implemented but not yet committed to fbt-repo.
To be discussed further, after FB 4.x release.
The text was updated successfully, but these errors were encountered: