Documentation: Correct s_umount state for freeze_fs/unfreeze_fs
freeze_fs/unfreeze_fs ops are called with s_umount held for write, not read. Signed-off-by: Valerie Aurora <val@vaaconsulting.com> Signed-off-by: Kamal Mostafa <kamal@canonical.com> Reviewed-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Jan Kara <jack@suse.cz> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
This commit is contained in:
parent
d9c95bdd53
commit
06fd516c1a
1 changed files with 2 additions and 2 deletions
|
@ -138,8 +138,8 @@ evict_inode:
|
||||||
put_super: write
|
put_super: write
|
||||||
write_super: read
|
write_super: read
|
||||||
sync_fs: read
|
sync_fs: read
|
||||||
freeze_fs: read
|
freeze_fs: write
|
||||||
unfreeze_fs: read
|
unfreeze_fs: write
|
||||||
statfs: maybe(read) (see below)
|
statfs: maybe(read) (see below)
|
||||||
remount_fs: write
|
remount_fs: write
|
||||||
umount_begin: no
|
umount_begin: no
|
||||||
|
|
Loading…
Add table
Reference in a new issue