patch-2.1.99 linux/Documentation/exception.txt

• Lines: 45
• Date: Tue Apr 28 14:22:04 1998
• Orig file: v2.1.98/linux/Documentation/exception.txt
• Orig date: Mon Nov 11 01:07:43 1996

diff -u --recursive --new-file v2.1.98/linux/Documentation/exception.txt linux/Documentation/exception.txt
@@ -9,7 +9,7 @@
 int verify_area(int type, const void * addr, unsigned long size) 
 function.
 
-This function verified, that the memory area starting at address 
+This function verified that the memory area starting at address 
 addr and of size size was accessible for the operation specified 
 in type (read or write). To do this, verify_read had to look up the 
 virtual memory area (vma) that contained the address addr. In the 
@@ -53,7 +53,7 @@
 Since we jump to the the contents of fixup, fixup obviously points 
 to executable code. This code is hidden inside the user access macros. 
 I have picked the get_user macro defined in include/asm/uacess.h as an
-example. The definition is somewhat hard to follow, so lets peek at 
+example. The definition is somewhat hard to follow, so let's peek at 
 the code generated by the preprocessor and the compiler. I selected
 the get_user call in drivers/char/console.c for a detailed examination.
 
@@ -122,7 +122,7 @@
   }
 );
 
-WOW! Black GCC/assembly magic. This is impossible to follow, so lets
+WOW! Black GCC/assembly magic. This is impossible to follow, so let's
 see what code gcc generates:
 
  >         xorl %edx,%edx
@@ -266,7 +266,7 @@
 3.) CPU calls do_page_fault
 4.) do page fault calls search_exception_table (regs->eip == c017e7a5);
 5.) search_exception_table looks up the address c017e7a5 in the
-    exception table (i.e. the contents of the ELF section __ex_table 
+    exception table (i.e. the contents of the ELF section __ex_table) 
     and returns the address of the associated fault handle code c0199ff5.
 6.) do_page_fault modifies its own return address to point to the fault 
     handle code and returns.
@@ -278,7 +278,7 @@
 
 The steps 8a to 8c in a certain way emulate the faulting instruction.
 
-That's it, mostely. If you look at our example, you might ask, why
+That's it, mostly. If you look at our example, you might ask why
 we set EAX to -EFAULT in the exception handler code. Well, the
 get_user macro actually returns a value: 0, if the user access was
 successful, -EFAULT on failure. Our original code did not test this