![[BACK]](/icons/back.gif){kind=icon}
Up to [Development] / linux-2.6-xfs / fs / xfs
Up to [Development] / linux-2.6-xfs / fs / xfs
Request diff between arbitrary revisions
Default branch: MAIN
Revision 1.14 / (download) - annotate - [select for diffs], Fri Sep 21 04:08:28 2007 UTC (10 years ago) by lachlan.longdrop.melbourne.sgi.com
Branch: MAIN
CVS Tags: HEAD
Changes since 1.13: +1 -2
lines
Diff to previous 1.13 (colored)
kill unnessecary ioops indirection Currently there is an indirection called ioops in the XFS data I/O path. Various functions are called by functions pointers, but there is no coherence in what this is for, and of course for XFS itself it's entirely unused. This patch removes it instead and significantly reduces source and binary size of XFS while making maintaince easier. Merge of xfs-linux-melb:xfs-kern:29737a by kenmcd. kill unnessecary ioops indirection
Revision 1.13 / (download) - annotate - [select for diffs], Mon Sep 17 16:04:19 2007 UTC (10 years ago) by dgc.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.12: +0 -1
lines
Diff to previous 1.12 (colored)
Kill unused IOMAP_EOF flag Signed-off-by: Christoph Hellwig <hch@lst.de> Merge of xfs-linux-melb:xfs-kern:29705a by kenmcd. kill unused IOMAP_EOF flag
Revision 1.12 / (download) - annotate - [select for diffs], Thu Sep 13 06:11:17 2007 UTC (10 years, 1 month ago) by donaldd.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.11: +0 -1
lines
Diff to previous 1.11 (colored)
kill BMAPI_UNWRITTEN There is no reason to go through xfs_iomap for the BMAPI_UNWRITTEN because it has nothing in common with the other cases. Instead check for the shutdown filesystem in xfs_end_bio_unwritten and perform a direct call to xfs_iomap_write_unwritten (which should be renamed to something more sensible one day) Signed-off-by: Christoph Hellwig <hch@lst.de> Merge of xfs-linux-melb:xfs-kern:29681a by kenmcd. kill BMAPI_UNWRITTEN
Revision 1.11 / (download) - annotate - [select for diffs], Thu Sep 13 06:10:29 2007 UTC (10 years, 1 month ago) by donaldd.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.10: +0 -1
lines
Diff to previous 1.10 (colored)
kill BMAPI_DEVICE There is no reason to go into the iomap machinery just to get the right block device for an inode. Instead look at the realtime flag in the inode and grab the right device from the mount structure. I created a new helper, xfs_find_bdev_for_inode instead of opencoding it because I plan to use it in other places in the future. Signed-off-by: Christoph Hellwig <hch@lst.de> Merge of xfs-linux-melb:xfs-kern:29680a by kenmcd. kill BMAPI_DEVICE
Revision 1.10 / (download) - annotate - [select for diffs], Fri Mar 30 04:04:14 2007 UTC (10 years, 6 months ago) by lachlan.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.9: +1 -0
lines
Diff to previous 1.9 (colored)
Fix to prevent the notorious 'NULL files' problem after a crash. The problem that has been addressed is that of synchronising updates of the file size with writes that extend a file. Without the fix the update of a file's size, as a result of a write beyond eof, is independent of when the cached data is flushed to disk. Often the file size update would be written to the filesystem log before the data is flushed to disk. When a system crashes between these two events and the filesystem log is replayed on mount the file's size will be set but since the contents never made it to disk the file is full of holes. If some of the cached data was flushed to disk then it may just be a section of the file at the end that has holes. There are existing fixes to help alleviate this problem, particularly in the case where a file has been truncated, that force cached data to be flushed to disk when the file is closed. If the system crashes while the file(s) are still open then this flushing will never occur. The fix that we have implemented is to introduce a second file size, called the in-memory file size, that represents the current file size as viewed by the user. The existing file size, called the on-disk file size, is the one that get's written to the filesystem log and we only update it when it is safe to do so. When we write to a file beyond eof we only update the in- memory file size in the write operation. Later when the I/O operation, that flushes the cached data to disk completes, an I/O completion routine will update the on-disk file size. The on-disk file size will be updated to the maximum offset of the I/O or to the value of the in-memory file size if the I/O includes eof. Merge of xfs-linux-melb:xfs-kern:28322a by kenmcd. Fix to prevent the notorious 'NULL files' problem after a crash.
Revision 1.9 / (download) - annotate - [select for diffs], Fri Nov 4 23:20:54 2005 UTC (11 years, 11 months ago) by sandeen
Branch: MAIN
Changes since 1.8: +1 -1
lines
Diff to previous 1.8 (colored)
Fix potential overflow in xfs_iomap_t delta for very large extents Fix potential overflow in xfs_iomap_t delta for very large extents Make iomap_delta 64 bits. Spotted by the folks at katalix.com
Revision 1.8 / (download) - annotate - [select for diffs], Fri Sep 23 03:51:28 2005 UTC (12 years ago) by nathans.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.7: +12 -26
lines
Diff to previous 1.7 (colored)
Update license/copyright notices to match the prefered SGI boilerplate. Merge of xfs-linux-melb:xfs-kern:23903a by kenmcd.
Revision 1.7 / (download) - annotate - [select for diffs], Fri Apr 29 15:10:40 2005 UTC (12 years, 5 months ago) by nathans.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.6: +10 -10
lines
Diff to previous 1.6 (colored)
Cleanup use of loff_t vs xfs_off_t in the core code. Merge of xfs-linux-melb:xfs-kern:22378a by kenmcd.
Revision 1.6 / (download) - annotate - [select for diffs], Fri Apr 29 15:09:58 2005 UTC (12 years, 5 months ago) by nathans.longdrop.melbourne.sgi.com
Branch: MAIN
Changes since 1.5: +2 -5
lines
Diff to previous 1.5 (colored)
Use the right offset when ensuring a delayed allocate conversion has covered the offset originally requested. Can cause data corruption when multiple processes are performing writeout on different areas of the same file. Quite difficult to hit though. Merge of xfs-linux-melb:xfs-kern:22377a by kenmcd.
Revision 1.5 / (download) - annotate - [select for diffs], Thu Aug 5 17:37:52 2004 UTC (13 years, 2 months ago) by arunr
Branch: MAIN
Changes since 1.4: +1 -1
lines
Diff to previous 1.4 (colored)
Correct copyright details. Correct copyright dates.
Revision 1.4 / (download) - annotate - [select for diffs], Tue Aug 3 04:06:25 2004 UTC (13 years, 2 months ago) by nathans
Branch: MAIN
Changes since 1.3: +1 -1
lines
Diff to previous 1.3 (colored)
Fix accidental reverting of sync write preallocations.
Revision 1.3 / (download) - annotate - [select for diffs], Mon Aug 2 17:20:16 2004 UTC (13 years, 2 months ago) by sandeen
Branch: MAIN
Changes since 1.2: +1 -0
lines
Diff to previous 1.2 (colored)
Code checks to trap access to fsb zero. Added IOMAP_REALTIME flag.
Revision 1.2 / (download) - annotate - [select for diffs], Wed Jan 14 06:14:39 2004 UTC (13 years, 9 months ago) by sandeen
Branch: MAIN
Changes since 1.1: +13 -14
lines
Diff to previous 1.1 (colored)
Fix for large allocation groups, so that extent sizes will not overflow pagebuf lengths. Clean up comments on xfs_iomap_t, and make the iomap size a 64-bit number. With AGs > 4G, extents and mappings can be > 32 bits long.
Revision 1.1 / (download) - annotate - [select for diffs], Tue Nov 18 22:07:48 2003 UTC (13 years, 10 months ago) by cattelan
Branch: MAIN
Add new file ... missed in orginal checkin Move iomap definitions to this location. Eventually xfs_iomap.c should move up from linux/xfs_iomap.c so create this file here so it doesn't have to be p_renamed later