Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753247AbbBQTNl (ORCPT ); Tue, 17 Feb 2015 14:13:41 -0500 Received: from mail-ie0-f171.google.com ([209.85.223.171]:43356 "EHLO mail-ie0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752812AbbBQTNj (ORCPT ); Tue, 17 Feb 2015 14:13:39 -0500 MIME-Version: 1.0 In-Reply-To: <20150217190844.GC27900@fieldses.org> References: <20150209055540.2f2a3689@tlielax.poochiereds.net> <20150216133200.GB3270@node.dhcp.inet.fi> <20150216090054.62455465@tlielax.poochiereds.net> <20150217190844.GC27900@fieldses.org> Date: Tue, 17 Feb 2015 11:13:39 -0800 X-Google-Sender-Auth: OqmCcF7AB41dviaCyfEJWiTMqWU Message-ID: Subject: Re: [GIT PULL] please pull file-locking related changes for v3.20 From: Linus Torvalds To: "J. Bruce Fields" Cc: Jeff Layton , "Kirill A. Shutemov" , linux-fsdevel , Linux Kernel Mailing List , Christoph Hellwig , Dave Chinner , Sasha Levin Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 779 Lines: 18 On Tue, Feb 17, 2015 at 11:08 AM, J. Bruce Fields 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. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/