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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171126173301.hqmnpez6jbjgksys@pd.tnic>
Date:   Sun, 26 Nov 2017 18:33:01 +0100
From:   Borislav Petkov <bp@...en8.de>
To:     Ingo Molnar <mingo@...nel.org>
Cc:     linux-kernel@...r.kernel.org,
        Dave Hansen <dave.hansen@...ux.intel.com>,
        Andy Lutomirski <luto@...capital.net>,
        Thomas Gleixner <tglx@...utronix.de>,
        "H . Peter Anvin" <hpa@...or.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 14/43] x86/asm/64: Return to userspace from the
 trampoline stack

On Sun, Nov 26, 2017 at 03:18:47PM +0100, Ingo Molnar wrote:
> Heh, indeed - if by 'future generations' you mean 'the guys who merge it,
> a few months down the line'. ;-)

... and the poor souls who get to backport it and maybe even the guys
who merged it, get to look at this after some time has passed by and
then all of a sudden, they start scratching heads: "Why TF did we do
that then? What were we thinking?"

It happens even to the best of us. :-)

And entry code is tricky as hell so hell yeah! to all the commenting.

-- 
Regards/Gruss,
    Boris.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ