Lines Matching refs:will
19 dereference these addresses, doing so will cause a memory protection fault.
39 will be freed.
65 Kernel objects that are found but do not meet the above conditions will not be
71 information will be printed if the script is run with the ``--verbose`` flag,
87 permissions on it) the object will be automatically freed. User threads
106 the object placement criteria will have their memory addresses placed in a
126 option and the build system will generate an error if this value is too low.
144 thread will then run in user mode with any permissions it had been granted
148 :c:macro:`K_INHERIT_PERMS` option, the child thread will be granted the
154 By default, when a user thread is created, it will only have access permissions
160 will inherit all the permissions of the parent thread, except the parent
176 untrusted or exploited code will then be able to access the object. Use
190 not being tracked by the kernel will be no-ops. Doing the same from user mode
191 will result in a fatal error for the calling thread.
199 Most operations on kernel objects will fail if the object is considered to be
203 Some objects will be implicitly initialized at boot:
206 (such as :c:macro:`K_SEM_DEFINE` for semaphores) will be in an initialized
214 thread, otherwise the kernel will consider the object uninitialized if accessed