osfmk/man/memory_object_data_unlock.html
Server Interface - Request that the memory manager change current access permission on the specified memory object's data.
**kern\_return\_t memory\_object\_data\_unlock**** (memory\_object\_t **memory\_object,** memory\_object\_control\_t **memory\_control,** vm\_offset\_t **offset,** vm\_size\_t **length,** vm\_prot\_t **desired\_access** ); ****kern\_return\_t seqnos\_memory\_object\_data\_unlock**** (memory\_object\_t **memory\_object,** mach\_port\_seqno\_t **seqno,** memory\_object\_control\_t **memory\_control,** vm\_offset\_t **offset,** vm\_size\_t **length,** vm\_prot\_t **desired\_access** );**
memory_object[in abstract-memory-object (receive) right] The abstract memory object port that represents the memory object data.
seqno[in scalar] The sequence number of this message relative to the abstract memory object port.
memory_control[in memory-cache-control send right] The memory cache control port to be used for a response by the memory manager. If the memory object has been supplied to more than one kernel, this parameter identifies the kernel that is making the call.
offset[in scalar] The offset within the memory object.
length[in scalar] The number of bytes to which the access applies, starting at offset. The number converts to an integral number of memory object pages.
desired_access[in scalar] The memory access modes requested for the cached data. Possible values are obtained by or'ing together the following values:
VM_PROT_READ Allows read access.
VM_PROT_WRITE Allows write access.
VM_PROT_EXECUTE Allows execute access.
A memory_object_data_unlock function is called as the result of a kernel message requesting the memory manager to permit at least the desired access to the specified data cached by the kernel. The memory manager is expected to use the memory_object_lock_request call in response.
Only generic errors apply.
Functions: memory_object_lock_completed, memory_object_lock_request, memory_object_server, seqnos_memory_object_server.