diff options
| author | John David Anglin <dave.anglin@bell.net> | 2022-01-04 21:40:02 +0000 |
|---|---|---|
| committer | Helge Deller <deller@gmx.de> | 2022-01-07 01:29:21 +0100 |
| commit | 20dda87bdc6567e864942ead40bc149ebbe3ae79 (patch) | |
| tree | b6dfec6b18c4984c356ec144612c5e6c80978e4a | |
| parent | 9d90a90855ceb9ce0fb9b46b0591ac211e4b4612 (diff) | |
| download | linux-20dda87bdc6567e864942ead40bc149ebbe3ae79.tar.bz2 | |
parisc: Enhance page fault termination message
In debugging kernel panics, I believe it is useful to know what type
of page fault caused the termination. "Bad Address" is too vague.
Signed-off-by: John David Anglin <dave.anglin@bell.net>
Signed-off-by: Helge Deller <deller@gmx.de>
| -rw-r--r-- | arch/parisc/mm/fault.c | 14 |
1 files changed, 10 insertions, 4 deletions
diff --git a/arch/parisc/mm/fault.c b/arch/parisc/mm/fault.c index 499e2e8f7f34..147868427b7c 100644 --- a/arch/parisc/mm/fault.c +++ b/arch/parisc/mm/fault.c @@ -266,11 +266,14 @@ void do_page_fault(struct pt_regs *regs, unsigned long code, unsigned long acc_type; vm_fault_t fault = 0; unsigned int flags; + char *msg; tsk = current; mm = tsk->mm; - if (!mm) + if (!mm) { + msg = "Page fault: no context"; goto no_context; + } flags = FAULT_FLAG_DEFAULT; if (user_mode(regs)) @@ -406,6 +409,7 @@ bad_area: force_sig_fault(signo, si_code, (void __user *) address); return; } + msg = "Page fault: bad address"; no_context: @@ -413,11 +417,13 @@ no_context: return; } - parisc_terminate("Bad Address (null pointer deref?)", regs, code, address); + parisc_terminate(msg, regs, code, address); - out_of_memory: +out_of_memory: mmap_read_unlock(mm); - if (!user_mode(regs)) + if (!user_mode(regs)) { + msg = "Page fault: out of memory"; goto no_context; + } pagefault_out_of_memory(); } |