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

Segfault when procedure dropped on classic server [CORE5650] #5916

Closed
firebird-issue-importer opened this issue Oct 25, 2017 · 5 comments
Closed

Comments

@firebird-issue-importer

Submitted by: @AlexPeshkoff

An issue was described on IBPhoenix tracker.

When procedure is used in some request it is marked being in use and can will be protected from final removal till request release. But between compiling request and locking resources used by it there is small timeframe when dropping procedure is possible which leads to NULL returned from metadata cache lookup function and in cases when there is no check for procedure pointer to be not NULL may lead to segfault.

This issue is very rarely reproduced cause dangerous timeframe is really small but anyway worth fixing.

Commits: bd0d93a 05e2ddd 0f2c858 8738264 5b37da8

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Oct 25, 2017

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Oct 25, 2017

Modified by: @AlexPeshkoff

description: An issue was described on IBPhoenix tracker.

When procedure is used in some request it is marked being in use and can will be protected from final removal till request release. But between compiling request and locking resources used by it there is small timeframe when dropping procedure is possible which leads to NULL returned from metadata cache lookup function and in cases when there is no check for procedure pointer to be not NULL may lead to segfault.

=>

An issue was described on IBPhoenix tracker.

When procedure is used in some request it is marked being in use and can will be protected from final removal till request release. But between compiling request and locking resources used by it there is small timeframe when dropping procedure is possible which leads to NULL returned from metadata cache lookup function and in cases when there is no check for procedure pointer to be not NULL may lead to segfault.

This issue is very rarely reproduced cause dangerous timeframe is really small but anyway worth fixing.

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Oct 25, 2017

Modified by: @AlexPeshkoff

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

resolution: Fixed [ 1 ]

Fix Version: 2.5.8 [ 10809 ]

Fix Version: 3.0.3 [ 10810 ]

Fix Version: 4.0 Beta 1 [ 10750 ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Oct 31, 2017

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 Oct 31, 2017

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