Repository navigation
[python] Back-reference keeping the handler alive in stream for pyjindo impl #10536
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[P2] Close the stream before releasing the owner instead of relying on attribute order
The keep-alive works only because
_streamis assigned before_owner. When an unclosedJindoInputFileis released, its__dict__drops_streamfirst, soFileStream.__dealloc__->close()still runs against a live store. Nothing makes that order explicit. With the same local reproduction, assigningself._owner = ownerbeforeself._stream = jindo_streambrings the SIGSEGV back on this head when the evicted handler's last unclosed file is released. Closing the file before releasing it, or adding a__del__that closes_streamwhile_owneris still set, passes with the reversed order. pyjindo's ownJindoOssFileis safe for the same reason:io.IOBasecloses it in its finalizer beforefsis released, and the PVFS path passes the same eviction reproduction.close()also keeps_owner, so a closed file that is still referenced pins the evicted handler and its native store longer than the stream is open. Releasing the owner after a successful close is safe: in the same reproduction, a closed file whose owner is released before its stream passes.Please close
_streamexplicitly before_ownercan be released and drop_owneronce the close succeeds (the same applies toJindoOutputFile), and consider makingownerrequired so a newopen_*path cannot silently skip it. Please also add a regression test: the existing mock-based tests can patchjfs.connect, drop thePyFileSystemwhile a file is open, and assert that the stream is closed before the fake filesystem is destroyed.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done