Hello!
According to the context and my understanding of locking primitives, I
suppose the 'exists' clause in the litmus test shouldn't be satisfied.
Signed-off-by: Patrick Pan <pyxchina92929@xxxxxxxxx>
---
memorder/memorder.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/memorder/memorder.tex b/memorder/memorder.tex
index a0a87d0a..9c1846d0 100644
--- a/memorder/memorder.tex
+++ b/memorder/memorder.tex
@@ -3452,7 +3452,7 @@ following subsequent critical sections?
This question can be answered for the Linux kernel by referring to
\cref{lst:memorder:Accesses Outside of Critical Sections}
(\path{C-Lock-outside-across.litmus}).
-Running this litmus test yields the \co{Sometimes} result,
+Running this litmus test yields the \co{Never} result,
which means that accesses in code leading up to a prior critical section
is also visible to the current CPU or thread holding that same lock.
Similarly, code that is placed after a subsequent critical section
base-commit: 7f12a9358e220f3d0c3a0880d01bc283113d7a5b
--
