On Thu, Aug 01, 2013 at 10:54:47AM +1000, Dave Chinner wrote: > > It's not just the range that it's operating on, but also the region > > beyond the range that's been collapsed out. > > Yes, that's part of "the range that it is operating over". > > > A quick eyeball of the patch didn't seem to show any code that handled > > this, which is why I asked the question. > > Right, but really it's the least of the problems I've noticed - the > XFS code is fundamentally broken in many ways - once I've finished > commenting on it, I'll have a quick look to see if the ext4 code has > the same fundamental flaws.... Well, the fundamental flaw of potential races if the file being collapsed has been mmap'ed and there is another process making changes beyond the range that is being collapsed is I suspect one that is going to be very hard to solve, short of not allowing the collapse while there are any read/write mmap's for the file in question. And I would think these sorts of VM issues should be handled with some generic library functions, instead of reimplementing them from scratch in each file system. - Ted _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
