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

fusefs: only test for incoherency if FN_SIZECHANGE is set #1110

Closed
wants to merge 1 commit into from

Conversation

etsal
Copy link
Contributor

@etsal etsal commented Feb 8, 2024

FUSE emits spurious incoherency warnings in writethrough mode. The warnings are triggered by setattr calls generated by vnode truncation turning the cached va_size vattr stale, causing comparisons with the fresh version provided by the server to fail. Only validate the vnode's va_size vattr if the FN_SIZECHANGE flag is set.

FUSE emits spurious incoherency warnings in writethrough mode. The warnings are triggered by setattr calls generated by vnode truncation turning the cached va_size vattr stale, causing comparisons with the fresh version provided by the server to fail. Only validate the vnode's va_size vattr if the FN_SIZECHANGE flag is set.
@emaste
Copy link
Member

emaste commented Feb 8, 2024

CC @asomers

Copy link
Member

@asomers asomers left a comment

Choose a reason for hiding this comment

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

This LGTM. We were correctly checking that flag in writeback mode, but not in writethrough mode. Thanks for fixing it.

@asomers
Copy link
Member

asomers commented Feb 8, 2024

BTW @etsal this looks like your first ever commit to src. Are you being paid in any way for the work you do on FreeBSD? If so, we should tag your commit message with "Sponsored by: Somebody".

@etsal
Copy link
Contributor Author

etsal commented Feb 9, 2024

I am part of the RCS Lab at the University of Waterloo, so we could add a tag "Contribution made as part of research work at RCSLab, University of Waterloo.", as previously done in 5e29272 for a contribution made by a labmate of mine.

@asomers
Copy link
Member

asomers commented Feb 9, 2024

Ok, I will so tag it.

freebsd-git pushed a commit that referenced this pull request Feb 9, 2024
FUSE emits spurious incoherency warnings in writethrough mode. The
warnings are triggered by setattr calls generated by vnode truncation
turning the cached va_size vattr stale, causing comparisons with the
fresh version provided by the server to fail. Only validate the vnode's
va_size vattr if the FN_SIZECHANGE flag is set.

This is a part of the research work at RCSLab, University of Waterloo.

Reviewed by:	asomers
MFC after:	1 week
Pull Request:	#1110
@asomers
Copy link
Member

asomers commented Feb 9, 2024

Fixed by 8758bf0

@asomers asomers closed this Feb 9, 2024
@emaste emaste added the merged label Feb 9, 2024
5u623l20 pushed a commit to 5u623l20/freebsd-src that referenced this pull request Feb 16, 2024
FUSE emits spurious incoherency warnings in writethrough mode. The
warnings are triggered by setattr calls generated by vnode truncation
turning the cached va_size vattr stale, causing comparisons with the
fresh version provided by the server to fail. Only validate the vnode's
va_size vattr if the FN_SIZECHANGE flag is set.

This is a part of the research work at RCSLab, University of Waterloo.

Reviewed by:	asomers
MFC after:	1 week
Pull Request:	freebsd#1110
freebsd-git pushed a commit that referenced this pull request Apr 21, 2024
FUSE emits spurious incoherency warnings in writethrough mode. The
warnings are triggered by setattr calls generated by vnode truncation
turning the cached va_size vattr stale, causing comparisons with the
fresh version provided by the server to fail. Only validate the vnode's
va_size vattr if the FN_SIZECHANGE flag is set.

This is a part of the research work at RCSLab, University of Waterloo.

Reviewed by:	asomers
Pull Request:	#1110

(cherry picked from commit 8758bf0)
freebsd-git pushed a commit that referenced this pull request Jun 13, 2024
FUSE emits spurious incoherency warnings in writethrough mode. The
warnings are triggered by setattr calls generated by vnode truncation
turning the cached va_size vattr stale, causing comparisons with the
fresh version provided by the server to fail. Only validate the vnode's
va_size vattr if the FN_SIZECHANGE flag is set.

This is a part of the research work at RCSLab, University of Waterloo.

Reviewed by:	asomers
Pull Request:	#1110

(cherry picked from commit 8758bf0)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
3 participants