Guillaume Yziquel 3fc5ed8067 Issue 122262: MAP_PRIVATE for more reliability on virtualised filesystems. ... Adding support of quirky filesystems occuring in virtualised settings not having full POSIX support for memory mapped files. Example: current virtiofs with cache disabled, occuring in Incus/LXD or Kata Containers. Has been hitting various virtualised filesystems since 2016, depending on their levels of maturity at the time. The situation will perhaps improve when virtiofs DAX support patches will have made it into the qemu mainline. On a reliability level, using the MAP_PRIVATE sycall flag instead of the MAP_SHARED syscall flag for the mmap() system call does have some undefined behaviour when the caller update the memory mapping of the mmap()ed file, but MAP_SHARED does allow not only the calling process but other processes to modify the memory mapping. Thus, in the current context, using MAP_PRIVATE copy-on-write is marginally more reliable than MAP_SHARED. This discussion of reliability is orthogonal to the type system enforced safety policy of rust, which does not claim to handle memory modification of memory mapped files triggered through the operating system and not the running rust process.		2024-03-15 18:31:07 -04:00
..
src	Issue 122262: MAP_PRIVATE for more reliability on virtualised filesystems.	2024-03-15 18:31:07 -04:00
Cargo.toml	windows bump to 0.52	2024-02-18 16:02:16 +03:00