提交 34e5053f 编写于 作者: A Artem Bityutskiy 提交者: Al Viro

Documentation: get rid of write_super

The '->write_super' superblock method is gone, and this patch removes all the
references to 'write_super' from various pieces of the kernel documentation.

Cc: Randy Dunlap <rdunlap@xenotime.net>
Signed-off-by: NArtem Bityutskiy <artem.bityutskiy@linux.intel.com>
Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
上级 f0cd2dbb
...@@ -224,8 +224,8 @@ all your transactions. ...@@ -224,8 +224,8 @@ all your transactions.
</para> </para>
<para> <para>
Then at umount time , in your put_super() (2.4) or write_super() (2.5) Then at umount time , in your put_super() you can then call journal_destroy()
you can then call journal_destroy() to clean up your in-core journal object. to clean up your in-core journal object.
</para> </para>
<para> <para>
......
...@@ -114,7 +114,6 @@ prototypes: ...@@ -114,7 +114,6 @@ prototypes:
int (*drop_inode) (struct inode *); int (*drop_inode) (struct inode *);
void (*evict_inode) (struct inode *); void (*evict_inode) (struct inode *);
void (*put_super) (struct super_block *); void (*put_super) (struct super_block *);
void (*write_super) (struct super_block *);
int (*sync_fs)(struct super_block *sb, int wait); int (*sync_fs)(struct super_block *sb, int wait);
int (*freeze_fs) (struct super_block *); int (*freeze_fs) (struct super_block *);
int (*unfreeze_fs) (struct super_block *); int (*unfreeze_fs) (struct super_block *);
...@@ -136,7 +135,6 @@ write_inode: ...@@ -136,7 +135,6 @@ write_inode:
drop_inode: !!!inode->i_lock!!! drop_inode: !!!inode->i_lock!!!
evict_inode: evict_inode:
put_super: write put_super: write
write_super: read
sync_fs: read sync_fs: read
freeze_fs: write freeze_fs: write
unfreeze_fs: write unfreeze_fs: write
......
...@@ -94,9 +94,8 @@ protected. ...@@ -94,9 +94,8 @@ protected.
--- ---
[mandatory] [mandatory]
BKL is also moved from around sb operations. ->write_super() Is now called BKL is also moved from around sb operations. BKL should have been shifted into
without BKL held. BKL should have been shifted into individual fs sb_op individual fs sb_op functions. If you don't need it, remove it.
functions. If you don't need it, remove it.
--- ---
[informational] [informational]
......
...@@ -216,7 +216,6 @@ struct super_operations { ...@@ -216,7 +216,6 @@ struct super_operations {
void (*drop_inode) (struct inode *); void (*drop_inode) (struct inode *);
void (*delete_inode) (struct inode *); void (*delete_inode) (struct inode *);
void (*put_super) (struct super_block *); void (*put_super) (struct super_block *);
void (*write_super) (struct super_block *);
int (*sync_fs)(struct super_block *sb, int wait); int (*sync_fs)(struct super_block *sb, int wait);
int (*freeze_fs) (struct super_block *); int (*freeze_fs) (struct super_block *);
int (*unfreeze_fs) (struct super_block *); int (*unfreeze_fs) (struct super_block *);
...@@ -273,9 +272,6 @@ or bottom half). ...@@ -273,9 +272,6 @@ or bottom half).
put_super: called when the VFS wishes to free the superblock put_super: called when the VFS wishes to free the superblock
(i.e. unmount). This is called with the superblock lock held (i.e. unmount). This is called with the superblock lock held
write_super: called when the VFS superblock needs to be written to
disc. This method is optional
sync_fs: called when VFS is writing out all dirty data associated with sync_fs: called when VFS is writing out all dirty data associated with
a superblock. The second parameter indicates whether the method a superblock. The second parameter indicates whether the method
should wait until the write out has been completed. Optional. should wait until the write out has been completed. Optional.
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册