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, 25 Jan 2018 10:52:53 +0000
From:   David Woodhouse <dwmw2@...radead.org>
To:     Juergen Gross <jgross@...e.com>,
        Peter Zijlstra <peterz@...radead.org>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Josh Poimboeuf <jpoimboe@...hat.com>,
        linux-kernel@...r.kernel.org, Dave Hansen <dave.hansen@...el.com>,
        Ashok Raj <ashok.raj@...el.com>,
        Tim Chen <tim.c.chen@...ux.intel.com>,
        Andy Lutomirski <luto@...nel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Greg KH <gregkh@...uxfoundation.org>,
        Andrea Arcangeli <aarcange@...hat.com>,
        Andi Kleen <ak@...ux.intel.com>,
        Arjan Van De Ven <arjan.van.de.ven@...el.com>,
        Dan Williams <dan.j.williams@...el.com>,
        Paolo Bonzini <pbonzini@...hat.com>,
        Jun Nakajima <jun.nakajima@...el.com>,
        Asit Mallick <asit.k.mallick@...el.com>,
        Jason Baron <jbaron@...mai.com>
Subject: Re: [PATCH 03/24] x86/paravirt: Annotate indirect calls

On Thu, 2018-01-25 at 11:26 +0100, Juergen Gross wrote:
> On 25/01/18 11:22, Peter Zijlstra wrote:
> > 
> > On Thu, Jan 25, 2018 at 10:02:05AM +0000, David Woodhouse wrote:
> > > 
> > > On Tue, 2018-01-23 at 16:25 +0100, Peter Zijlstra wrote:
> > > > 
> > > > Paravirt emits indirect calls which get flagged by objtool retpoline
> > > > checks, annotate it away because all these indirect calls will be
> > > > patched out before we start userspace.
> > > I've seen this asserted repeatedly but I've never truly convinced
> > > myself of it. Is this absolutely unconditionally true in every case,
> > > even when we're running as a guest and there are *actual* calls to be
> > > made? We turn them into direct calls, never leave them indirect?
> > That is my understanding; and when I worked on the paravirt spinlock
> > code and disassembled live guest code this seemed to have happend.
> > 
> > But let me go read the paravirt code again to make a stronger argument
> > in favour.
> > 
> paravirt_patch_default() is the function you want to look at: it either
> replaces the indirect call by some cutom code (which is never an
> indirect call) or by a call of the target function.

OK, my brain hurts a bit but I'm happy now. Thank you.
Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (5213 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ