[pfc] Bugfix in reading of last access time for file purging. #612
Conversation
This file contains 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
|
I hope you understand that 4.7.1 has already been released. So, this will have to wait until 4.7.2 or 4.8.0, whichever comes first. |
|
Unfortunately, I know. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Access history in cache meta-data is fixed size now, make sure we do not read beyond the end.
The file purge checking code was reading beyond the end and could lead to random behavior or crashes once the number of times a file was accessed grew beyond the internal size limit (20).
Please merge this also into stable-4.7.x.