AM> We cannot free disk blocks until I/O against them has completed.
AM> Otherwise the block could be reused for something else, then the
AM> old IO will scribble on the new data.
AM> What we _can_ do is to defer the waiting - only wait on the I/O
AM> when someone reuses the disk blocks. So there are actually
AM> unused blocks with I/O in flight against them.
AM> We do that for metadata (the wait happens in
AM> unmap_underlying_metadata()) but for file data blocks there is no
AM> mechanism in place to look them up
yeah! indeed. my stupid mistake ...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/