Lines Matching defs:sem_lock
189 * a) global sem_lock() for read/write
195 * b) global or semaphore sem_lock() for read/write:
203 * * global sem_lock() for write
204 * * either local or global sem_lock() for read.
222 * Initialization is done while holding sem_lock(), so no further barrier is
225 * smp_store_release() (for case a) and while holding sem_lock()
227 * The AQUIRE when reading the result code without holding sem_lock() is
230 * Reading the result code while holding sem_lock() needs no further barriers,
231 * the locks inside sem_lock() enforce ordering (case b above)
234 * current->state is set to TASK_INTERRUPTIBLE while holding sem_lock().
237 * when holding sem_lock(), no further barriers are required.
386 static inline int sem_lock(struct sem_array *sma, struct sembuf *sops,
498 sem_lock(sma, NULL, -1);
1377 sem_lock(sma, NULL, -1);
1437 sem_lock(sma, NULL, -1);
1534 sem_lock(sma, NULL, -1);
1625 sem_lock(sma, NULL, -1);
1630 sem_lock(sma, NULL, -1);
2084 locknum = sem_lock(sma, sops, nsops);
2091 * entangled here and why it's RMID race safe on comments at sem_lock()
2168 /* memory ordering ensured by the lock in sem_lock() */
2172 /* memory ordering is ensured by the lock in sem_lock() */
2189 * slowpath (aka after taking sem_lock), such that we can detect
2202 locknum = sem_lock(sma, sops, nsops);
2208 * No necessity for any barrier: We are protect by sem_lock()
2368 sem_lock(sma, NULL, -1);
2438 * The proc interface isn't aware of sem_lock(), it calls
2440 * In order to stay compatible with sem_lock(), we must