[Top] [All Lists]

Re: [PATCH 0/5] xfs: more patches for 3.13

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: [PATCH 0/5] xfs: more patches for 3.13
From: Ben Myers <bpm@xxxxxxx>
Date: Wed, 6 Nov 2013 17:01:33 -0600
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <1383280040-21979-1-git-send-email-david@xxxxxxxxxxxxx>
References: <1383280040-21979-1-git-send-email-david@xxxxxxxxxxxxx>
User-agent: Mutt/1.5.20 (2009-06-14)
On Fri, Nov 01, 2013 at 03:27:15PM +1100, Dave Chinner wrote:
> Hi folks,
> The following series follows up the recently committed series of
> patches for 3.13. The first two patches are the remaining
> uncommitted patches from the previous series.
> The next two patches are tracing patches, one for AIL manipulations
> and the other for AGF and AGI read operations. Both of these were
> written during recent debugging sessions, and both proved useful so
> should be added to the menagerie of tracepoints we already have
> avaialble.
> The final patch is the increasing of the inode cluster size for v5
> filesystems. I'd like to get this into v5 filesystems for 3.13 so we
> get wider exposure of it ASAP so we have more data available to be
> able to make informed decisions about how to bring this back to v4
> filesystems in a safe and controlled manner.

Applied 3 and 4.  I still don't understand why the locking on patch 2 is
correct.  Seems like the readers of i_version hold different locks than we do
when we log the inode.  Maybe Christoph can help me with that.


<Prev in Thread] Current Thread [Next in Thread>