[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150226110046.4bd919ad@lxorguk.ukuu.org.uk>
Date: Thu, 26 Feb 2015 11:00:46 +0000
From: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: "J. Bruce Fields" <bfields@...ldses.org>,
Jeff Layton <jlayton@...chiereds.net>,
"Kirill A. Shutemov" <kirill@...temov.name>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Christoph Hellwig <hch@....de>,
Dave Chinner <david@...morbit.com>,
Sasha Levin <sasha.levin@...cle.com>
Subject: Re: [GIT PULL] please pull file-locking related changes for v3.20
On Tue, 17 Feb 2015 11:13:39 -0800
Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> On Tue, Feb 17, 2015 at 11:08 AM, J. Bruce Fields <bfields@...ldses.org> wrote:
> >
> > I agree that it's weird, but I think it's what we're stuck with.
>
> And if by "weird" you mean "flock is really not a well-defined or sane
> interface", I'll agree with you.
>
> That said, I'm not at all sure about the "we're stuck with it". We can
> improve the semantics without anybody noticing, because it's not like
> anybody could *depend* on the weaker semantics - they needed
> particular races and timings to hit anyway.
The BSD implementation does not documented such a race, or indeed appear
to have one. That implies that nothing using flock should have this
problem.
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists