Issue Details (XML | Word | Printable)

Key: CORE-5762
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Alexander Peshkov
Reporter: Alexander Peshkov
Votes: 0
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
Firebird Core

Wrong transaction number in RDB$PAGES relation may cause infinite recusrion in engine and segfault

Created: 27/Feb/18 12:13 PM   Updated: 03/Mar/18 08:38 AM
Component/s: None
Affects Version/s: 2.5.0, 2.5.1, 2.5.2, 2.5.2 Update 1, 2.5.3, 2.1.7, 2.5.3 Update 1, 2.5.4, 2.5.5, 4.0 Initial, 3.0.0, 2.5.6, 3.0.1, 2.5.7, 3.0.2, 4.0 Alpha 1, 2.5.8, 3.0.3
Fix Version/s: 3.0.4, 4.0 Beta 1, 2.5.9

QA Status: Cannot be tested


 Description  « Hide
Normally only system (i.e. zero) transaction updates RDB$PAGES relation. But due to:
- update by SYSDBA user (FB <3 only),
- database decryption error,
- generic data corruption
wrong transaction number can be read by engine for this table. Certainly all cases are more or less abnormal but segfault is not good diagnostic for it.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Alexander Peshkov made changes - 27/Feb/18 12:13 PM
Field Original Value New Value
Assignee Alexander Peshkov [ alexpeshkoff ]
Alexander Peshkov made changes - 27/Feb/18 12:17 PM
Summary Wrong transaction number in RDB$PAGES relation cause infinite recusrion in engine and segfault Wrong transaction number in RDB$PAGES relation may cause infinite recusrion in engine and segfault
Alexander Peshkov made changes - 27/Feb/18 12:28 PM
Status Open [ 1 ] Resolved [ 5 ]
Fix Version/s 4.0 Beta 1 [ 10750 ]
Fix Version/s 3.0.4 [ 10863 ]
Fix Version/s 2.5.9 [ 10862 ]
Resolution Fixed [ 1 ]
Pavel Zotov made changes - 03/Mar/18 08:38 AM
Status Resolved [ 5 ] Resolved [ 5 ]
QA Status No test Cannot be tested
Pavel Zotov made changes - 03/Mar/18 08:38 AM
Status Resolved [ 5 ] Closed [ 6 ]