The patch titled Subject: mm/memblock: fix potential issue in memblock_search_pfn_nid() has been removed from the -mm tree. Its filename was mm-memblock-fix-potential-issue-in-memblock_search_pfn_nid.patch

This patch was dropped because it was nacked

------------------------------------------------------ From: Wei Yang richard.weiyang@gmail.com Subject: mm/memblock: fix potential issue in memblock_search_pfn_nid()

memblock_search_pfn_nid() returns the nid and the [start|end]_pfn of the memory region where pfn sits in. While the calculation of start_pfn has potential issue when the regions base is not page aligned.

For example, we assume PAGE_SHIFT is 12 and base is 0x1234. Current implementation would return 1 while this is not correct.

This patch fixes this by using PFN_UP().

The original commit is commit e76b63f80d93 ("memblock, numa: binary search node id") and merged in v3.12.

Link: http://lkml.kernel.org/r/20180330033055.22340-1-richard.weiyang@gmail.com Fixes: e76b63f80d93 ("memblock, numa: binary search node id") Signed-off-by: Wei Yang richard.weiyang@gmail.com Cc: Michal Hocko mhocko@suse.com Cc: Yinghai Lu yinghai@kernel.org Cc: Jia He hejianet@gmail.com Cc: stable@vger.kernel.org [3.12+] Signed-off-by: Andrew Morton akpm@linux-foundation.org ---

mm/memblock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

diff -puN mm/memblock.c~mm-memblock-fix-potential-issue-in-memblock_search_pfn_nid mm/memblock.c --- a/mm/memblock.c~mm-memblock-fix-potential-issue-in-memblock_search_pfn_nid +++ a/mm/memblock.c @@ -1646,7 +1646,7 @@ int __init_memblock memblock_search_pfn_ if (mid == -1) return -1;

- *start_pfn = PFN_DOWN(type->regions[mid].base); + *start_pfn = PFN_UP(type->regions[mid].base); *end_pfn = PFN_DOWN(type->regions[mid].base + type->regions[mid].size);

return type->regions[mid].nid; _

Patches currently in -mm which might be from richard.weiyang@gmail.com are

mm-check-__highest_present_sectioin_nr-directly-in-memory_dev_init.patch