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  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, 23 Nov 2017 07:58:28 +0100
From:   Ingo Molnar <>
To:     Andy Lutomirski <>
Cc:     Thomas Gleixner <>, X86 ML <>,
        Borislav Petkov <>,
        "" <>,
        Brian Gerst <>,
        Dave Hansen <>,
        Linus Torvalds <>,
        Josh Poimboeuf <>
Subject: Re: [PATCH v2 00/18] Entry stack switching

* Ingo Molnar <> wrote:

> * Ingo Molnar <> wrote:
> > > Anyway, I booted your config (more or less -- I munged it through
> > > virtme-configkernel --update first) with 17 vCPUs and it seems fine.
> > > Is the issue reliable enough to bisect?
> > 
> > Ok, it should be bisectable, will try to bisect it.
> The latestest entry-stack code appears to be working fine though.
> So one of the below fixes from yesterday appears to have done the trick.
> I'll re-test today to make sure: maybe it's more sporadic than I thought, in one 
> of the bootups I got the do_IRQ warning only once, in half a day of uptime.

I re-tested and it all seems fine now. I suspect it got fixed by:

  ca37e57bbe0c: x86/entry/64: Add missing irqflags tracing to native_load_gs_index()

still it is weird, because I boot that system with latest -tip on a daily basis, 
and don't remember having seen that warning.

Do you have any theory for why the entry stack changes would uncover this bug?



Powered by blists - more mailing lists