From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay3.corp.sgi.com [198.149.34.15]) by oss.sgi.com (Postfix) with ESMTP id 570CA7F37 for ; Thu, 8 Oct 2015 17:24:55 -0500 (CDT) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by relay3.corp.sgi.com (Postfix) with ESMTP id CFD5AAC007 for ; Thu, 8 Oct 2015 15:24:54 -0700 (PDT) Received: from ipmail06.adl6.internode.on.net (ipmail06.adl6.internode.on.net [150.101.137.145]) by cuda.sgi.com with ESMTP id D4uS7HYy5U0nU1SU for ; Thu, 08 Oct 2015 15:24:52 -0700 (PDT) Date: Fri, 9 Oct 2015 09:24:50 +1100 From: Dave Chinner Subject: Re: [PATCH] xfs: clarify lock ordering comment Message-ID: <20151008222450.GH32150@dastard> References: <1444341481-14139-1-git-send-email-ross.zwisler@linux.intel.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1444341481-14139-1-git-send-email-ross.zwisler@linux.intel.com> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Ross Zwisler Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com On Thu, Oct 08, 2015 at 03:58:01PM -0600, Ross Zwisler wrote: > Replace "i_mmap_lock" with "mmap_lock" in the lock ordering comment above > xfs_filemap_page_mkwrite(). The lock in question is actually the > XFS_MMAPLOCK_SHARED rw_semaphore (no leading "i"), and this comment is struct xfs_inode { .... mrlock_t i_mmaplock; /* inode mmap IO lock */ .... > easily confused with the "i_mmap_lock_[read|write]" functions that operate > on struct address_space->i_mmap_rwsem. This clarification is especially > important because address_space->i_mmap_rwsem is taken down in the DAX > code as part of this fault path. > > Signed-off-by: Ross Zwisler > --- > fs/xfs/xfs_file.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c > index f429662..b190033 100644 > --- a/fs/xfs/xfs_file.c > +++ b/fs/xfs/xfs_file.c > @@ -1477,7 +1477,7 @@ xfs_file_llseek( > * > * mmap_sem (MM) > * sb_start_pagefault(vfs, freeze) > - * i_mmap_lock (XFS - truncate serialisation) > + * mmap_lock (XFS - truncate serialisation) As per above, the XFS lock is "i_mmaplock"... The lock names are annotated with the subsystem the lock belongs to to avoid this confusion. Along with the lock ordering (inside sb_start_pagefault) this should indicate that it's not the "i_mmap_lock (MM - vma serialisation)" lock... ;) Cheers, Dave. -- Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs