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.

Sign up for GitHub

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

Jump to bottom

newInputStream and newOutputStream are not atomic #154

Open
marschall opened this issue Dec 29, 2023 · 0 comments
Open

newInputStream and newOutputStream are not atomic #154

marschall opened this issue Dec 29, 2023 · 0 comments
Assignees
@marschall
Labels
bug

Comments

@marschall
Copy link
Owner

newInputStream and newOutputStream are not atomic:

They first call #getEntry which releases the lock and does not increment the open count. Only after this are the streams created and the open count incremented. This allows for a race where file can be deleted between #getEntry returning and the stream being created.
@marschall marschall added the bug label Dec 29, 2023
@marschall marschall self-assigned this Dec 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@marschall marschall

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@marschall