Initializing allocated memory
POSIX requires that mmap() zero any memory that it allocates. It can take a while to initialize the memory, so BlackBerry PlayBook OS provides a way to relax the POSIX requirement. This allows for faster starting, but can be a security problem.
Avoiding initializing the memory requires the cooperation of the process doing the unmapping and the one doing the mapping:
function is a non-POSIX function that's similar to
but lets you control what happens when the memory is next mapped:
int munmap_flags( void *addr, size_t len, unsigned flags );
If you specify a flags argument of 0, munmap_flags() behaves the same as munmap() does.
The following bits control the clearing of memory on allocation:
- POSIX initialization of the page to all zeroes is required the next time the underlying physical memory is allocated.
- Initialization of the underlying physical memory to zeroes on its next allocation is optional.
- If you specify the MAP_NOINIT flag to mmap() , and the physical memory being mapped was previously unmapped with UNMAP_INIT_OPTIONAL, the POSIX requirement that the memory be zeroed is relaxed.
By default, the kernel initializes the memory, but you can control this by using the -m option to procnto . The argument to this option is a string that lets you enable or disable aspects of the memory manager:
- munmap() acts as if UNMAP_INIT_REQUIRED were specified.
- munmap() acts as if UNMAP_INIT_OPTIONAL were specified.
By default when memory is freed for later reuse, the contents of that memory remain untouched; whatever the application that owned the memory left behind is left intact until the next time that memory is allocated by another process. The munmap_flags() function supports the following bits that let you control the clearing when unmapping:
- Clean the memory region when the unmapping is done, if possible (it isn't cleaned if there are still other references to it, for example if it's a shared memory region and there are still other processes referencing it).
- Don't clean the memory on unmapping, even if clean-on-unmapping is the default behavior. Instead, the cleaning is done the next time the memory pages are allocated to another process.
You can also use the -m option to procnto to control the default behavior:
- Clear memory when it's freed.
- Don't clear memory when it's freed (the default). When memory is freed for later reuse, the contents of that memory remain untouched; whatever the application that owned the memory left behind is left intact until the next time that memory is allocated by another process. At that point, before the memory is handed to the next process, it's zeroed.