I wasn't aware of that (and I would definitely prefer a different behaviour).One could remap to /dev/null - the file would then be free to be
But anyway, correct me if I'm wrong, revoke (V2) not simply removes the
pages from the mmaped area as truncating does (the vma stays); revoke
seems to completely remove the vma which is clearly a security bug.
Future mappings may silently get mapped into the area of the revoked
file without the app noticing it. It may then hand out data of the new
file still thinking it's sending the old one.