linux-kernel - Re: [GIT pull] timer updates for 4.19

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] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.21.1808271032330.1631@nanos.tec.linutronix.de>
Date:   Mon, 27 Aug 2018 10:34:01 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Arnd Bergmann <arnd@...db.de>
cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...nel.org>, Christoph Hellwig <hch@....de>
Subject: Re: [GIT pull] timer updates for 4.19

On Mon, 27 Aug 2018, Arnd Bergmann wrote:
> Only a handful of syscalls actually require that complexity, most of them
> need only two entry points either way (32-bit time, and 64-bit time), the
> question is what we call them. I have a mild preference for the second
> version after the discussion with Christoph, but I'm also fine with going back
> to the orignal plan if you like that better after all.

Nah, lets use that old_ naming scheme for the existing 32bit time mess and
use compat for everything which is truly compat in the sense of 32bit on
64bit.

Thanks,

	tglx