On Thu 08-12-11 10:04:37, Kamal Mostafa wrote: > From: Valerie Aurora <val@xxxxxxxxxxxxxxxxx> > > 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@xxxxxxx> Honza > > BugLink: https://bugs.launchpad.net/bugs/897421 > Signed-off-by: Valerie Aurora <val@xxxxxxxxxxxxxxxxx> > Cc: Kamal Mostafa <kamal@xxxxxxxxxxxxx> > Tested-by: Peter M. Petrakis <peter.petrakis@xxxxxxxxxxxxx> > Signed-off-by: Kamal Mostafa <kamal@xxxxxxxxxxxxx> > Reviewed-by: Christoph Hellwig <hch@xxxxxx> > --- > 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 <jack@xxxxxxx> SUSE Labs, CR -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
