Segfault when procedure dropped on classic server [CORE5650] #5916
Comments
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Modified by: @AlexPeshkoffdescription: 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. |
Modified by: @AlexPeshkoffstatus: 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 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Cannot be tested |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
firebird-automations
added
affect-version: 4.0 Alpha 1
affect-version: 3.0.2
affect-version: 2.5.7
affect-version: 3.0.1
affect-version: 2.5.6
affect-version: 3.0.0
affect-version: 4.0 Initial
affect-version: 2.5.5
affect-version: 2.5.4
affect-version: 2.5.3 Update 1
affect-version: 2.1.7
affect-version: 2.5.3
affect-version: 2.5.2 Update 1
affect-version: 2.5.2
affect-version: 2.5.1
affect-version: 2.5.0
fix-version: 2.5.8
fix-version: 3.0.3
fix-version: 4.0 Beta 1
resolution: fixed
priority: major
component: engine
type: bug
qa: cannot be tested
labels
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
The text was updated successfully, but these errors were encountered: