File handler leakage when making fuse_operations.Create call
YaroslavLitvinov opened this issue · comments
Description
Current implementation of (*inode) NewFile, that is based on newEntry is not handling returned file descriptor that is supposedly fits FUSEOpenOut. In overall that is leading to a file handler leakage inside of gvisor.
In practice when user uses something like open(...,O_CREAT) gvisor fuse makes two calls: create & open. After file is created by create it just eats returned file descriptor and makes open call to acquire another file handle that will be returned to a caller.
Steps to reproduce
No response
runsc version
No response
docker version (if using docker)
No response
uname
No response
kubectl (if using Kubernetes)
No response
repo state (if built from source)
No response
runsc debug logs (if available)
No response
A friendly reminder that this issue had no activity for 120 days.
This issue has been closed due to lack of activity.