You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How do we plan to tackle the case where two processes:
Access the same file
At least one of them uses mmap()
At least one of them has write permission
Do we consider this case unlikely and thus fail on it? Like, when the second file tries to do an mmap() on the already-opened file (by another process), we return an error?
The text was updated successfully, but these errors were encountered:
This is assuming we emulate mmap by loading the whole file to memory, and saving it on close? (if the map is writable and shared)
I don't have an idea for anything other than (a) pretending to support this, and not updating the map when the file changes, (b) detecting such cases (by way of some common state stored on server) and disallowing them. If we consider this case unlikely, maybe there's no need to even detect it?
I'd prefer to disallow such shared mappings, but: gramineproject/graphene#2147 (review).
But maybe it would work if we allowed such mappings, but enforced that they are not actually shared by anyone.
How do we plan to tackle the case where two processes:
mmap()
Do we consider this case unlikely and thus fail on it? Like, when the second file tries to do an
mmap()
on the already-opened file (by another process), we return an error?The text was updated successfully, but these errors were encountered: