Lines Matching refs:task

18      - Accessing task credentials.
19      - Accessing another task's credentials.
55      accounting and limitation (disk quotas and task rlimits for example).
79      For instance an open file may send SIGIO to a task using the UID and EUID
80      given to it by a task that called fcntl(F_SETOWN) upon it.  In this case,
90      A Linux task, for example, has the FSUID, FSGID and the supplementary
93      task.
175      granted piecemeal to a task that an ordinary task wouldn't otherwise have.
184      The effective capabilities are the ones that a task is actually allowed to
224      operations that a task may do.  Currently Linux supports several LSM
228      rules (policies) that say what operations a task with one label may do to
235      interact directly with task and file credentials; rather it keeps system
239 When a file is opened, part of the opening task's subjective context is
241 struct to use those credentials instead of the subjective context of the task
267 These are compared to the task's subjective security context, and certain
277 In Linux, all of a task's credentials are held in (uid, gid) or through
279 Each task points to its credentials by a pointer called 'cred' in its
302 the task pointer to make it point to the new copy.  There are wrappers to aid
305 A task may only alter its _own_ credentials; it is no longer permitted for a
306 task to alter another's credentials.  This means the capset() system call is no
334 A task being able to alter only its own credentials permits the current process
343 There are convenience wrappers for retrieving specific aspects of a task's
357 a task's credentials:
364 them from the current task's credentials.
388 Whilst a task may access its own credentials without the need for locking, the
389 same is not true of a task wanting to access another task's credentials.  It
394 	const struct cred *__task_cred(struct task_struct *task);
411 Should it be necessary to hold another task's credentials for a long period of
415 	const struct cred *get_task_cred(struct task_struct *task);
423 There are a couple of convenience functions to access bits of another task's
426 	uid_t task_uid(task)		Task's real UID
427 	uid_t task_euid(task)		Task's effective UID
431 	__task_cred(task)->uid
432 	__task_cred(task)->euid
434 should be used instead.  Similarly, if multiple aspects of a task's credentials
440 Should some other single aspect of another task's credentials need to be
443 	task_cred_xxx(task, member)
447 	uid_t task_cred_xxx(task, suid);
449 will retrieve 'struct cred::suid' from the task, doing the appropriate RCU
457 As previously mentioned, a task may only alter its own credentials, and may not
458 alter those of another task.  This means that it doesn't need to use any
558 When a new file is opened, a reference is obtained on the opening task's