linux-kernel - Re: [PATCH V4 1/4] mm/memory_hotplug: Prevalidate the address range being added with platform

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: <a07711a8-f24b-be8d-8570-6447e66768d9@redhat.com>
Date:   Mon, 25 Jan 2021 10:21:41 +0100
From:   David Hildenbrand <david@...hat.com>
To:     Anshuman Khandual <anshuman.khandual@....com>, linux-mm@...ck.org,
        akpm@...ux-foundation.org, hca@...ux.ibm.com,
        catalin.marinas@....com
Cc:     Oscar Salvador <osalvador@...e.de>,
        Vasily Gorbik <gor@...ux.ibm.com>,
        Will Deacon <will@...nel.org>,
        Ard Biesheuvel <ardb@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        linux-arm-kernel@...ts.infradead.org, linux-s390@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH V4 1/4] mm/memory_hotplug: Prevalidate the address range
 being added with platform

On 25.01.21 03:58, Anshuman Khandual wrote:
> This introduces mhp_range_allowed() which can be called in various memory
> hotplug paths to prevalidate the address range which is being added, with
> the platform. Then mhp_range_allowed() calls mhp_get_pluggable_range()
> which provides applicable address range depending on whether linear mapping
> is required or not. For ranges that require linear mapping, it calls a new
> arch callback arch_get_mappable_range() which the platform can override. So
> the new callback, in turn provides the platform an opportunity to configure
> acceptable memory hotplug address ranges in case there are constraints.
> 
> This mechanism will help prevent platform specific errors deep down during
> hotplug calls. This drops now redundant check_hotplug_memory_addressable()
> check in __add_pages() but instead adds a VM_BUG_ON() check which would
> ensure that the range has been validated with mhp_range_allowed() earlier
> in the call chain. Besides mhp_get_pluggable_range() also can be used by
> potential memory hotplug callers to avail the allowed physical range which
> would go through on a given platform.
> 
> This does not really add any new range check in generic memory hotplug but
> instead compensates for lost checks in arch_add_memory() where applicable
> and check_hotplug_memory_addressable(), with unified mhp_range_allowed().
> 
> Cc: David Hildenbrand <david@...hat.com>
> Cc: Andrew Morton <akpm@...ux-foundation.org>
> Cc: linux-mm@...ck.org
> Cc: linux-kernel@...r.kernel.org
> Reviewed-by: Oscar Salvador <osalvador@...e.de>
> Suggested-by: David Hildenbrand <david@...hat.com>
> Signed-off-by: Anshuman Khandual <anshuman.khandual@....com>

[...]

> +
> +struct range mhp_get_pluggable_range(bool need_mapping)
> +{
> +	const u64 max_phys = (1ULL << MAX_PHYSMEM_BITS) - 1;
> +	struct range mhp_range;
> +
> +	if (need_mapping) {
> +		mhp_range = arch_get_mappable_range();
> +		if (mhp_range.start > max_phys) {
> +			mhp_range.start = 0;
> +			mhp_range.end = 0;
> +		}
> +		mhp_range.end = min_t(u64, mhp_range.end, max_phys);
> +	} else {
> +		mhp_range.start = 0;
> +		mhp_range.end = max_phys;
> +	}
> +	return mhp_range;
> +}
> +EXPORT_SYMBOL_GPL(mhp_get_pluggable_range);


Some people might prefer the EXPORT_SYMBOL_GPL() going to the actual
user (patch #4), I don't care :) Thanks!

Reviewed-by: David Hildenbrand <david@...hat.com>

-- 
Thanks,

David / dhildenb