virtiofsd: update FUSE_FORGET comment on "lo_inode.nlookup"
Miklos confirms it's *only* the FUSE_FORGET request that the client can use for decrementing "lo_inode.nlookup". Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com> Cc: Miklos Szeredi <mszeredi@redhat.com> Cc: Stefan Hajnoczi <stefanha@redhat.com> Fixes: 1222f015558fc34cea02aa3a5a92de608c82cec8 Signed-off-by: Laszlo Ersek <lersek@redhat.com> Message-Id: <20201208073936.8629-1-lersek@redhat.com> Reviewed-by: Vivek Goyal <vgoyal@redhat.com> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
This commit is contained in:
parent
31a4990f8d
commit
d6211148f6
@ -101,7 +101,7 @@ struct lo_inode {
|
||||
* This counter keeps the inode alive during the FUSE session.
|
||||
* Incremented when the FUSE inode number is sent in a reply
|
||||
* (FUSE_LOOKUP, FUSE_READDIRPLUS, etc). Decremented when an inode is
|
||||
* released by requests like FUSE_FORGET, FUSE_RMDIR, FUSE_RENAME, etc.
|
||||
* released by a FUSE_FORGET request.
|
||||
*
|
||||
* Note that this value is untrusted because the client can manipulate
|
||||
* it arbitrarily using FUSE_FORGET requests.
|
||||
|
Loading…
x
Reference in New Issue
Block a user