linux-kernel - Re: [Patch v2] mm/sparse: only sub-section aligned range would be populated

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

Message-ID: <20200806095912.GA97074@L-31X9LVDL-1304.local>
Date:   Thu, 6 Aug 2020 17:59:12 +0800
From:   Wei Yang <richard.weiyang@...ux.alibaba.com>
To:     David Hildenbrand <david@...hat.com>
Cc:     Wei Yang <richard.weiyang@...il.com>,
        Wei Yang <richard.weiyang@...ux.alibaba.com>,
        akpm@...ux-foundation.org, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org
Subject: Re: [Patch v2] mm/sparse: only sub-section aligned range would be
 populated

On Thu, Aug 06, 2020 at 09:29:36AM +0200, David Hildenbrand wrote:
>On 05.08.20 23:49, Wei Yang wrote:
>> On Fri, Jul 03, 2020 at 11:18:28AM +0800, Wei Yang wrote:
>>> There are two code path which invoke __populate_section_memmap()
>>>
>>>  * sparse_init_nid()
>>>  * sparse_add_section()
>>>
>>> For both case, we are sure the memory range is sub-section aligned.
>>>
>>>  * we pass PAGES_PER_SECTION to sparse_init_nid()
>>>  * we check range by check_pfn_span() before calling
>>>    sparse_add_section()
>>>
>>> Also, the counterpart of __populate_section_memmap(), we don't do such
>>> calculation and check since the range is checked by check_pfn_span() in
>>> __remove_pages().
>>>
>>> Clear the calculation and check to keep it simple and comply with its
>>> counterpart.
>>>
>>> Signed-off-by: Wei Yang <richard.weiyang@...ux.alibaba.com>
>>>
>> 
>> Hi, Andrew,
>> 
>> Is this one picked up?
>
>I can spot it in -next via the -mm tree:
>
>https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=68ad9becb23be14622e39ed36e5b0621a90a41d9
>

Thanks ;-)

Next time I would refer to this repo first.

>
>-- 
>Thanks,
>
>David / dhildenb

-- 
Wei Yang
Help you, Help me