Skip to content

Taking read only Inode lock while reading via file-handle #3454

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

Open
wants to merge 2 commits into
base: masterwithgoproc
Choose a base branch
from

Conversation

raj-prince
Copy link
Collaborator

@raj-prince raj-prince commented Jun 26, 2025

Description

  • Taking inode.RLock() while reading via file-handle
  • Permanently disabling the content cache path, which is unused and seems not required in the future. Keeping this will make lock/unlock implementation dirty.

Before:
image

After:
image

Link to the issue in case of a bug fix.

b/427609583

Testing details

  1. Manual - Tested.
  2. Unit tests - NA
  3. Integration tests - NA

Any backward incompatible change? If so, please explain.

@raj-prince raj-prince changed the title Taking Inode RLock while reading via file-handle Taking read only Inode lock while reading via file-handle Jun 26, 2025
@raj-prince raj-prince marked this pull request as ready for review June 26, 2025 14:16
@raj-prince raj-prince requested a review from a team as a code owner June 26, 2025 14:16
@raj-prince raj-prince requested review from vadlakondaswetha and removed request for a team June 26, 2025 14:16
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.

1 participant