Function report

Linux Kernel

v5.5.9

Brick Technologies Co., Ltd

Source Code:include\linux\sched.h Create Date:2022-07-28 05:59:40
Last Modify:2021-07-28 10:30:23 Copyright©Brick
home page Tree
Annotation kernel can get tool activityDownload SCCTChinese

Name:task_pid_vnr

Proto:static inline pid_t task_pid_vnr(struct task_struct *tsk)

Type:pid_t

Parameter:

TypeParameterName
struct task_struct *tsk
1335  Return __task_pid_nr_ns(tsk, PIDTYPE_PID, NULL)
Caller
NameDescribe
dynamic_emit_prefix
SYSCALL_DEFINE1
wait_task_zombieHandle sys_wait4 work for one task in state EXIT_ZOMBIE. We hold* read_lock(&tasklist_lock) on entry. If we return zero, we still hold* the lock and this task is uninteresting. If we return nonzero, we have
wait_task_stoppedwait_task_stopped - Wait for %TASK_STOPPED or %TASK_TRACED*@wo: wait options*@ptrace: is the wait for ptrace*@p: task to wait for* Handle sys_wait4() work for %p in state %TASK_STOPPED or %TASK_TRACED
wait_task_continuedHandle do_wait work for one task in a live, non-stopped state.* read_lock(&tasklist_lock) on entry. If we return zero, we still hold* the lock and this task is uninteresting. If we return nonzero, we have
kill_something_infokill_something_info() interprets pid in interesting ways just like kill(2).* POSIX specifies that kill(-1,sig) is unspecified, but what we have* is probably wrong. Should make it like BSD or SYSV.
ptrace_do_notify
ptrace_signal
do_rt_sigqueueinfo
do_rt_tgsigqueueinfo
SYSCALL_DEFINE3
SYSCALL_DEFINE2Ugh. To avoid negative return values, "getpriority()" will* not return the normal nice-value, but a negated value that* has been offset by 20 (ie it returns 40..1 instead of -20..19)* to stay compatible.
sys_gettid
SYSCALL_DEFINE2This needs some heavy checking
schedule_tailschedule_tail - first thing a freshly forked thread must call.*@prev: the thread we just switched away from.
posix_cpu_nsleep
attach_to_pi_stateValidate that the existing waiter has a pi_state and sanity check* the pi_state against the user space value. If correct, attach to* it.
futex_lock_pi_atomicex_lock_pi_atomic() - Atomic work required to acquire a pi aware futex*@uaddr: the pi futex user address*@hb: the pi futex hash bucket*@key: the futex key associated with uaddr and hb*@ps: the pi_state pointer where we store the result of the* lookup
wake_futex_piCaller must hold a reference on @pi_state.
futex_proxy_trylock_atomicex_proxy_trylock_atomic() - Attempt an atomic lock for the top waiter*@pifutex: the user address of the to futex*@hb1: the from futex hash bucket, must be locked by the caller*@hb2: the to futex hash bucket, must be locked by the caller*@key1: the from
fixup_pi_state_owner
futex_unlock_piUserspace attempted a TID -> 0 atomic transition, and failed.* This is the in-kernel slowpath: we look up the PI state (if any),* and do the rt-mutex unlock.
handle_futex_deathProcess a futex-list entry, check whether it's owned by the* dying task, and do notification if so:
cgroup_procs_show
pidlist_array_loadLoad a cgroup's pidarray with either procs' tgids or tasks' pids
cgroup_css_links_read
SYSCALL_DEFINE3
SYSCALL_DEFINE2
userfault_msg
format_corenamermat_corename will inspect the pattern parameter, and output a* name into corename, which must have space for at least* CORENAME_MAX_SIZE bytes plus one byte for the zero terminator.