From: Fernando Luis Vazquez Cao Subject: [PATCH] vfs: update documentation to reflect current fsfreeze locking rules Date: Thu, 05 Jul 2012 16:15:42 +0900 Message-ID: <4FF53F1E.6000709@lab.ntt.co.jp> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------060709020206040508000706" Cc: linux-fsdevel@vger.kernel.org, Christoph Hellwig To: Al Viro Return-path: Received: from tama500.ecl.ntt.co.jp ([129.60.39.148]:53104 "EHLO tama500.ecl.ntt.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750834Ab2GEHPx (ORCPT ); Thu, 5 Jul 2012 03:15:53 -0400 Sender: linux-fsdevel-owner@vger.kernel.org List-ID: This is a multi-part message in MIME format. --------------060709020206040508000706 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit --------------060709020206040508000706 Content-Type: text/x-patch; name="vfs-update-documentation-to-reflect-current-fsfreeze-locking-rules.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename*0="vfs-update-documentation-to-reflect-current-fsfreeze-locking"; filename*1="-rules.patch" Subject: vfs: update documentation to reflect current fsfreeze locking rules From: Fernando Luis Vazquez Cao Documentation and implementation got out of sync. Fix it. Signed-off-by: Fernando Luis Vazquez Cao --- diff -urNp linux-3.5-rc5-orig/Documentation/filesystems/Locking linux-3.5-rc5/Documentation/filesystems/Locking --- linux-3.5-rc5-orig/Documentation/filesystems/Locking 2012-07-05 16:02:32.558348964 +0900 +++ linux-3.5-rc5/Documentation/filesystems/Locking 2012-07-05 16:04:40.859998129 +0900 @@ -135,8 +135,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 --------------060709020206040508000706--