public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dave.hansen@linux.intel.com, Andrew Lutomirski <luto@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	bp@alien8.de, the arch/x86 maintainers <x86@kernel.org>,
	Peter Anvin <hpa@zytor.com>,
	Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	Rik van Riel <riel@surriel.com>,
	yu-cheng.yu@intel.com, Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] x86/fault: Decode and print #PF oops in human readable form
Date: Fri, 7 Dec 2018 11:18:48 -0800	[thread overview]
Message-ID: <20181207191848.GD10404@linux.intel.com> (raw)
In-Reply-To: <CAHk-=whMhJ84SqnUa0qAV-xkP6ghictLv8RLxOrp8mXKfp5zqQ@mail.gmail.com>

On Fri, Dec 07, 2018 at 10:52:49AM -0800, Linus Torvalds wrote:
> On Fri, Dec 7, 2018 at 10:44 AM Sean Christopherson
> <sean.j.christopherson@intel.com> wrote:
> >
> > Remove the per-bit decoding of the error code and instead print the raw
> > error code followed by a brief description of what caused the fault, the
> > effective privilege level of the faulting access, and whether the fault
> > originated in user code or kernel code.
> 
> This doesn't quite work as-is, though.
> 
> For example, at least the PK bit is independent of the other bits and
> would be interesting in the human-legible version, but doesn't show up
> there at all.

Heh, I actually intentionally omitted protection keys thinking it'd be
superfluous, i.e. "go look at the error code bits if you care that much".

> That said, I think the end result might be more legible than the
> previous version, so this approach may well be good, it just needs at
> least that "permissions violation"  part to be extended with whether
> it was PK or not.
> 
> Also, shouldn't we show the SGX bit too as some kind of "during SGX"
> extension on the "in user/kernel space" part?

The SGX bit isn't defined in mainline yet.  But yeah, I can see how
printing e.g. "SGX EPCM violation" would be a lot more helpful than
a vanilla "permissions violation".  I'll send a v2 with the PK bit
added and a slightly reworded changelog.

  reply	other threads:[~2018-12-07 19:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05 16:36 [PATCH] x86/fault: Print "SUPERVISOR" and "READ" when decoding #PF oops Sean Christopherson
2018-12-05 19:27 ` Randy Dunlap
2018-12-05 19:35   ` Linus Torvalds
2018-12-06  7:34 ` [PATCH] x86/mm/fault: Streamline the fault error_code decoder some more Ingo Molnar
2018-12-06 15:53   ` Sean Christopherson
2018-12-06 16:23     ` Ingo Molnar
2018-12-06 16:39     ` Andy Lutomirski
2018-12-06 16:47       ` Ingo Molnar
2018-12-06 17:05         ` Andy Lutomirski
2018-12-06 17:36           ` Ingo Molnar
2018-12-06 18:15   ` Linus Torvalds
2018-12-06 19:06     ` Andy Lutomirski
2018-12-06 20:24       ` Linus Torvalds
2018-12-06 20:28         ` Andy Lutomirski
2018-12-06 20:39           ` Linus Torvalds
2018-12-07 18:44             ` [PATCH] x86/fault: Decode and print #PF oops in human readable form Sean Christopherson
2018-12-07 18:52               ` Linus Torvalds
2018-12-07 19:18                 ` Sean Christopherson [this message]
2018-12-07 19:52               ` [PATCH v2] " Sean Christopherson
2018-12-07 20:46                 ` Linus Torvalds
2018-12-07 22:06                   ` Sean Christopherson
2018-12-07 22:14                     ` Linus Torvalds
2018-12-07 23:57                       ` Andy Lutomirski
2018-12-10 16:04                         ` 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=20181207191848.GD10404@linux.intel.com \
    --to=sean.j.christopherson@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=riel@surriel.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    --cc=yu-cheng.yu@intel.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox