linux-kernel - Re: [PATCH v2 0/2] x86/mm/KASLR: Change the granularity of randomization to PUD size in 5-level

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: <20190304081529.nuneutcjhoa56fw7@kshutemo-mobl1>
Date:   Mon, 4 Mar 2019 11:15:29 +0300
From:   "Kirill A. Shutemov" <kirill@...temov.name>
To:     Baoquan He <bhe@...hat.com>
Cc:     linux-kernel@...r.kernel.org, kirill.shutemov@...ux.intel.com,
        dave.hansen@...ux.intel.com, luto@...nel.org, peterz@...radead.org,
        tglx@...utronix.de, mingo@...hat.com, bp@...en8.de, hpa@...or.com,
        x86@...nel.org, keescook@...omium.org, thgarnie@...gle.com
Subject: Re: [PATCH v2 0/2] x86/mm/KASLR: Change the granularity of
 randomization to PUD size in 5-level

On Fri, Mar 01, 2019 at 10:45:02PM +0800, Baoquan He wrote:
> Hi Kirill,
> 
> I updated patch per your comments. While I kept the 'paddr' variable and
> the '0' initilization stuffs. My thought is there are two kinds of mapping
> in the handling, so keeping these names from old codes can make it more
> understandable. What do you think?
> 
> Kind               Physical address            Virtual address
> ----------------------------------------------------------------
> Direct mapping     paddr                vaddr = paddr+PAGE_OFFSET
> 1:1 mapping        paddr                    paddr

I agree with your logic and patch looks good to me. But maybe you should
exmplain this in the comments too?

Anyway:

Acked-by: Kirill A. Shutemov <kirill.shutemov@...ux.intel.com>

-- 
 Kirill A. Shutemov