Function report

Linux Kernel

v5.5.9

Brick Technologies Co., Ltd

Source Code:kernel\futex.c Create Date:2022-07-28 10:54:27
Last Modify:2020-03-17 15:28:32 Copyright©Brick
home page Tree
Annotation kernel can get tool activityDownload SCCTChinese

Name:xup_owner() - Post lock pi_state and corner case management*@uaddr: user address of the futex*@q: futex_q (contains pi_state and access to the rt_mutex)*@locked: if the attempt to take the rt_mutex succeeded (1) or not (0)* After attempting to lock an

Proto:static int fixup_owner(unsigned int __user *uaddr, struct futex_q *q, int locked)

Type:int

Parameter:

TypeParameterName
unsigned int __user *uaddr
struct futex_q *q
intlocked
2628  ret = 0
2630  If locked Then
2639  If owner != current process Then ret = fixup_pi_state_owner(uaddr, q, current process)
2641  Go to out
2652  If owner == current process Then
2653  ret = fixup_pi_state_owner(uaddr, q, NULL)
2654  Go to out
2661  If rt_mutex_owner( & The PI object:) == current process Then
2662  printk - print a kernel message*@fmt: format string* This is printk(). It can be called from any context. We want it to work.* We try to grab the console_lock. If we succeed, it's easy - we log the* output and call the console drivers
2668  out :
2669  Return If ret Then ret Else locked
Caller
NameDescribe
futex_lock_piUserspace tried a 0 -> TID atomic transition of the futex value* and failed. The kernel side here does the whole locking operation:* if there are waiters then it will block as a consequence of relying* on rt-mutexes, it does PI, etc
futex_wait_requeue_piex_wait_requeue_pi() - Wait on uaddr and take uaddr2*@uaddr: the futex we initially wait on (non-pi)*@flags: futex flags (FLAGS_SHARED, FLAGS_CLOCKRT, etc