From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Jann Horn <jannh@google.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Andrey Ryabinin <aryabinin@virtuozzo.com>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
Andrey Konovalov <andreyknvl@google.com>,
Andy Lutomirski <luto@kernel.org>
Subject: Re: [PATCH v5 2/4] x86/traps: Print address on #GP
Date: Tue, 3 Dec 2019 12:58:51 -0800 [thread overview]
Message-ID: <20191203205850.GF19877@linux.intel.com> (raw)
In-Reply-To: <20191127234916.31175-2-jannh@google.com>
On Thu, Nov 28, 2019 at 12:49:14AM +0100, Jann Horn wrote:
With a few nits below,
Reviewed-and-tested-by: Sean Christopherson <sean.j.christopherson@intel.com>
> +#define GPFSTR "general protection fault"
> +
> dotraplinkage void
> do_general_protection(struct pt_regs *regs, long error_code)
> {
> - const char *desc = "general protection fault";
> struct task_struct *tsk;
> + char desc[sizeof(GPFSTR) + 50 + 2*sizeof(unsigned long) + 1] = GPFSTR;
Nit, x86 maintainers prefer inverse fir tree for variable declarations.
>
> RCU_LOCKDEP_WARN(!rcu_is_watching(), "entry code didn't wake RCU");
> cond_local_irq_enable(regs);
> @@ -540,6 +587,9 @@ do_general_protection(struct pt_regs *regs, long error_code)
>
> tsk = current;
> if (!user_mode(regs)) {
> + enum kernel_gp_hint hint = GP_NO_HINT;
> + unsigned long gp_addr;
> +
> if (fixup_exception(regs, X86_TRAP_GP, error_code, 0))
> return;
>
> @@ -556,8 +606,22 @@ do_general_protection(struct pt_regs *regs, long error_code)
> return;
>
> if (notify_die(DIE_GPF, desc, regs, error_code,
> - X86_TRAP_GP, SIGSEGV) != NOTIFY_STOP)
> - die(desc, regs, error_code);
> + X86_TRAP_GP, SIGSEGV) == NOTIFY_STOP)
> + return;
> +
> + if (error_code)
> + snprintf(desc, sizeof(desc), "segment-related " GPFSTR);
> + else
> + hint = get_kernel_gp_address(regs, &gp_addr);
> +
> + if (hint != GP_NO_HINT)
> + snprintf(desc, sizeof(desc), GPFSTR " %s 0x%lx",
Nit, probably should have a comma before the hint, i.e. GPFSTR ", %s...".
general protection fault maybe for address 0xffffc9000017cf58: 0000 [#1] SMP
general protection fault probably for non-canonical address 0xdead000000000000: 0000 [#1] SMP
vs.
general protection fault, maybe for address 0xffffc9000017cf58: 0000 [#1] SMP
general protection fault, probably for non-canonical address 0xdead000000000000: 0000 [#1] SMP
> + (hint == GP_NON_CANONICAL) ?
> + "probably for non-canonical address" :
> + "maybe for address",
> + gp_addr);
> +
> + die(desc, regs, error_code);
> return;
> }
>
> --
> 2.24.0.432.g9d3f5f5b63-goog
>
next prev parent reply other threads:[~2019-12-03 20:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 23:49 [PATCH v5 1/4] x86/insn-eval: Add support for 64-bit kernel mode Jann Horn
2019-11-27 23:49 ` [PATCH v5 2/4] x86/traps: Print address on #GP Jann Horn
2019-12-03 20:58 ` Sean Christopherson [this message]
2019-11-27 23:49 ` [PATCH v5 3/4] x86/dumpstack: Split out header line printing from __die() Jann Horn
2019-11-27 23:49 ` [PATCH v5 4/4] x86/kasan: Print original address on #GP Jann Horn
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=20191203205850.GF19877@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=andreyknvl@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=bp@alien8.de \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=hpa@zytor.com \
--cc=jannh@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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 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.