On Thu, Aug 29, 2019 at 4:10 PM Jan Kara <jack@xxxxxxx> wrote: > > Hello, > > this is a patch series that addresses a possible race between readahead and > hole punching Amir has discovered [1]. The first patch makes madvise(2) to > handle readahead requests through fadvise infrastructure, the third patch > then adds necessary locking to XFS to protect against the race. Note that > other filesystems need similar protections but e.g. in case of ext4 it isn't > so simple without seriously regressing mixed rw workload performance so > I'm pushing just xfs fix at this moment which is simple. > Jan, Could you give a quick status update about the state of this issue for ext4 and other fs. I remember some solutions were discussed. Perhaps this could be a good topic for a cross track session in LSF/MM? Aren't the challenges posed by this race also relevant for RWF_UNCACHED? Thanks, Amir.