Copyright © tutorialspoint.com
The prot argument describes the desired memory protection (and must not conflict with the open mode of the file). It is either PROT_NONE or is the bitwise OR of one or more of the other PROT_* flags.
|PROT_EXEC||Pages may be executed.|
|PROT_READ||Pages may be read.|
|PROT_WRITE||Pages may be written.|
|PROT_NONE||Pages may not be accessed.|
|MAP_FIXED||Do not select a different address than the one specified. If the memory region specified by start and len overlaps pages of any existing mapping(s), then the overlapped part of the existing mapping(s) will be discarded. If the specified address cannot be used, mmap() will fail. If MAP_FIXED is specified, start must be a multiple of the page size. Use of this option is discouraged.|
|MAP_SHARED||Share this mapping with all other processes that map this object. Storing to the region is equivalent to writing to the file. The file may not actually be updated until msync(2) or munmap(2) are called.|
|MAP_PRIVATE||Create a private copy-on-write mapping. Stores to the region do not affect the original file. It is unspecified whether changes made to the file after the mmap() call are visible in the mapped region.|
The above three flags are described in POSIX.1-2001. Linux also knows about the following non-standard flags:
|This flag is ignored. (Long ago, it signalled that attempts to write to the underlying file should fail with ETXTBUSY. But this was a source of denial-of-service attacks.)|
|This flag is ignored.|
|Do not reserve swap space for this mapping. When swap space is reserved, one has the guarantee that it is possible to modify the mapping. When swap space is not reserved one might get SIGSEGV upon a write if no physical memory is available. See also the discussion of the file /proc/sys/vm/overcommit_memory in proc(5). In kernels before 2.6, this flag only had effect for private writable mappings.|
|MAP_LOCKED (since Linux 2.5.37)|
|Lock the pages of the mapped region into memory in the manner of mlock(). This flag is ignored in older kernels.|
|Used for stacks. Indicates to the kernel VM system that the mapping should extend downwards in memory.|
|The mapping is not backed by any file; the fd and offset arguments are ignored. The use of this flag in conjunction with MAP_SHARED is only supported on Linux since kernel 2.4.|
|Alias for MAP_ANONYMOUS. Deprecated.|
|Compatibility flag. Ignored.|
|Put the mapping into the first 2GB of the process address space. Ignored when MAP_FIXED is set. This flag is currently only supported on x86-64 for 64bit programs.|
|MAP_POPULATE (since Linux 2.5.46)|
|Populate (prefault) page tables for a file mapping, by performing read-ahead on the file. Later accesses to the mapping will not be bocked by page faults.|
|MAP_NONBLOCK (since Linux 2.5.46)|
|Only meaningful in conjunction with MAP_POPULATE. Dont perform read-ahead: only create page tables entries for pages that are already present in RAM.|
fd should be a valid file descriptor, unless MAP_ANONYMOUS is set. If MAP_ANONYMOUS is set, then fd is ignored on Linux. However, some implementations require fd to be -1 if MAP_ANONYMOUS (or MAP_ANON) is specified, and portable applications should ensure this.
offset should be a multiple of the page size as returned by getpagesize(2).
Memory mapped by mmap() is preserved across fork(2), with the same attributes.
A file is mapped in multiples of the page size. For a file that is not a multiple of the page size, the remaining memory is zeroed when mapped, and writes to that region are not written out to the file. The effect of changing the size of the underlying file of a mapping on the pages that correspond to added or removed regions of the file is unspecified.
The munmap() system call deletes the mappings for the specified address range, and causes further references to addresses within the range to generate invalid memory references. The region is also automatically unmapped when the process is terminated. On the other hand, closing the file descriptor does not unmap the region.
The address start must be a multiple of the page size. All pages containing a part of the indicated range are unmapped, and subsequent references to these pages will generate SIGSEGV. It is not an error if the indicated range does not contain any mapped pages.
For file-backed mappings, the st_atime field for the mapped file may be updated at any time between the mmap() and the corresponding unmapping; the first reference to a mapped page will update the field if it has not been already.
The st_ctime and st_mtime field for a file mapped with PROT_WRITE and MAP_SHARED will be updated after a write to the mapped region, and before a subsequent msync() with the MS_SYNC or MS_ASYNC flag, if one occurs.
|EACCES||A file descriptor refers to a non-regular file. Or MAP_PRIVATE was requested, but fd is not open for reading. Or MAP_SHARED was requested and PROT_WRITE is set, but fd is not open in read/write (O_RDWR) mode. Or PROT_WRITE is set, but the file is append-only.|
|EAGAIN||The file has been locked, or too much memory has been locked (see setrlimit(2)).|
|EBADF||fd is not a valid file descriptor (and MAP_ANONYMOUS was not set).|
|EINVAL||We dont like start or length or offset. (E.g., they are too large, or not aligned on a page boundary.)|
|ENFILE||The system limit on the total number of open files has been reached.|
|ENODEV||The underlying filesystem of the specified file does not support memory mapping.|
|ENOMEM||No memory is available, or the processs maximum number of mappings would have been exceeded.|
|EPERM||The prot argument asks for PROT_EXEC but the mapped area belongs to a file on a filesystem that was mounted no-exec.|
|MAP_DENYWRITE was set but the object specified by fd is open for writing.|
|Use of a mapped region can result in these signals:|
|Attempted write into a region mapped as read-only.|
|SIGBUS||Attempted access to a portion of the buffer that does not correspond to the file (for example, beyond the end of the file, including the case where another process has truncated the file).|
In kernels before 2.6.7, the MAP_POPULATE flag only has effect if prot is specified as PROT_NONE.
Copyright © tutorialspoint.com