From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753229AbdKMW7r (ORCPT ); Mon, 13 Nov 2017 17:59:47 -0500 Received: from mx1.redhat.com ([209.132.183.28]:55300 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752719AbdKMW7q (ORCPT ); Mon, 13 Nov 2017 17:59:46 -0500 Date: Mon, 13 Nov 2017 16:59:44 -0600 From: Josh Poimboeuf To: Andrei Vagin Cc: Andrei Vagin , X86 ML , LKML , Ingo Molnar , Linus Torvalds , Peter Zijlstra , "H. Peter Anvin" , Thomas Gleixner , Andy Lutomirski Subject: Re: [PATCH 1/3] x86/entry: Fix idtentry unwind hint Message-ID: <20171113225944.me36msnvq4clhleh@treble> References: <931d57f0551ed7979d5e7e05370d445c8e5137f8.1508516398.git.jpoimboe@redhat.com> <20171025210737.GA16091@outlook.office365.com> <20171026152429.77dkjuwwsocou54t@treble> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0.1 (2016-04-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.39]); Mon, 13 Nov 2017 22:59:46 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 13, 2017 at 02:06:35PM -0800, Andrei Vagin wrote: > Hi Josh, > > On Thu, Oct 26, 2017 at 8:24 AM, Josh Poimboeuf 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! Sorry, a bunch of other work got in the way. I haven't forgotten about it. It's now (almost) at the top of my TODO list. -- Josh