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:   Fri, 7 Dec 2018 18:52:53 +0100
From:   Borislav Petkov <bp@...en8.de>
To:     Nick Desaulniers <ndesaulniers@...gle.com>
Cc:     luto@...nel.org, Fangrui Song <maskray@...gle.com>,
        Andi Kleen <ak@...ux.intel.com>, andi@...stfloor.org,
        Dmitry Golovin <dima@...ovin.in>,
        Bill Wendling <morbo@...gle.com>, Rui Ueyama <ruiu@...gle.com>,
        Thomas Gleixner <tglx@...utronix.de>, mingo@...hat.com,
        hpa@...or.com, x86@...nel.org, LKML <linux-kernel@...r.kernel.org>,
        rafael@...indo.la, Stephen Hines <srhines@...gle.com>,
        Greg KH <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] x86/vdso: drop implicit common-page-size linker flag

On Fri, Dec 07, 2018 at 09:45:42AM -0800, Nick Desaulniers wrote:
> Google's Native Client, a technology for running native code in a web
> browser.  It's since been superseded by Portable Native Client (pNaCl)
> and to an extent Web Assembly.  It seems that BFD still contains code
> for NaCl.

Yeah, found the wikipedia page. :)

> How does this sound:
> TL;DR
> -z common-page-size's default value is based on the target
> architecture.  arch/x86/entry/vdso/Makefile sets it to the
> architecture default, which is implicit and redundant.  Drop it.

Sure. Although the longer explanation gives more insight into the whole
deal but that's fine too - the longer explanation is on the ML and we
have the Link: tags.

So no need to resend - I'll simply take the three-liner above.

Thx.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

Powered by blists - more mailing lists