linux-kernel - Re: [PATCH 1/3] x86/entry: Fix idtentry unwind hint

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 26 Oct 2017 09:42:28 -0700
From:   Andrei Vagin <avagin@...tuozzo.com>
To:     Josh Poimboeuf <jpoimboe@...hat.com>
Cc:     x86@...nel.org, linux-kernel@...r.kernel.org,
        Ingo Molnar <mingo@...nel.org>, torvalds@...ux-foundation.org,
        peterz@...radead.org, hpa@...or.com, tglx@...utronix.de,
        Andy Lutomirski <luto@...nel.org>
Subject: Re: [PATCH 1/3] x86/entry: Fix idtentry unwind hint

On Thu, Oct 26, 2017 at 10:24:29AM -0500, 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.

The config is attached to this e-mail. It is a travis-ci vm. I think
they are hosted in Google Cloud:

[    0.000000] DMI: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
[    0.000000] Hypervisor detected: KVM

https://travis-ci.org/avagin/linux/jobs/292773933

> 
> I'm in Prague this week but I should have a v2 of those patches in a
> week or two (will cc you).

Good!

> 
> -- 
> Josh