> > you describe the scenarios under which FALLOC_FL_PUNCH_HOLE fails?
> with a parallel pwrite - and it doesn't fail.
> is an inherent, pre-existing, race in the ftrucate/etc APIs.
that have been written too.
like RDMA has also pin those pages. Do we want to abort the invalidate ?
do a memcopy to the page so that we preserve the direct I/O semantics ?
update the direct I/O code to handle GUPed page cache page.