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.

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

Fix for issue 1864 #1865

Merged
merged 1 commit into from
Dec 15, 2022
Merged

Fix for issue 1864 #1865

merged 1 commit into from
Dec 15, 2022

Conversation

amadio
Copy link
Member

@amadio amadio commented Dec 14, 2022

Fixes #1864.

@amadio amadio self-assigned this Dec 14, 2022
Copy link
Member

@abh3 abh3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, I now understand why my tests succeeded and yours failed. It was a happenstance of the data we used. So, indeed, this is the correct fix as the verification stops when a bad checksum is encountered and the caller needs to redrive the check where it left off. So, yes, data needs to point to where the verification should resume.

@abh3
Copy link
Member

abh3 commented Dec 15, 2022

Let me know whether you will merge this or want me to do it. I think this is the only place it needs to be fixed or do you have another concern?

@amadio
Copy link
Member Author

amadio commented Dec 15, 2022

I usually hold off on merging my own changes until there is a review/approval. I will merge this and include it also in the next release candidate. I don't think a fix is necessary elsewhere.

@amadio amadio merged commit e88666b into xrootd:master Dec 15, 2022
@amadio amadio deleted the issue-1864 branch December 15, 2022 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Server reports all pages with bad checksum when first page of a file is corrupted
2 participants