Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong transaction number in RDB$PAGES relation may cause infinite recusrion in engine and segfault [CORE5762] #6025

Closed
firebird-issue-importer opened this issue Feb 27, 2018 · 5 comments

Comments

@firebird-issue-importer

Submitted by: @AlexPeshkoff

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.

Commits: 3304a6d 2928eec 6e461ec

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Feb 27, 2018

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Feb 27, 2018

Modified by: @AlexPeshkoff

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

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Feb 27, 2018

Modified by: @AlexPeshkoff

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 4.0 Beta 1 [ 10750 ]

Fix Version: 3.0.4 [ 10863 ]

Fix Version: 2.5.9 [ 10862 ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Mar 3, 2018

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Resolved [ 5 ]

QA Status: No test => Cannot be tested

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Mar 3, 2018

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment