| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | [PATCH 0/2] xfs: extent swap fixes |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Thu, 31 Jul 2014 16:12:06 +1000 |
| Delivered-to: | xfs@xxxxxxxxxxx |
Hi folks, The extent swap code is not symmetrical, so correct behaviour is dependent on userspace doing the right thing. If we try to swap extents with the temporary inode in the wrong state we can have interesting failures. These two patches fix those issues and treat the two files identically in terms of the state of the data contained in the files being swapped. Failure to write or remove all cached data from either file will now cause the swap extents operation to fail. Comments, thoughts? Cheers, Dave. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH 2/2] xfs: flush both inodes in xfs_swap_extents, Dave Chinner |
|---|---|
| Next by Date: | [PATCH 3/6] xfs: kill VN_DIRTY(), Dave Chinner |
| Previous by Thread: | [PATCH 0/4 V2] xfs: missing verifier fixes, Dave Chinner |
| Next by Thread: | [PATCH 1/2] xfs: fix swapext ilock deadlock, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |