Hi Alexander Viro,
add ->mount function introduction into Documentation/filesystems/vfs.txt
and note that the vfs will replace ->get_sb to ->mount
Signed-off-by: LiuQi <lingjiujianke@xxxxxxxxx>
---
Documentation/filesystems/porting | 24 ++++++++++++++++++++++++
1 files changed, 24 insertions(+), 0 deletions(-)
diff --git a/Documentation/filesystems/porting
b/Documentation/filesystems/porting
index dfbcd1b..9e20eb5 100644
--- a/Documentation/filesystems/porting
+++ b/Documentation/filesystems/porting
@@ -66,6 +66,30 @@ foo_get_sb.
---
[mandatory]
+Newset change of file_system_type method (new mount function ->mount)
+
+*NOTE* linux will replace ->get_sb to ->mount soon.
+the foo_mount function that would return dentry in case of success and negative
+number in case of error (-EINVAL unless you have more informative
error value to
+report). Call it foo_fill_super(). Now declare
+
+struct dentry *foo_mount(struct file_system_type *fs_type,
+ int flags, const char *dev_name, void *data)
+{
+ return mount_bdev(fs_type, flags, dev_name, data, foo_fill_super);
+}
+
+(or similar with s/bdev/nodev/ or s/bdev/single/, depending on the kind of
+filesystem).
+
+Replace DECLARE_FSTYPE... with explicit initializer and have ->mount set as
+foo_mount.
+
+---
+
+
+[mandatory]
+
Locking change: ->s_vfs_rename_sem is taken only by cross-directory renames.
Most likely there is no need to change anything, but if you relied on
global exclusion between renames for some internal purpose - you need to
--
1.7.2
Best Regards
LiuQi
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
