Return-Path: linux-nfs-owner@vger.kernel.org Received: from mxout1.mail.janestreet.com ([38.105.200.112]:50809 "EHLO mxout1.mail.janestreet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932472AbbBZOKg (ORCPT ); Thu, 26 Feb 2015 09:10:36 -0500 Received: from tot-qpr-mailcore1.delacy.com ([172.27.56.68] helo=tot-qpr-mailcore1) by mxout1.mail.janestreet.com with smtp (Exim 4.82) (envelope-from ) id 1YQz99-000529-Ky for linux-nfs@vger.kernel.org; Thu, 26 Feb 2015 09:10:35 -0500 Received: from mail-yk0-f179.google.com ([209.85.160.179]) by mxgoog1.mail.janestreet.com with esmtps (UNKNOWN:AES128-GCM-SHA256:128) (Exim 4.72) (envelope-from ) id 1YQz99-0006Uf-G6 for linux-nfs@vger.kernel.org; Thu, 26 Feb 2015 09:10:35 -0500 Received: by ykt10 with SMTP id 10so4132245ykt.1 for ; Thu, 26 Feb 2015 06:10:35 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: From: Chris Perl Date: Thu, 26 Feb 2015 09:10:13 -0500 Message-ID: Subject: Re: File Read Returns Non-existent Null Bytes To: Trond Myklebust Cc: Linux NFS Mailing List , Chris Perl Content-Type: text/plain; charset=UTF-8 Sender: linux-nfs-owner@vger.kernel.org List-ID: > However if you are asking us for an extensive list of "this is what I > can expect if I ignore these rules", then I don't think you will find > much traction. Such a list would be committing us to defining a model > for "non-close-to-open" semantics, which isn't of interest to me at > least, and I doubt anyone else is interested in committing to > maintaining that. One more point on this. I wasn't really asking for a list of what I can expect if I ignore the rules (although I think pointing out that reading corrupt data from the cache is worth mentioning), I was asking what the rules for close-to-open consistency were so I can follow them. I now know one of them is that if a file is open for writing on one client then it can't be read on another. Are there others?