Skip to content

Commit

Permalink
Kernel slides: update memory debugging frameworks
Browse files Browse the repository at this point in the history
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
  • Loading branch information
michaelopdenacker committed Jun 10, 2021
1 parent acbcbae commit 53e8492
Showing 1 changed file with 10 additions and 5 deletions.
Expand Up @@ -358,20 +358,25 @@ \section{Memory Management}
\begin{itemize}
\item Dynamic memory error detector, to find use-after-free and
out-of-bounds bugs.
\item Only available on \code{x86} (64 bit), \code{arm64}, \code{riscv}
(64 bit), \code{powerpc} (32 bit), \code{s390} and \code{xtensa} so far
(Linux 5.11 status), but will help to improve architecture independent
code anyway.
\item Available on most archictures
\item See \kdochtml{dev-tools/kasan} for details.
\end{itemize}
\item \code{KFENCE} ({\em Kernel Electric Fence})
\begin{itemize}
\item A low overhead alternative to KASAN, trading performance
for precision. Meant to be used in production systems.
\item Only available on \code{x86}, \code{arm64} and \code{powerpc}
(Linux 5.13 status)
\item See \kdochtml{dev-tools/kfence} for details.
\end{itemize}
\item \code{Kmemleak}
\begin{itemize}
\item Dynamic checker for memory leaks
\item This feature is available for all architectures.
\item See \kdochtml{dev-tools/kmemleak} for details.
\end{itemize}
\end{itemize}
Both have a significant overhead. Only use them in development!
KASAN and Kmemleak have a significant overhead. Only use them in development!
\end{frame}

\begin{frame}
Expand Down

0 comments on commit 53e8492

Please sign in to comment.