Subsection of "Type-Safe Memory" was moved upward in commit
e22df8aea3f2 ("defer/rcuusage: Move type-safe-memory section").
Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
---
Hi Paul,
This patch and the next are last minute nitpicks for the
upcoming release.
Thanks, Akira
--
defer/rcuusage.tex | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/defer/rcuusage.tex b/defer/rcuusage.tex
index 3fbe73be..811dd32a 100644
--- a/defer/rcuusage.tex
+++ b/defer/rcuusage.tex
@@ -588,8 +588,9 @@ element being freed and reallocated as the same type of structure
while they are referencing it, but must prohibit a change in type.
This guarantee, called ``type-safe memory'' in
academic literature~\cite{Cheriton96a},
-is weaker than the existence guarantees in the
-previous section, and is therefore quite a bit harder to work with.
+is weaker than the existence guarantees discussed
+in \cref{sec:defer:Existence Guarantee},
+and is therefore quite a bit harder to work with.
Type-safe memory algorithms in the Linux kernel make use of slab caches,
specially marking these caches with \co{SLAB_TYPESAFE_BY_RCU}
so that RCU is used when returning a freed-up
base-commit: a8f5948a1b8921941bf4039e278aa7929f64c322
--
2.17.1
