From 626763d452ca816a72c8e33d3ec223567dbfb15a Mon Sep 17 00:00:00 2001 From: Philipp Oppermann Date: Tue, 20 Sep 2016 17:16:13 +0200 Subject: [PATCH] =?UTF-8?q?Write=20=E2=80=9CWhat's=20next=3F=E2=80=9D?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- blog/post/11-returning-from-exceptions.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/blog/post/11-returning-from-exceptions.md b/blog/post/11-returning-from-exceptions.md index 281c229f..d0f4fa42 100644 --- a/blog/post/11-returning-from-exceptions.md +++ b/blog/post/11-returning-from-exceptions.md @@ -886,4 +886,7 @@ When we execute `make run` now, we should see the _“It did not crash”_ messa Our `iretq` logic seems to work! So let's remove the `0xdeadbeaf` hack from our `page_fault_handler` again. ## What's next? -double faults +We are now able to catch exceptions and to return from them. However, there are still exceptions that completely crash our kernel by causing a [triple fault]. In the next post, we will fix this issue by handling a special type of exception: the [double fault]. Thus, we will be able to avoid random reboots in our kernel. + +[triple fault]: https://en.wikipedia.org/wiki/Triple_fault +[double fault]: https://en.wikipedia.org/wiki/Double_fault