From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Fri, 1 Sep 2017 12:43:09 +0200 From: Christoph Hellwig To: Amir Goldstein Cc: Christoph Hellwig , Brian Foster , "Darrick J . Wong" , Dave Chinner , linux-xfs , linux-fsdevel , Josef Bacik , "stable [v4.9]" Subject: Re: [PATCH] xfs: fix incorrect log_flushed on fsync Message-ID: <20170901104309.GA25726@lst.de> References: <1504100302-3297-1-git-send-email-amir73il@gmail.com> <20170831134722.GA6912@lst.de> <20170831163954.GH21939@bfoster.bfoster> <20170901095222.GC24482@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: stable-owner@vger.kernel.org List-ID: On Fri, Sep 01, 2017 at 01:37:28PM +0300, Amir Goldstein wrote: > Well since the bug was demonstrated using crash simulator, > I have no idea how often one would run into this with actual power > failure, but does it really matter how often, if we *know* that it can > happen? No, the issue is real. I wonder how much of an issue the additional flushes are in practice. > I am working on a variant of the flushseq you suggested using > log->l_last_sync_lsn that may be simple enough and not as painful > as turning off optimization for WANT_SYNC log buffer. Ok, I'll take a look once you post it.