diff options
| author | Dev Jain <dev.jain@arm.com> | 2025-11-12 11:57:16 +0530 |
|---|---|---|
| committer | Catalin Marinas <catalin.marinas@arm.com> | 2025-11-28 15:36:40 +0000 |
| commit | 0c2988aaa4d3eda94b738d5a7acae7838d52fe4d (patch) | |
| tree | ff06d71c97e5559554bc21defe34cdc67db8cfc5 /net/unix/af_unix.c | |
| parent | e5efd56fa157d2e7d789949d1d64eccbac18a897 (diff) | |
arm64/mm: Document why linear map split failure upon vm_reset_perms is not problematic
Consider the following code path:
(1) vmalloc -> (2) set_vm_flush_reset_perms -> (3) set_memory_ro/set_memory_rox
-> .... (4) use the mapping .... -> (5) vfree -> (6) vm_reset_perms
-> (7) set_area_direct_map.
Or, it may happen that we encounter failure at (3) and directly jump to (5).
In both cases, (7) may fail due to linear map split failure. But, we care
about its success *only* for the region which got successfully changed by
(3). Such a region is guaranteed to be pte-mapped.
The TLDR is that (7) will surely succeed for the regions we care about.
Signed-off-by: Dev Jain <dev.jain@arm.com>
Reviewed-by: Ryan Roberts <ryan.roberts@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions