Lines Matching full:user
9 User mode threads are considered to be untrusted by Zephyr and are therefore
10 isolated from other user mode threads and from the kernel. A flawed or
11 malicious user mode thread cannot leak or modify the private data/resources
13 control another user mode thread or the kernel.
15 Example use-cases of Zephyr's user mode features:
32 'user mode') we aim to protect against the following:
41 - A user thread will by default have read/write access to its own stack
44 - A user thread will never by default have access to user thread stacks
47 - A user thread will never by default have access to thread stacks owned
51 - A user thread may have read/write access to the stacks of other user
56 - On MMU systems, threads may access any user thread stack in the same
62 - User threads by default are not granted default access to any memory
82 - We ensure the detection and safe handling of user mode stack overflows.
90 - We prevent re-entry from user to supervisor mode except through the
93 - We prevent the introduction of new executable code by user mode threads,
110 kernel mode that exposes private kernel data structures to a user thread. RAM
113 - It is possible to make top-level declarations of user mode threads and
119 starvation. Zephyr has no thread priority aging and a user thread of a
124 simultaneously, after which creation of new user threads will fail.
135 - Any user thread will only have access to a subset of memory:
144 - User threads cannot directly access memory belonging to kernel objects.
151 - User threads by default have no permission to access any kernel object or
161 user mode through system calls involves an extra layer of handler functions,
175 at build time if they are to be used from user mode. Dynamic use-cases for
191 be entered with the CPU already in user mode.