This was lower-cased by a commit in 2016 and has survived since. Fixes: 791af9cfcb0c ("locking: Use consistent expressions") Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx> --- locking/locking.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/locking/locking.tex b/locking/locking.tex index 406c5034..0d7666a9 100644 --- a/locking/locking.tex +++ b/locking/locking.tex @@ -381,7 +381,7 @@ In this case, we cannot construct a local locking hierarchy by releasing all locks before invoking unknown code. However, we can instead construct a layered locking hierarchy, as shown in Figure~\ref{fig:locking:Layered Locking Hierarchy for qsort()}. -here, the \co{cmp()} function uses a new Lock~D that is acquired after +Here, the \co{cmp()} function uses a new Lock~D that is acquired after all of Locks~A, B, and~C, avoiding deadlock. We therefore have three layers to the global deadlock hierarchy, the first containing Locks~A and~B, the second containing Lock~C, and -- 2.17.1