From: Borislav Petkov <bp@alien8.de> To: hpa@zytor.com, torvalds@linux-foundation.org, luto@kernel.org, sean.j.christopherson@intel.com, peterz@infradead.org, tglx@linutronix.de, mingo@kernel.org, linux-kernel@vger.kernel.org, riel@surriel.com, dave.hansen@linux.intel.com, yu-cheng.yu@intel.com Cc: linux-tip-commits@vger.kernel.org Subject: Re: [tip:x86/mm] x86/fault: Decode and print #PF oops in human readable form Date: Sun, 21 Apr 2019 20:35:24 +0200 [thread overview] Message-ID: <20190421183524.GC6048@zn.tnic> (raw) In-Reply-To: <tip-18ea35c5ed9921867194a8efc2a0ac2d5a3c7d2a@git.kernel.org> On Fri, Apr 19, 2019 at 11:35:51AM -0700, tip-bot for Sean Christopherson wrote: > BUG: kernel NULL pointer dereference, address = 0000000000000008 > #PF: supervisor-privileged instruction fetch from kernel code > #PF: error_code(0x0010) - not-present page > > BUG: unable to handle page fault for address = ffffbeef00000000 > #PF: supervisor-privileged instruction fetch from kernel code > #PF: error_code(0x0010) - not-present page > > BUG: unable to handle page fault for address = ffffc90000230000 > #PF: supervisor-privileged write access from kernel code > #PF: error_code(0x000b) - reserved bit violation Writing those in human-readable form is nice. May I suggest making those messages more succinct, though - we'll be staring at them for years, after all. --- From: Borislav Petkov <bp@suse.de> Date: Sun, 21 Apr 2019 20:24:08 +0200 Subject: [PATCH] x86/fault: Make fault messages more succinct So we are going to be staring at those in the next years, let's make them more succinct. In particular: - change "address = " to "address: " - "-privileged" reads funny. It should be simply "kernel" or "user" - "from kernel code" reads funny too. "kernel mode" or "user mode" is more natural. An actual example says more than 1000 words, of course: [ 0.248370] BUG: kernel NULL pointer dereference, address: 00000000000005b8 [ 0.249120] #PF: supervisor write access in kernel mode [ 0.249717] #PF: error_code(0x0002) - not-present page Signed-off-by: Borislav Petkov <bp@suse.de> --- arch/x86/mm/fault.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/arch/x86/mm/fault.c b/arch/x86/mm/fault.c index 74c9204c5751..a0df19b0897d 100644 --- a/arch/x86/mm/fault.c +++ b/arch/x86/mm/fault.c @@ -630,13 +630,13 @@ show_fault_oops(struct pt_regs *regs, unsigned long error_code, unsigned long ad } if (address < PAGE_SIZE && !user_mode(regs)) - pr_alert("BUG: kernel NULL pointer dereference, address = %px\n", + pr_alert("BUG: kernel NULL pointer dereference, address: %px\n", (void *)address); else - pr_alert("BUG: unable to handle page fault for address = %px\n", + pr_alert("BUG: unable to handle page fault for address: %px\n", (void *)address); - pr_alert("#PF: %s-privileged %s from %s code\n", + pr_alert("#PF: %s %s in %s mode\n", (error_code & X86_PF_USER) ? "user" : "supervisor", (error_code & X86_PF_INSTR) ? "instruction fetch" : (error_code & X86_PF_WRITE) ? "write access" : -- 2.21.0 -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-04-21 18:35 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-12-21 21:36 [PATCH v3 0/2] x86/fault: Further improve #PF oops messages Sean Christopherson 2018-12-21 21:36 ` [PATCH v3 1/2] x86/fault: Reword initial BUG message for unhandled page faults Sean Christopherson 2019-04-19 18:35 ` [tip:x86/mm] " tip-bot for Sean Christopherson 2018-12-21 21:36 ` [PATCH v3 2/2] x86/fault: Decode and print #PF oops in human readable form Sean Christopherson 2019-04-19 18:35 ` [tip:x86/mm] " tip-bot for Sean Christopherson 2019-04-21 18:35 ` Borislav Petkov [this message] 2019-04-21 18:52 ` [tip:x86/mm] x86/fault: Make fault messages more succinct tip-bot for Borislav Petkov 2019-04-29 13:58 ` [PATCH v3 2/2] x86/fault: Decode and print #PF oops in human readable form Dmitry Vyukov 2019-04-29 14:14 ` Borislav Petkov 2019-02-28 15:44 ` [PATCH v3 0/2] x86/fault: Further improve #PF oops messages Sean Christopherson
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20190421183524.GC6048@zn.tnic \ --to=bp@alien8.de \ --cc=dave.hansen@linux.intel.com \ --cc=hpa@zytor.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-tip-commits@vger.kernel.org \ --cc=luto@kernel.org \ --cc=mingo@kernel.org \ --cc=peterz@infradead.org \ --cc=riel@surriel.com \ --cc=sean.j.christopherson@intel.com \ --cc=tglx@linutronix.de \ --cc=torvalds@linux-foundation.org \ --cc=yu-cheng.yu@intel.com \ --subject='Re: [tip:x86/mm] x86/fault: Decode and print #PF oops in human readable form' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.