From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Whitehouse Subject: Re: [RFC PATCH 01/13] gfs2: Get rid of I_MUTEX_QUOTA usage Date: Thu, 06 Sep 2012 15:27:46 +0100 Message-ID: <1346941666.2728.17.camel@menhir> References: <1346878524-10585-1-git-send-email-bfields@redhat.com> <1346878524-10585-2-git-send-email-bfields@redhat.com> <20120905205920.GA10724@fieldses.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: "J. Bruce Fields" , Al Viro , linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Jan Kara To: "J. Bruce Fields" Return-path: In-Reply-To: <20120905205920.GA10724-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org> Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org Hi, On Wed, 2012-09-05 at 16:59 -0400, J. Bruce Fields wrote: > On Wed, Sep 05, 2012 at 04:55:11PM -0400, J. Bruce Fields wrote: > > From: Jan Kara > > > > GFS2 uses i_mutex on its system quota inode to synchronize writes to > > quota file. Since this is an internal inode to GFS2 (not part of directory > > hiearchy or visible by user) we are safe to define locking rules for it. So > > let's just get it its own locking class to make it clear. > > By the way, Steve, is there any reason you haven't taken this through > the gfs2 tree? > > --b. > I don't remember now, but I've pushed it into my tree for the next merge window, Steve. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html