context: more on memory management and weaknesses

This commit is contained in:
steveej 2017-09-11 22:54:22 +02:00
parent e69951fe71
commit ebc4bcb8bb
8 changed files with 547 additions and 312 deletions

View file

@ -2,7 +2,10 @@
\chapter{Topic Refinement}
% TODO: is this chapter required?
\chapter{Derived Research Questions}
\chapter{Research Questions}
Setting up and maintaining the paging-structure, as well as allocating physical memory for the virtual pages is a complex task in the \gls{OS}.
Developing this part of the \gls{OS} is error-prone, and is not well-supported by mainstream \glspl{proglang}.
\subsection{Definition Of Additional Analysis Rules To Extend Safety Checks}
% TODO: How can Business Logical
@ -32,13 +35,13 @@
\chapter{Porting \glsentrytext{C} Vulnerabilities}
\label{rnd:porting-c-vulns}
\label{rnd::porting-c-vulns}
In this chapter, the examples from \autoref{TODO} ported to \gls{Rust} for evaluation.
\chapter{\glsentrytext{LX} Modules Written In \glsentrytext{Rust}}
% TODO: describe Difficulties with the GPL Macros used Within Kernel Modules
\chapter{Existing \glsentrytext{OS}-Development Projects Based On Rust}
\label{rnd::existing-os-in-rust}
\section{Libraries}
@ -54,6 +57,7 @@ In this chapter, the examples from \autoref{TODO} ported to \gls{Rust} for evalu
\chapter{\glsentrytext{imezzos}: Adding Preemptive \glsentrytext{OS}-Level Multitasking}
\section{Timed Interrupts For Scheduling and Dispatching}
\section{Simple Stack Allocation Scheme}
\section{Risk Of Stack-Overflow}
@ -64,17 +68,3 @@ In this chapter, the examples from \autoref{TODO} ported to \gls{Rust} for evalu
% Stack size for each function: calculated,
% Call-Tree: calculated,
\chapter{Result Generalization}
\section{Low-Level Safe Abstractions in Rust}
% TODO: Is the static analysis of hardware specific assembly code possible and useful at all?
% TODO: LLVM knows about the target and can potentially give hints about hardware specific instructions
\section{Tracking \textit{'static}ally allocated Resources}
\section{The Necessary Evils of \textit{unsafe}}
\chapter{Result Evaluation}
% TODO: repeat that rust *can* be used to increase safety in the OS, but it doesn't guarantee it per-se
\chapter{Summary}