[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrUoV9AbpTaQa_TmnEncogsMRmVvpyX0pBp6gxy8252JUw@mail.gmail.com>
Date: Wed, 15 Jun 2016 11:12:37 -0700
From: Andy Lutomirski <luto@...capital.net>
To: Borislav Petkov <bp@...en8.de>
Cc: Paolo Bonzini <pbonzini@...hat.com>, wfg@...ux.intel.com,
LKP <lkp@...org>, lkml <linux-kernel@...r.kernel.org>,
Fengguang Wu <fengguang.wu@...el.com>,
Eduardo Habkost <ehabkost@...hat.com>,
Josh Poimboeuf <jpoimboe@...hat.com>
Subject: Re: [x86] 5ac0c41bf3: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50
ex_handler_rdmsr_unsafe
On Wed, Jun 15, 2016 at 11:07 AM, Borislav Petkov <bp@...en8.de> wrote:
> On Wed, Jun 15, 2016 at 10:55:34AM -0700, Andy Lutomirski wrote:
>> Isn't it this one?
>
> Yes, it is.
>
>> I'm not. If %pF points at some silly helper, we still want the frames below it.
>
> Why silly helper? It points to the rIP where the *MSR instruction is.
> Can't get more precise than that.
A hypothetical helper.
void do_thing(unsigned long msr)
{
rdmsr(...);
}
void actual_problem(void)
{
do_thing(0xbaadc0de);
}
I want to see actual_problem in the log.
--Andy
Powered by blists - more mailing lists