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  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]
Date:   Tue, 12 Jan 2021 11:09:34 +0100
From:   David Hildenbrand <>
To:     Anshuman Khandual <>,
        Oscar Salvador <>
        Vasily Gorbik <>,
        Will Deacon <>,
        Ard Biesheuvel <>,
        Mark Rutland <>
Subject: Re: [PATCH V2 1/3] mm/hotplug: Prevalidate the address range being
 added with platform

On 12.01.21 04:51, Anshuman Khandual wrote:
> On 1/11/21 7:13 PM, Oscar Salvador wrote:
>> On Mon, Jan 11, 2021 at 11:51:47AM +0100, David Hildenbrand wrote:
>>> AFAIKs, all memhp_get_pluggable_range() users pass "1".
>>> What about the "add_pages()-only" path?
>> I guess you refer to memremap_pages(), right?
> Right, via pagemap_range().
>> If so, moving the added memhp_range_allowed() check above the if-else might do
>> the trick
> We had that code in the earlier version. But dropped it, as we did
> not want to add any new checks in the generic code. Can add it back
> if that is preferred.

I remember discussing replacing the check in __add_pages() instead. But
I don't really care where the check ends up being. As discussed, at some
point, we should provide versions of add_pages() and arch_add_pages()
that don't immediately end in arch-code.


David / dhildenb

Powered by blists - more mailing lists