From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Andrei Vagin <avagin@virtuozzo.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@kernel.org>,
torvalds@linux-foundation.org, peterz@infradead.org,
hpa@zytor.com, tglx@linutronix.de,
Andy Lutomirski <luto@kernel.org>
Subject: Re: [PATCH 1/3] x86/entry: Fix idtentry unwind hint
Date: Thu, 26 Oct 2017 10:24:29 -0500 [thread overview]
Message-ID: <20171026152429.77dkjuwwsocou54t@treble> (raw)
In-Reply-To: <20171025210737.GA16091@outlook.office365.com>
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).
--
Josh
next prev parent reply other threads:[~2017-10-26 15:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 16:21 Josh Poimboeuf
2017-10-20 16:21 ` [PATCH 2/3] x86/unwind: Show function name+offset in ORC error messages Josh Poimboeuf
2017-10-23 12:44 ` [tip:x86/asm] " tip-bot for Josh Poimboeuf
2017-10-20 16:21 ` [PATCH 3/3] x86/asm: Don't use the confusing '.ifeq' directive Josh Poimboeuf
2017-10-23 12:44 ` [tip:x86/asm] " tip-bot for Josh Poimboeuf
2017-10-23 12:43 ` [tip:x86/asm] x86/entry: Fix idtentry unwind hint tip-bot for Josh Poimboeuf
2017-10-25 21:07 ` [PATCH 1/3] " Andrei Vagin
2017-10-26 15:24 ` Josh Poimboeuf [this message]
2017-10-26 16:42 ` Andrei Vagin
2017-11-13 22:06 ` Andrei Vagin
2017-11-13 22:59 ` Josh Poimboeuf
[not found] ` <AM4PR08MB07393706B7D76768D4817AC2CF0C0@AM4PR08MB0739.eurprd08.prod.outlook.com>
2017-12-20 6:34 ` Josh Poimboeuf
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=20171026152429.77dkjuwwsocou54t@treble \
--to=jpoimboe@redhat.com \
--cc=avagin@virtuozzo.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®