On Tue, Sep 06, 2016 at 08:29:48AM -0700, Christoph Hellwig wrote: > On Thu, Aug 25, 2016 at 04:39:13PM -0700, Darrick J. Wong wrote: > > From: Christoph Hellwig <hch@xxxxxx> > > > > Have xfs_vm_bmap return zero for reflinked files. This hack prevents > > using a file with shared blocks as a swap file, because we don't want > > to deal with CoW when we're (probably) low on memory. > > > > Signed-off-by: Christoph Hellwig <hch@xxxxxx> > > [darrick.wong@xxxxxxxxxx: add a more descriptive changelog] > > Which happens to be incorrect :) The swap code uses ->bmap to build > a logical to physical block map at swapon time (to avoid allocations > or even just block mappings under memory pressure I suspect). This > means we'd get reliable data corruption when COWing a swap file. Yeah, at the time I thought I was going to write out a clever resolution to the conflict between swap and CoW by using swap_activate to punch and fallocate all the shared extents and turn off the inode reflink flag which would then enable me to drop this patch altogether, but then got busy and forgot all about it. Clearly I didn't fix the changelog here either. :( "Have xfs_vm_bmap return zero for reflinked files because the bmap-based swap code requires static block mappings, which is incompatible with copy on write." > > > + * The swap code (ab-)uses ->bmap to get a block mapping and then > > + * bypasse?? the file system for actual I/O. We really can't allow > > Also it seems like I introduced some weird character instead of an > "s" here.. Will fix that while I'm at it. --D _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
