The patch titled
Subject: ipc/sem.c: use READ_ONCE()/WRITE_ONCE() for use_global_lock
has been removed from the -mm tree. Its filename was
ipc-semc-use-read_once-write_once-for-use_global_lock-update.patch
This patch was dropped because it was folded into ipc-semc-use-read_once-write_once-for-use_global_lock.patch
------------------------------------------------------
From: Manfred Spraul <manfred@xxxxxxxxxxxxxxxx>
Subject: ipc/sem.c: use READ_ONCE()/WRITE_ONCE() for use_global_lock
Link: https://lkml.kernel.org/r/20210627161919.3196-3-manfred@xxxxxxxxxxxxxxxx
Signed-off-by: Manfred Spraul <manfred@xxxxxxxxxxxxxxxx>
Reviewed-by: Paul E. McKenney <paulmck@xxxxxxxxxx>
Cc: Davidlohr Bueso <dbueso@xxxxxxx>
Cc: <1vier1@xxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
ipc/sem.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/ipc/sem.c~ipc-semc-use-read_once-write_once-for-use_global_lock-update
+++ a/ipc/sem.c
@@ -2439,7 +2439,8 @@ static int sysvipc_sem_proc_show(struct
/*
* The proc interface isn't aware of sem_lock(), it calls
- * ipc_lock_object() directly (in sysvipc_find_ipc).
+ * ipc_lock_object(), i.e. spin_lock(&sma->sem_perm.lock).
+ * (in sysvipc_find_ipc)
* In order to stay compatible with sem_lock(), we must
* enter / leave complex_mode.
*/
_
Patches currently in -mm which might be from manfred@xxxxxxxxxxxxxxxx are
ipc-semc-use-read_once-write_once-for-use_global_lock.patch
ipc-utilc-use-binary-search-for-max_idx.patch
