| To: | Nick Piggin <npiggin@xxxxxxx>, akpm@xxxxxxxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, Chris Mason <chris.mason@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [patch 0/9] writeback data integrity and other fixes (take 3) |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Wed, 29 Oct 2008 05:12:03 -0400 |
| In-reply-to: | <20081029031645.GE4985@disturbed> |
| References: | <20081028144715.683011000@suse.de> <20081028153953.GB3082@wotan.suse.de> <20081028222746.GB4985@disturbed> <20081029001653.GF15599@wotan.suse.de> <20081029031645.GE4985@disturbed> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
On Wed, Oct 29, 2008 at 02:16:45PM +1100, Dave Chinner wrote: > Yeah, that'd do it. Good catch. I can't believe I recently fixed a > bug that touched these lines of code without noticing the inversion. > Sometimes I wonder if we should just conver the entire of XFS to > return negative errors - mistakes in handling negative error numbers > in the core XFS code happen all the time. > > FWIW, the core issue here is that we've got to do the > filemap_fdatawait() call in the ->fsync method because ->fsync > gets called before we've waited for the data I/O to complete. > XFS updates inode state on I/O completion, so we *must* wait > for data I/O to complete before logging the inode changes. I > think btrfs has the same problem.... Yes. I have patches to fix this by changing what ->fsync does and how it's called. I really need to get them out on the list. |
| Previous by Date: | Re: [patch 0/9] writeback data integrity and other fixes (take 3), Dave Chinner |
|---|---|
| Next by Date: | Re: [patch 0/9] writeback data integrity and other fixes (take 3), Christoph Hellwig |
| Previous by Thread: | Re: [patch 0/9] writeback data integrity and other fixes (take 3), Dave Chinner |
| Next by Thread: | Re: [patch 0/9] writeback data integrity and other fixes (take 3), Nick Piggin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |