linux-kernel - Re: [GIT PULL] x86/mm changes for v4.12

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: <20170524062526.bti7xfj3cgi4lk75@gmail.com>
Date:   Wed, 24 May 2017 08:25:26 +0200
From:   Ingo Molnar <mingo@...nel.org>
To:     "Kirill A. Shutemov" <kirill@...temov.name>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
        "H. Peter Anvin" <hpa@...or.com>,
        Peter Zijlstra <a.p.zijlstra@...llo.nl>,
        Andy Lutomirski <luto@...nel.org>,
        Borislav Petkov <bp@...en8.de>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] x86/mm changes for v4.12


* Kirill A. Shutemov <kirill@...temov.name> wrote:

> On Mon, May 01, 2017 at 02:00:53PM +0200, Ingo Molnar wrote:
> >  - Continued Intel 5-level paging enablement: in particular the conversion 
> >    of x86 GUP to the generic GUP code. (Kirill A. Shutemov)
> > 
> ...
> > 
> > I'd like to draw special attention to this late MM commit:
> > 
> >   71389703839e: mm, zone_device: Replace {get, put}_zone_device_page() with a single reference to fix pmem crash
> > 
> > ... which is a late fix, and which I believe is the right thing to do - but please 
> > double check.
> 
> I've just noticied that the x86 GUP conversion haven't made it's way to
> v4.12: the fix got applied (71389703839e), but the final commit that does
> convertion keeped reverted -- 6dd29b3df975.
> 
> I guess it's too late for v4.12...
> 
> Ingo could you re-apply 2947ba054a4d ("x86/mm/gup: Switch GUP to the
> generic get_user_page_fast() implementation") to be queued to v4.13?

There were some late problems and I wanted x86/mm to be regression-free - we don't 
have all the 5-level paging patches applied yet so the exact cut we made at v4.12 
does not matter much - v4.13 is going to be the real deal.

Could you please make the re-application part of the remaining 5-level paging 
patches?

Thanks,

	Ingo