Re: [Nfs-ganesha-devel] open2 implementations

> Ye, FSAL_GPFS could use openat but I want to have control over all the calls > in GPFS before it calls the VFS. Do you see any problem with the code? > Thanks, Marc. No looks good. I was just auditing the use of obj_hdl->obj_ops within an FSAL. These operations are un-cached because the

Re: [Nfs-ganesha-devel] open2 implementations

Ye, FSAL_GPFS could use openat but I want to have control over all the calls in GPFS before it calls the VFS. Do you see any problem with the code? Thanks, Marc. From: "Frank Filz" To: "'nfs-ganesha-devel'" , Marc

Re: [Nfs-ganesha-devel] open2 implementations

age- > From: Frank Filz [mailto:ffilz...@mindspring.com] > Sent: Monday, September 12, 2016 11:42 AM > To: 'nfs-ganesha-devel' <nfs-ganesha-devel@lists.sourceforge.net>; 'Marc > Eshel' <es...@us.ibm.com> > Subject: [Nfs-ganesha-devel] open2 implementations > > M

[Nfs-ganesha-devel] open2 implementations

Marc especially... I see several open2 implementations seem to be doing a lookup and then an open2 by handle. FSAL_CEPH needed to do this because it doesn't have openat to open a file given a directory handle and a filename within that directory. FSAL_ VFS can do openat, so it doesn't need to