aboutsummaryrefslogtreecommitdiff
path: root/website/content/en/status/report-2021-10-2021-12/membarrier-rseq.adoc
diff options
context:
space:
mode:
Diffstat (limited to 'website/content/en/status/report-2021-10-2021-12/membarrier-rseq.adoc')
-rw-r--r--website/content/en/status/report-2021-10-2021-12/membarrier-rseq.adoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/website/content/en/status/report-2021-10-2021-12/membarrier-rseq.adoc b/website/content/en/status/report-2021-10-2021-12/membarrier-rseq.adoc
index a0362524e1..814598c6aa 100644
--- a/website/content/en/status/report-2021-10-2021-12/membarrier-rseq.adoc
+++ b/website/content/en/status/report-2021-10-2021-12/membarrier-rseq.adoc
@@ -86,7 +86,7 @@ system-global context switches. Instead, if the process registered for
rseq(2), on any return to user mode we check if any exceptional
events happened while the thread was in the kernel (context switches may happen
only while the thread is in kernel mode), and if a context switch indeed
-occured, we fire an ast to check whether the program counter is inside the
+occurred, we fire an ast to check whether the program counter is inside the
critical section and jump to the abort handler if it is.
The implementations of membarrier(2) and rseq(2) are clean-room: I used