[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190923111745.GG15392@bombadil.infradead.org>
Date: Mon, 23 Sep 2019 04:17:45 -0700
From: Matthew Wilcox <willy@...radead.org>
To: Anshuman Khandual <anshuman.khandual@....com>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, akpm@...ux-foundation.org,
catalin.marinas@....com, will@...nel.org, mark.rutland@....com,
mhocko@...e.com, david@...hat.com, cai@....pw, logang@...tatee.com,
cpandya@...eaurora.org, arunks@...eaurora.org,
dan.j.williams@...el.com, mgorman@...hsingularity.net,
osalvador@...e.de, ard.biesheuvel@....com, steve.capper@....com,
broonie@...nel.org, valentin.schneider@....com,
Robin.Murphy@....com, steven.price@....com, suzuki.poulose@....com,
ira.weiny@...el.com
Subject: Re: [PATCH V8 2/2] arm64/mm: Enable memory hot remove
On Mon, Sep 23, 2019 at 11:13:45AM +0530, Anshuman Khandual wrote:
> +#ifdef CONFIG_MEMORY_HOTPLUG
> +static void free_hotplug_page_range(struct page *page, size_t size)
> +{
> + WARN_ON(!page || PageReserved(page));
WARN_ON(!page) isn't terribly useful. You're going to crash on the very
next line when you call page_address() anyway. If this line were
if (WARN_ON(!page || PageReserved(page)))
return;
it would make sense, or if it were just
WARN_ON(PageReserved(page))
it would also make sense.
> + free_pages((unsigned long)page_address(page), get_order(size));
> +}
Powered by blists - more mailing lists