syscalls: remove policy from handler checks
The various macros to do checks in system call handlers all implictly would generate a kernel oops if a check failed. This is undesirable for a few reasons: * System call handlers that acquire resources in the handler have no good recourse for cleanup if a check fails. * In some cases we may want to propagate a return value back to the caller instead of just killing the calling thread, even though the base API doesn't do these checks. These macros now all return a value, if nonzero is returned the check failed. K_OOPS() now wraps these calls to generate a kernel oops. At the moment, the policy for all APIs has not changed. They still all oops upon a failed check/ The macros now use the Z_ notation for private APIs. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
This commit is contained in:
parent
2b9b4b2cf7
commit
8345e5ebf0
31 changed files with 365 additions and 330 deletions
|
@ -52,12 +52,12 @@ void _impl_k_thread_abort(k_tid_t thread)
|
|||
#endif
|
||||
|
||||
#ifdef CONFIG_USERSPACE
|
||||
_SYSCALL_HANDLER(k_thread_abort, thread_p)
|
||||
Z_SYSCALL_HANDLER(k_thread_abort, thread_p)
|
||||
{
|
||||
struct k_thread *thread = (struct k_thread *)thread_p;
|
||||
_SYSCALL_OBJ(thread, K_OBJ_THREAD);
|
||||
_SYSCALL_VERIFY_MSG(!(thread->base.user_options & K_ESSENTIAL),
|
||||
"aborting essential thread %p", thread);
|
||||
Z_OOPS(Z_SYSCALL_OBJ(thread, K_OBJ_THREAD));
|
||||
Z_OOPS(Z_SYSCALL_VERIFY_MSG(!(thread->base.user_options & K_ESSENTIAL),
|
||||
"aborting essential thread %p", thread));
|
||||
|
||||
_impl_k_thread_abort((struct k_thread *)thread);
|
||||
return 0;
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue