Skip to contentSkip to conversation

XFS development tree branch, xfs-renameat-extensions, created. v3.19-rc1-2-gd31a182

XFS updates [email protected] 1 participant 1 message Dec 24, 2014

lore
Share & tools
lore

[email protected]

author Reviewed-by Brian Foster Reviewed-by Dave Chinner Reviewed-by Brian Foster
#0 lore raw

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "XFS development tree".

The branch, xfs-renameat-extensions has been created

        at  d31a1825450062b85282b4afed1c840fd306d012 (commit)

- Log ----------------------------------------------------------------- commit d31a1825450062b85282b4afed1c840fd306d012

Author: Carlos Maiolino <[email protected]>
Date:   Wed Dec 24 08:51:42 2014 +1100

xfs: Add support to RENAME_EXCHANGE flag

Adds a new function named xfs_cross_rename(), responsible for handling requests from sys_renameat2() using RENAME_EXCHANGE flag.

commit dbe1b5ca26396b6c61d711c8ac4de13ebb02e9f6

Author: Carlos Maiolino <[email protected]>
Date:   Wed Dec 24 08:51:38 2014 +1100

xfs: Make xfs_vn_rename compliant with renameat2() syscall

To be able to support RENAME_EXCHANGE flag from renameat2() system call, XFS must have its inode_operations updated, exporting .rename2 method, instead of .rename.

This patch just replaces the (now old) .rename method by .rename2, using the same infra-structure, but checking rename flags. Calls to .rename2 using RENAME_EXCHANGE flag, although now handled inside XFS, still return -EINVAL.

RENAME_NOREPLACE is handled via VFS and we don't need to care about it inside xfs_vn_rename.

-----------------------------------------------------------------------

hooks/post-receive

Signature · 6 lines
XFS development tree

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs