fs/9p: add 9P2000.L renameat operation

renameat - change name of file or directory

size[4] Trenameat tag[2] olddirfid[4] oldname[s] newdirfid[4] newname[s]
size[4] Rrenameat tag[2]

older Trename have the below request format

size[4] Trename tag[2] fid[4] newdirfid[4] name[s]

The rename message is used to change the name of a file, possibly moving it
to a new directory. The rename opreation is actually a directory opertation
and should ideally have olddirfid, if not we cannot represent the fid on server
with anything other than name. We will have to derive the old directory name
from fid in the Trename request.

Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>

1 files changed, 6 insertions, 3 deletions

diff --git a/fs/9p/vfs_inode.c b/fs/9p/vfs_inode.c
index 3bbf705634b2..bce66f56c62c 100644
--- a/fs/9p/vfs_inode.c
+++ b/fs/9p/vfs_inode.c
@@ -904,9 +904,12 @@ v9fs_vfs_rename(struct inode *old_dir, struct dentry *old_dentry,
 
         down_write(&v9ses->rename_sem);
         if (v9fs_proto_dotl(v9ses)) {
-                retval = p9_client_rename(oldfid, newdirfid,
-                                        (char *) new_dentry->d_name.name);
-                if (retval != -ENOSYS)
+                retval = p9_client_renameat(olddirfid, old_dentry->d_name.name,
+                                            newdirfid, new_dentry->d_name.name);
+                if (retval == -EOPNOTSUPP)
+                        retval = p9_client_rename(oldfid, newdirfid,
+                                                  new_dentry->d_name.name);
+                if (retval != -EOPNOTSUPP)
                         goto clunk_newdir;
         }
         if (old_dentry->d_parent != new_dentry->d_parent) {