Lines Matching full:safe

102 // runs. It is safe for that to happen on any thread, so it is ok for this type to be `Send`.
163         // SAFETY: Getting the current pointer is always safe.
170     /// [`current`] macro because it is safe.
217         // SAFETY: It's always safe to call `task_uid` on a valid task.
224         // SAFETY: It's always safe to call `task_euid` on a valid task.
231         // SAFETY: It's always safe to call `signal_pending` on a valid task.
260         // thus pass a null pointer. The underlying C function is safe to be used with NULL
268         // SAFETY: It's always safe to call `wake_up_process` on a valid task, even if the task
292         // This is safe even if `kthread_use_mm()`/`kthread_unuse_mm()` are used. There are two
313         // SAFETY: It is safe to call `task_active_pid_ns` without RCU protection when calling it
326         // safe and requires neither RCU locking nor a reference count to be held. Retrieving the
425     // SAFETY: Always safe to call.