We need to adapt our OFD locks in case of a disk resize command. This has been spotted by @phip1611.

Here is the relevant discussion

One last question: Since we have #7494: How does this work together with disk locking using byte-ranges? The old range will remain locked but that will not correspond to the new size.

From a Cloud Hypervisor perspective, as the locks are just advisory and overlapping, we can keep the old lock as it will in any case prevent further Cloud Hypervisor instances from locking again. But technically, other software could see regions of the file being unlocked.

Originally posted by @phip1611 in #7476 (comment)