| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH V2] xfs: truncate_setsize should be outside transactions |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Sat, 3 May 2014 08:16:01 -0700 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20140502232339.GD26353@dastard> |
| References: | <1398983979-23696-1-git-send-email-david@xxxxxxxxxxxxx> <20140502045443.GA8867@xxxxxxxxxxxxx> <20140502050053.GA17578@xxxxxxxxxxxxx> <20140502064700.GB26353@dastard> <20140502070054.GC26353@dastard> <20140502100802.GB14028@xxxxxxxxxxxxx> <20140502232339.GD26353@dastard> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Sat, May 03, 2014 at 09:23:39AM +1000, Dave Chinner wrote: > before we get to the transaction that can fail: > block_truncate_page() zeroes the tail of the page cache page. Hence > if the transaction reservation fails, we've already trashed the file > data - we may as well finish off the job and at least make it look > like the truncate succeeded from a user point of view. They then get > a ENOMEM error (only non-fatal error that can come from > xfs_trans_reserve) and try the truncate again.... I don't think we can even get the ENOMEM. But yeah, I guess we want something like the old version, with comments explaining exactly we we have this order. |
| Previous by Date: | Re: [PATCH] xfs: fix Q_XQUOTARM ioctl, Christoph Hellwig |
|---|---|
| Next by Date: | [PATCH 3/5] xfs: fold xfs_attr_remove_int into xfs_attr_remove, Christoph Hellwig |
| Previous by Thread: | Re: [PATCH V2] xfs: truncate_setsize should be outside transactions, Dave Chinner |
| Next by Thread: | Re: [PATCH V2] xfs: truncate_setsize should be outside transactions, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |