vfs: Rename end_writeback() to clear_inode()
After we moved inode_sync_wait() from end_writeback() it doesn't make sense to call the function end_writeback() anymore. Rename it to clear_inode() which well says what the function really does - set I_CLEAR flag. Signed-off-by: Jan Kara <jack@suse.cz> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
This commit is contained in:
parent
7994e6f725
commit
dbd5768f87
52 changed files with 68 additions and 70 deletions
|
|
@ -1744,8 +1744,8 @@ struct super_operations {
|
|||
* I_FREEING Set when inode is about to be freed but still has dirty
|
||||
* pages or buffers attached or the inode itself is still
|
||||
* dirty.
|
||||
* I_CLEAR Added by end_writeback(). In this state the inode is clean
|
||||
* and can be destroyed. Inode keeps I_FREEING.
|
||||
* I_CLEAR Added by clear_inode(). In this state the inode is
|
||||
* clean and can be destroyed. Inode keeps I_FREEING.
|
||||
*
|
||||
* Inodes that are I_WILL_FREE, I_FREEING or I_CLEAR are
|
||||
* prohibited for many purposes. iget() must wait for
|
||||
|
|
@ -2328,7 +2328,7 @@ extern unsigned int get_next_ino(void);
|
|||
|
||||
extern void __iget(struct inode * inode);
|
||||
extern void iget_failed(struct inode *);
|
||||
extern void end_writeback(struct inode *);
|
||||
extern void clear_inode(struct inode *);
|
||||
extern void __destroy_inode(struct inode *);
|
||||
extern struct inode *new_inode_pseudo(struct super_block *sb);
|
||||
extern struct inode *new_inode(struct super_block *sb);
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue