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]
Message-ID: <20160828201429.GV19647@uranus>
Date:   Sun, 28 Aug 2016 23:14:29 +0300
From:   Cyrill Gorcunov <gorcunov@...il.com>
To:     Dmitry Safonov <dsafonov@...tuozzo.com>
Cc:     linux-kernel@...r.kernel.org, mingo@...hat.com,
        luto@...capital.net, tglx@...utronix.de, hpa@...or.com,
        x86@...nel.org, 0x7f454c46@...il.com, oleg@...hat.com,
        rostedt@...dmis.org, viro@...iv.linux.org.uk
Subject: Re: [RFC 1/3] x86/vdso: create vdso file, use it for mapping

On Thu, Aug 25, 2016 at 06:21:08PM +0300, Dmitry Safonov wrote:
> I added here a new in-kernel fs with ramfs-like options.
> Created vdso file in this fs (yet for testing, only 64-bit vdso).
> Mapped this file to process's mm on setup_additional_pages.
> Just for testing purpose it's done only for specific UID.
> 
> Signed-off-by: Dmitry Safonov <dsafonov@...tuozzo.com>

Dmitry, could you clarify please, why "old way" remains in the code?
Even if RFC is not the new approach is supposing to completely remove
old one? Or I miss something obvious?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ