| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 3/6] xfs: xfs_vm_write_end truncates too much on failure |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Mon, 14 Apr 2014 18:13:07 +1000 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20140410103555.GF17641@xxxxxxxxxxxxx> |
| References: | <1397106053-7489-1-git-send-email-david@xxxxxxxxxxxxx> <1397106053-7489-4-git-send-email-david@xxxxxxxxxxxxx> <20140410103555.GF17641@xxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Thu, Apr 10, 2014 at 03:35:55AM -0700, Christoph Hellwig wrote: > On Thu, Apr 10, 2014 at 03:00:50PM +1000, Dave Chinner wrote: > > From: Dave Chinner <dchinner@xxxxxxxxxx> > > > > Similar to the write_begin problem, xfs-vm_write_end will truncate > > back to the old EOF, potentially removing page cache from over the > > top of delalloc blocks with valid data in them. Fix this by > > truncating back to just the start of the failed write. > > > > Signed-off-by: Dave Chinner <dchinner@xxxxxxxxxx> > > Looks good, > > Reviewed-by: Christoph Hellwig <hch@xxxxxx> > > Any reason you used max_t in the previous one, and opencode it here? No, just made the changes at different times. I'll fix them both to use max_t.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| Previous by Date: | [XFS updates] XFS development tree branch, for-next, updated. xfs-for-linus-3.15-rc1-14826-gc9eaa44, xfs |
|---|---|
| Next by Date: | Re: [PATCH] xfs: unmount does not wait for shutdown during unmount, Dave Chinner |
| Previous by Thread: | Re: [PATCH 3/6] xfs: xfs_vm_write_end truncates too much on failure, Christoph Hellwig |
| Next by Thread: | Re: [PATCH 0/6 v2] xfs: delalloc, dio and corruption..., Brian Foster |
| Indexes: | [Date] [Thread] [Top] [All Lists] |