lkml.org 
[lkml]   [2012]   [Jan]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH v2 7/7] Documentation: Correct s_umount state for freeze_fs/unfreeze_fs
    On Thu 08-12-11 10:04:37, Kamal Mostafa wrote:
    > From: Valerie Aurora <val@vaaconsulting.com>
    >
    > 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
    >
    > BugLink: https://bugs.launchpad.net/bugs/897421
    > Signed-off-by: Valerie Aurora <val@vaaconsulting.com>
    > Cc: Kamal Mostafa <kamal@canonical.com>
    > Tested-by: Peter M. Petrakis <peter.petrakis@canonical.com>
    > Signed-off-by: Kamal Mostafa <kamal@canonical.com>
    > 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 <jack@suse.cz>
    SUSE Labs, CR


    \
     
     \ /
      Last update: 2012-01-06 01:39    [W:4.212 / U:0.524 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site