We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
pjdfstest covers a ton of control-path functionality, but there's some stuff that it doesn't touch. This is a metabug to track its gaps. * [ ] file handle access with fhopen(2) etc. Used by userspace NFS servers. * [ ] POSIX.1e ACLs * [ ] NFSv4 ACLs * [ ] Advisory locking with flock(2) or fcntl(2) * [ ] Extended attributes ([enhancement request: extended attributes #52](https://github.com/pjd/pjdfstest/issues/52)) * [ ] Any kind of datapath access (lseek, read, write, mmap, copy_file_range, and hole-punching) * [ ] Tricky readdir corner cases. telldir/seekdir, etc.
pjdfstest covers a ton of control-path functionality, but there's some stuff that it doesn't touch. This is a metabug to track its gaps.
* [ ] file handle access with fhopen(2) etc. Used by userspace NFS servers. * [ ] POSIX.1e ACLs * [ ] NFSv4 ACLs * [ ] Advisory locking with flock(2) or fcntl(2) * [ ] Extended attributes ([enhancement request: extended attributes #52](https://github.com/pjd/pjdfstest/issues/52)) * [ ] Any kind of datapath access (lseek, read, write, mmap, copy_file_range, and hole-punching) * [ ] Tricky readdir corner cases. telldir/seekdir, etc.
pjd#60 (comment)
The text was updated successfully, but these errors were encountered:
To be clear, this is beyond the scope of GSoC.
Sorry, something went wrong.
Yes, that's why I haven't set a milestone for this issue.
No branches or pull requests
pjd#60 (comment)
The text was updated successfully, but these errors were encountered: