[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANaxB-yFpddZi-q_=gsh-b1yYtLeUVkFUAp-m21jC9ZTgye9Kw@mail.gmail.com>
Date: Mon, 13 Nov 2017 14:06:35 -0800
From: Andrei Vagin <avagin@...il.com>
To: Josh Poimboeuf <jpoimboe@...hat.com>
Cc: Andrei Vagin <avagin@...tuozzo.com>, X86 ML <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Andy Lutomirski <luto@...nel.org>
Subject: Re: [PATCH 1/3] x86/entry: Fix idtentry unwind hint
Hi Josh,
On Thu, Oct 26, 2017 at 8:24 AM, Josh Poimboeuf <jpoimboe@...hat.com> wrote:
> On Wed, Oct 25, 2017 at 02:07:38PM -0700, Andrei Vagin wrote:
>> Hi Josh,
>>
>> Here is one more warning:
>> [ 5.852094] WARNING: can't dereference iret registers at ffffb6ce01b7ffe0 for ip entry_SYSCALL_64_fastpath+0xa/0xc2
>
> Thanks, I hadn't seen this one yet.
>
> I suspect this is in the middle of the ENABLE_INTERRUPTS() paravirt
> code, which would mean this is another issue that will be fixed by my
> "Make pv ops code generation more closely match reality" patches.
>
> If you can share either the entry_64.o file or the .config, and what
> virt platform it's running on (kvm, xen, native), I should be able to
> confirm the issue.
>
> I'm in Prague this week but I should have a v2 of those patches in a
> week or two (will cc you).
Do you have any news? We still see this warning in the kernel log. Thanks!
>
> --
> Josh
Powered by blists - more mailing lists