Up to [Development] / linux-2.6-xfs / fs / xfs / linux-2.6
Request diff between arbitrary revisions
Default branch: MAIN
Current tag: HEAD
Revision 1.24 / (download) - annotate - [select for diffs], Thu Oct 23 15:01:39 2008 UTC (8 years, 11 months ago) by pleckie.longdrop.melbourne.sgi.com
Branch: MAIN
CVS Tags: HEAD
Changes since 1.23: +18 -57
lines
Diff to previous 1.23 (colored)
avoid all reclaimable inodes in xfs_sync_inodes_ag If we are syncing data in xfs_sync_inodes_ag(), the VFS inode must still be referencable as the dirty data state is carried on the VFS inode. hence if we can't get a reference via igrab(), the inode must be in reclaim which implies that it has no dirty data attached. Leave such inodes to the reclaim code to flush the dirty inode state to disk and so avoid attempting to access the VFS inode when it may not exist in xfs_sync_inodes_ag(). Version 4: o don't reference liinux inode untiil after igrab() succeeds Version 3: o converted unlock/rele to an xfs_iput() call. Version 2: o change igrab logic to be more linear o remove initial reclaimable inode check now that we are using igrab() failure to find reclaimable inodes o assert that igrab failure occurs only on reclaimable inodes o clean up inode locking - only grab the iolock if we are doing a SYNC_DELWRI call and we have a dirty inode. Merge of xfs-linux-melb:xfs-kern:32391a by kenmcd. avoid all reclaimable inodes in xfs_sync_inodes_ag