[issue10867] mmap.flush() issue msync() even if mapping was created with prot=mmap.PROT_READ only

[Марк Коренберг]

Марк Коренберг <socketpair at gmail.com> added the comment:

I have changed title of the bug. This is more precisely describe the problem.

In my code, I do mmap.close(), so msync does not called.

Generally, calling msync() on read-only mapping is not needed at all. And meven more, calling msync() on memory-mapped USB-camera will lead to EIO errno

I think, that flush() should be no-op if mapping is read-only.

----------
title: python mmap objects issue msync() in destructor even if mapping was created with  prot=mmap.PROT_READ only -> mmap.flush() issue msync() even if mapping was created with  prot=mmap.PROT_READ only

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue10867>
_______________________________________