[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140813120907.33c5584a@canb.auug.org.au>
Date: Wed, 13 Aug 2014 12:09:07 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Jeff Layton <jeff.layton@...marydata.com>
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-nfs@...r.kernel.org
Subject: Re: [PATCH 0/5] locks: move most locks_release_private calls
outside of i_lock
Hi Jeff,
On Tue, 12 Aug 2014 19:47:36 -0400 Jeff Layton <jeff.layton@...marydata.com> wrote:
>
> On Wed, 13 Aug 2014 08:28:27 +1000
> Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> > On Tue, 12 Aug 2014 10:48:08 -0400 Jeff Layton <jlayton@...marydata.com> wrote:
> > >
> > > Absent any objections, I'll plan to merge these for 3.18.
> >
> > This means that this patch set should *not* be in linux-next until after
> > (at least) v3.17-rc1 is released ... This s reinforced by the lack of
> > Acked-by, Reviewed-by and Tested-by tags ... (the addition of which would
> > presumably require the rebase (or rewrite) of a published git tree.)
>
> It would, but I sent a later reply that revised that statement.
>
> Trond pointed out that this problem can cause a user-triggerable oops,
> so we may have to merge it for 3.17 after all. With that in mind, I
> added these to my linux-next branch and will probably send a pull
> request before the window closes (assuming that there are no glaring
> problems with it).
OK, fine. I have merged it today in any case.
> While we're on the subject, we probably ought to rename my tree in your
> "Trees" file from "file-private-locks" to "file-locks" or something.
> File private locks (aka OFD locks) got merged in v3.15, but I have been
> collecting patches that touch fs/locks.c
OK, I will do that tomorrow.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists