Lines Matching refs:be

10 by providing a set of APIs that can be used to perform consistent, thorough
40 VM functions can be called from three places: userspace, kexts, and xnu itself.
41 Functions callable from userspace should be fully sanitized. Functions
61 1. rewrite an error code to be a different error code.
62 2. rewrite an error code to be `KERN_SUCCESS`. The VM API returns success
64 Not all changed error codes are (or could be) rewritten.
68 2. The error code being returned would be different from its historical
70 Not all changed error codes are (or could be) telemetered. Currently all
103 - `VM_GENERATE_UNSAFE_ADDR`: Should be used for a new variant that represents
105 - `VM_GENERATE_UNSAFE_SIZE`: Should be used for a new variant that represents
107 - `VM_GENERATE_UNSAFE_TYPE`: Should be used for other types that are not
113 - 32 bit variants like `VM_GENERATE_UNSAFE_ADDR32` should be used for 32bit
118 - EXT variants like `VM_GENERATE_UNSAFE_EXT` should not be used directly. They
237 contain the basic blocks that could be chained to meet your specific
245   were supposed to be sanitized by the function.
311 may also be used to generate new golden files. Test results may also be
321 is more direct than `function_name` would be. Examples: `__mmap`, `__msync`,
330 to VM API that perform sanitizations. These entrypoints should be disabled
348 If you are testing both kernel and userspace you may be able to share much of
368 should be tested. The trials should be exhaustive for small values, and
379 name must be unique within a single test.
386 to be tested. If there is an existing VM API with similar setup or
404 files; each test name must be unique.