[PATCH] Print error code in page faults

When a page faults comes from a kernel space, the printed summary
leaves us clueless about what kind of access was being tried (which
is encoded in the error_code variable).

Having it promply available may ease debugging in a bunch of
situations.

Signed-off-by: Glauber de Oliveira Costa <[email protected]>

diff --git a/arch/x86_64/mm/fault.c b/arch/x86_64/mm/fault.c
index 6ada723..e65522e 100644
--- a/arch/x86_64/mm/fault.c
+++ b/arch/x86_64/mm/fault.c
@@ -539,7 +539,7 @@ no_context:
 		printk(KERN_ALERT "Unable to handle kernel NULL pointer dereference");
 	else
 		printk(KERN_ALERT "Unable to handle kernel paging request");
-	printk(" at %016lx RIP: \n" KERN_ALERT,address);
+	printk(" at %016lx (error=0x%02lx) RIP: \n" KERN_ALERT, error_code, address);
 	printk_address(regs->rip);
 	dump_pagetable(address);
 	tsk->thread.cr2 = address;

---

• Follow-Ups:
  • Re: [PATCH] Print error code in page faults
    • From: Andi Kleen <[email protected]>
  • Re: [PATCH] Print error code in page faults
    • From: Chuck Ebbert <[email protected]>

• Prev by Date: Re: [rfc][patch] dynamic resizing dentry hash using RCU
• Next by Date: Re: SLUB: The unqueued Slab allocator
• Previous by thread: [RFC] div64_64 support
• Next by thread: Re: [PATCH] Print error code in page faults
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]