linux-kernel - Re: [PATCH] x86/fault: Decode page fault OOPSes better

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <8268eb6b-ea83-385f-de5f-e79f4d8a454c@linux.intel.com>
Date:   Thu, 6 Sep 2018 10:27:08 -0700
From:   Dave Hansen <dave.hansen@...ux.intel.com>
To:     Andy Lutomirski <luto@...nel.org>, x86@...nel.org
Cc:     Borislav Petkov <bp@...en8.de>,
        LKML <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Josh Poimboeuf <jpoimboe@...hat.com>
Subject: Re: [PATCH] x86/fault: Decode page fault OOPSes better

On 08/31/2018 08:42 PM, Andy Lutomirski wrote:
> One of Linus' favorite hobbies seems to be looking at OOPSes and
> decoding the error code in his head.  This is not one of my favorite
> hobbies :)

I just work around this by having a screenshot of 'enum
x86_pf_error_code' as my desktop background.

I love stuff like this.  I'd only ask for more, like in
show_signal_msg() or the page fault tracepoints too.

BTW, I'm feeling rather perturbed that error_code diverges from the
hardware-issued error code for user-mode implicit accesses/buglets.  I
really wish captured the "raw" hardware error codes.