75a10a74e8
When copying an area with vm_copy_area only the new protection would be applied and any possibly existing page protections on the source area were ignored. For areas with stricter area protection than page protection, this lead to faults when accessing the copy. In the opposite case it lead to too relaxed protection. The currently only user of vm_copy_area is fork_team which goes through all areas of the parent and copies them to the new team. Hence page protections were ignored on all forked teams. Remove the protection argument and instead always carry over the source area protection and duplicate the page protections when present. Also make sure to take the page protections into account for deciding whether or not the copy is writable and therefore needs to have copy on write semantics. Change-Id: I52f295f2aaa66e31b4900b754343b3be9a19ba30 Reviewed-on: https://review.haiku-os.org/c/haiku/+/3166 Reviewed-by: waddlesplash <waddlesplash@gmail.com> |
||
|---|---|---|
| .. | ||
| vm_page.h | ||
| vm_priv.h | ||
| vm_types.h | ||
| vm.h | ||
| VMAddressSpace.h | ||
| VMArea.h | ||
| VMCache.h | ||
| VMTranslationMap.h | ||