From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ed1-f71.google.com (mail-ed1-f71.google.com [209.85.208.71]) by kanga.kvack.org (Postfix) with ESMTP id A18A06B0003 for ; Thu, 2 Aug 2018 03:31:51 -0400 (EDT) Received: by mail-ed1-f71.google.com with SMTP id v26-v6so503422eds.9 for ; Thu, 02 Aug 2018 00:31:51 -0700 (PDT) Received: from mx1.suse.de (mx2.suse.de. [195.135.220.15]) by mx.google.com with ESMTPS id j4-v6si825166edl.323.2018.08.02.00.31.49 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Aug 2018 00:31:49 -0700 (PDT) Date: Thu, 2 Aug 2018 09:31:47 +0200 From: Michal Hocko Subject: Re: [RFC 2/2] mm: harden alloc_pages code paths against bogus nodes Message-ID: <20180802073147.GA10808@dhcp22.suse.cz> References: <20180801200418.1325826-1-jeremy.linton@arm.com> <20180801200418.1325826-3-jeremy.linton@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180801200418.1325826-3-jeremy.linton@arm.com> Sender: owner-linux-mm@kvack.org List-ID: To: Jeremy Linton Cc: linux-mm@kvack.org, cl@linux.com, penberg@kernel.org, rientjes@google.com, iamjoonsoo.kim@lge.com, akpm@linux-foundation.org, vbabka@suse.cz, Punit.Agrawal@arm.com, Lorenzo.Pieralisi@arm.com, linux-arm-kernel@lists.infradead.org, bhelgaas@google.com, linux-kernel@vger.kernel.org On Wed 01-08-18 15:04:18, Jeremy Linton wrote: > Its possible to crash __alloc_pages_nodemask by passing it > bogus node ids. This is caused by NODE_DATA() returning null > (hopefully) when the requested node is offline. We can > harded against the basic case of a mostly valid node, that > isn't online by checking for null and failing prepare_alloc_pages. > > But this then suggests we should also harden NODE_DATA() like this > > #define NODE_DATA(nid) ( (nid) < MAX_NUMNODES ? node_data[(nid)] : NULL) > > eventually this starts to add a bunch of generally uneeded checks > in some code paths that are called quite frequently. But the page allocator is really a hot path and people will not be happy to have yet another branch there. No code should really use invalid numa node ids in the first place. If I remember those bugs correctly then it was the arch code which was doing something wrong. I would prefer that code to be fixed instead. > Signed-off-by: Jeremy Linton > --- > include/linux/gfp.h | 2 ++ > mm/page_alloc.c | 2 ++ > 2 files changed, 4 insertions(+) > > diff --git a/include/linux/gfp.h b/include/linux/gfp.h > index a6afcec53795..17d70271c42e 100644 > --- a/include/linux/gfp.h > +++ b/include/linux/gfp.h > @@ -436,6 +436,8 @@ static inline int gfp_zonelist(gfp_t flags) > */ > static inline struct zonelist *node_zonelist(int nid, gfp_t flags) > { > + if (unlikely(!NODE_DATA(nid))) //VM_WARN_ON? > + return NULL; > return NODE_DATA(nid)->node_zonelists + gfp_zonelist(flags); > } > > diff --git a/mm/page_alloc.c b/mm/page_alloc.c > index a790ef4be74e..3a3d9ac2662a 100644 > --- a/mm/page_alloc.c > +++ b/mm/page_alloc.c > @@ -4306,6 +4306,8 @@ static inline bool prepare_alloc_pages(gfp_t gfp_mask, unsigned int order, > { > ac->high_zoneidx = gfp_zone(gfp_mask); > ac->zonelist = node_zonelist(preferred_nid, gfp_mask); > + if (!ac->zonelist) > + return false; > ac->nodemask = nodemask; > ac->migratetype = gfpflags_to_migratetype(gfp_mask); > > -- > 2.14.3 > -- Michal Hocko SUSE Labs