No objections to the code, a text change below: I fix it when applying or you send v4, see the cover letter reply.
On Fri, 13 Nov 2026 14:11:23 +0300, Andrey Zhadchenko wrote: > and a fast path read may then return the data of another guest > offset. A follow-up series fixes this in VSTOR-154659. Item 3 of the cover letter reply: say the limitation is accepted and name VSTOR-154939. Why: VSTOR-154659 is the write counting that is already in the tree, and it is resolved. The read race was filed as VSTOR-154939 and closed as Won't Fix: it needs a read and a discard of the same LBA in flight together, which takes raw access to a disk its owner can read and write anyway, and counting every read would cost the hot read path. No follow-up series will come, so the message must not promise one. -- Konstantin Khorenko, Virtuozzo Linux Kernel Team _______________________________________________ Devel mailing list [email protected] https://lists.openvz.org/mailman/listinfo/devel
