From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 5 Sep 2018 09:53:36 -0400 From: "J. Bruce Fields" To: Jeff Layton Cc: =?utf-8?B?54Sm5pmT5Yas?= , R.E.Wolff@bitwizard.nl, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: POSIX violation by writeback error Message-ID: <20180905135336.GB22395@fieldses.org> References: <82ffc434137c2ca47a8edefbe7007f5cbecd1cca.camel@redhat.com> <20180904161203.GD17478@fieldses.org> <20180904162348.GN17123@BitWizard.nl> <20180904185411.GA22166@fieldses.org> <09ba078797a1327713e5c2d3111641246451c06e.camel@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <09ba078797a1327713e5c2d3111641246451c06e.camel@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: On Wed, Sep 05, 2018 at 06:55:15AM -0400, Jeff Layton wrote: > There is no requirement for a filesystem to flush data on close(). In > fact, most local filesystems do not. NFS does, but that's because it has > to in order to provide close-to-open cache consistency semantics. And these days even NFS can delay writeback till after close thanks to write delegations. --b.