Check if exp_obj exist before accesing the priv - #1799
Merged
Conversation
Now the priv_top is freed when exp_obj is destroyed or deposited, so we need to check properly for exp_obj existence before accessing it. This fixes all the error paths, where the exported object has been aready destroyed, but removing core from the OCF failed, leaving half-deinitialized, so that user can safely retry the failed operation and clean up this broken state. Signed-off-by: Robert Baldyga <robert.baldyga@unvertical.com>
robertbaldyga
force-pushed
the
exp_obj-exist-check
branch
from
September 5, 2026 13:04
e7e9c7d to
c369d3f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Now the priv_top is freed when exp_obj is destroyed or deposited, so we need to check properly for exp_obj existence before accesing it.
This fixes all the error paths, where the exported object has been aready destroyed, but removing core from the OCF failed, leaving half-deinitialized, so that user can safely retry the failed operation and clean up this broken state.