Re: [PATCH v2 7/7] Documentation: Correct s_umount state for freeze_fs/unfreeze_fs
From: Jan Kara <jack@suse.cz>
Date: 2012-01-06 00:36:45
Also in:
linux-ext4, lkml
On Thu 08-12-11 10:04:37, Kamal Mostafa wrote:
From: Valerie Aurora <redacted> freeze_fs/unfreeze_fs ops are called with s_umount held for write, not read.
Looks good. You can add: Acked-by: Jan Kara <jack@suse.cz> Honza
quoted hunk ↗ jump to hunk
BugLink: https://bugs.launchpad.net/bugs/897421 Signed-off-by: Valerie Aurora <redacted> Cc: Kamal Mostafa <redacted> Tested-by: Peter M. Petrakis <redacted> Signed-off-by: Kamal Mostafa <redacted> Reviewed-by: Christoph Hellwig <hch@lst.de> --- Documentation/filesystems/Locking | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)diff --git a/Documentation/filesystems/Locking b/Documentation/filesystems/Locking index d819ba1..7e46a94 100644 --- a/Documentation/filesystems/Locking +++ b/Documentation/filesystems/Locking@@ -134,8 +134,8 @@ evict_inode: put_super: write write_super: read sync_fs: read -freeze_fs: read -unfreeze_fs: read +freeze_fs: write +unfreeze_fs: write statfs: maybe(read) (see below) remount_fs: write umount_begin: no-- 1.7.5.4
-- Jan Kara [off-list ref] SUSE Labs, CR