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

Support forget inode ops #7

Closed
jacobsa opened this issue Mar 24, 2015 · 1 comment
Closed

Support forget inode ops #7

jacobsa opened this issue Mar 24, 2015 · 1 comment

Comments

@jacobsa
Copy link
Owner

jacobsa commented Mar 24, 2015

We define a ForgetInodeOp, but don't currently ever issue it. Start issuing it. Things:

  • Give up on the idea of reference counting within the fuse package and just send the count through to the user. They can naturally track counts in their inode structure.
  • Be very precise in the documentation about what increments the count.
@jacobsa
Copy link
Owner Author

jacobsa commented Mar 30, 2015

Still to do:

  • Write a file system called forgetfs. Same structure as flushfs. It maintains the reference count according to the documentation. It has a public method that panics if any inodes are left with a reference count. It also panics on negative reference count.
  • Write a test that exercises various methods of forgetfs. TearDown unmounts as usual and then calls the check method.

jacobsa added a commit that referenced this issue Mar 30, 2015
jacobsa added a commit that referenced this issue Mar 30, 2015
jacobsa added a commit that referenced this issue Mar 30, 2015
@jacobsa jacobsa closed this as completed Mar 30, 2015
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

No branches or pull requests

1 participant