Re: [lkp] [x86, perf] 7aba70e47c: BUG: unable to handle kernel paging request at 696d2f62

From: Huang\, Ying
Date: Wed Nov 18 2015 - 19:39:06 EST


Hi, Peter,

Peter Zijlstra <peterz@xxxxxxxxxxxxx> writes:

> On Wed, Nov 18, 2015 at 02:33:00PM +0800, kernel test robot wrote:
>> FYI, we noticed the below changes on
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git perf/core
>> commit 7aba70e47ca4e961acb5af96d5127e3fad651c7c ("x86, perf: Optimize stack walk user accesses")
>
> Of course, that commit no longer exists. I re-create the tree every time
> I push it, this means that if you report something a few days later, its
> highly likely its against non-existant commits :/

I am sorry about this. We will try our best to reach real 0day
reporting.

>> [ 21.984049] BUG: unable to handle kernel paging request at 696d2f62
>> [ 21.986759] IP: [<4110c023>] perf_prepare_sample+0xcc/0x51d
>> [ 21.987859] *pdpt = 0000000001a93001 *pde = 0000000000000000
>> [ 21.988015] Oops: 0000 [#1] PREEMPT
>> [ 21.988015] Modules linked in:
>> [ 21.988015] CPU: 0 PID: 496 Comm: trinity-main Not tainted 4.3.0-01147-g7aba70e #1
>
> That doesn't actually look like something the fingered patch touches.
> And seeing how its trinity triggering it, I suspect bisection fail.

Thanks for reminding, we will check the bisection process.

Best Regards,
Huang, Ying
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/