Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2634911imu; Sun, 23 Dec 2018 04:27:43 -0800 (PST) X-Google-Smtp-Source: AFSGD/ViomqDe/t80tP63Irx6FOS7pv0FKae0oAlZdbarW7RMu2arYECw2+yu6NdDUp2MFt+x2Mm X-Received: by 2002:a62:5884:: with SMTP id m126mr9515728pfb.177.1545568063233; Sun, 23 Dec 2018 04:27:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1545568063; cv=none; d=google.com; s=arc-20160816; b=FrutEmScRLeMPldW/xSpOcVjIEfHZLOQOYbG48jioDvZGGDpKdfOOhcWtGUS+RS+44 7FMlkIOqZGjKiVVtHr6yZOiIVE27M4BUe0SuOKm4CvUXUxMVOnhGFCT57jrGuy9ELzyb dhs/hriHhAoaf5uZgG+BUBnqUVViOV36d3BmpcUQugK943dHqJ/+Q1jYnw/IAB6JN8vm 4Fedj9kH6ds+ukVqJtdcLV5v/uRmKydmkGiP8OxCZO2CouIWqTvg3FIsO+N6OZmKZdF8 9RBxWBhfNTJU175CM2QVreo+j8X+BAV1/mswTlFjpOpEmb8qg+015kF2PfQzSZsCsAIT oorA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date:dkim-signature; bh=tPIyQKEhD8jSuYym3JA98vimnD2uHKo0PyBvCttAp70=; b=qIPXcRh+hFWilj16dQLkyqoBExHRBOpjzd1APkDZP6MoBkWXXvBv8ZkA9uZpXj6W/2 DatldAFK6OpM5zGC/xJRBxL25FofG7jIpWmeu0En5p8ormDDrTrcvAgTEZidGNur1Phv vTF/eJ7CH7kkAb1m3rPOLjxJBFSgi9ZTj8yc4x9B64DVo3mYp8HFp7JLI48khnW8Guxl 1kpYvjdqfAxQjoqlQQ8vqDF9YjFRHTGq1x66kikRpOJrUVIpqXYvOvCo/jj/5raHQHcF iwGhifNKFhSaM+4gjPHVpG3hrwpz+yEvJg1a0KBQiF4yLjGnBQH/WgsJuxmWXGab+HEQ T3sQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=M67B5Mqm; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p127si26700250pfp.119.2018.12.23.04.26.49; Sun, 23 Dec 2018 04:27:43 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=M67B5Mqm; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2392034AbeLUV6m (ORCPT + 99 others); Fri, 21 Dec 2018 16:58:42 -0500 Received: from mail-pg1-f194.google.com ([209.85.215.194]:38444 "EHLO mail-pg1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725837AbeLUV6m (ORCPT ); Fri, 21 Dec 2018 16:58:42 -0500 Received: by mail-pg1-f194.google.com with SMTP id g189so3063277pgc.5 for ; Fri, 21 Dec 2018 13:58:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=date:from:to:cc:subject:in-reply-to:message-id:references :user-agent:mime-version; bh=tPIyQKEhD8jSuYym3JA98vimnD2uHKo0PyBvCttAp70=; b=M67B5Mqm948rD0LRf4ZPMVo+xHTg+EuImBkQtlQ06jbb08eViauzP/ayOcFgEL69Ms NT3otIX7hQlTC4vEvmuKVEi0iOeZXoGYZKpZHfywWwDrLxAUnbckPbgNoF0/aJXetfLI j48W6ffx/M8XbIrKlqCxAbP1eQQ4jrSIp79tPeZ2I8erPdlG0BuX7P2uwpgJGlhABIpg KsJPbwmc/IhAnPgZ8FUuJ4vqsBBNuc2tOqr4gY7Dx9kUfT7hrIuPqRDsZ/7dyFTM9/m0 ZMf0ttwPZ34U61YBKsyZPE1bKnhQwa2cFfKNukyzHihQZ2cdsHyfrCT0ma6+R1x/Lb94 dN1g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:in-reply-to:message-id :references:user-agent:mime-version; bh=tPIyQKEhD8jSuYym3JA98vimnD2uHKo0PyBvCttAp70=; b=Rz1EJwyL5sm8hCoq24YZI4aKT2zY2eBXUPs45XSFDbET6ELKmzcck299skQ+JYudc8 iI6j0zhVve0nZW/I0OaR+XqS1frsy/q2an5/fqJhXhbul4I1upZsZbjIYhL54qwbNSJ4 TCAHEDQxbRg0FeyMAbrrYXiY2YZPnQWtWvik+zDI1W1njBW0Hkb/QArjFnsJSC0Ai1Tf 6UmS1tl/u/3TMW2OH0WgCOFyAv2Z1RNqdewj8UdetD+YQW2XoyCFaiQQxK7JPn0UswYv rCWow9Xh2oCr8SeoJpbj3im6yR8jJA4u9T8j+75aIBwHvSjy/F4gmz3DLAHGfZrsOL1a 2dgA== X-Gm-Message-State: AJcUukcQh1Y8gRjXFW8PgV54jUIPh3Wm1TtB7O4m/42qSVXul/79DsBW 1DKpZbQmcvEsU3B3yL5sIcsA7A== X-Received: by 2002:a63:e445:: with SMTP id i5mr3999567pgk.307.1545429521165; Fri, 21 Dec 2018 13:58:41 -0800 (PST) Received: from [2620:15c:17:3:3a5:23a7:5e32:4598] ([2620:15c:17:3:3a5:23a7:5e32:4598]) by smtp.gmail.com with ESMTPSA id 7sm82600646pfm.8.2018.12.21.13.58.40 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 21 Dec 2018 13:58:40 -0800 (PST) Date: Fri, 21 Dec 2018 13:58:39 -0800 (PST) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Nicholas Mc Guire cc: Andrew Morton , Chintan Pandya , Michal Hocko , Andrey Ryabinin , Arun KS , Joe Perches , "Luis R. Rodriguez" , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH RFC] mm: vmalloc: do not allow kzalloc to fail In-Reply-To: <1545337437-673-1-git-send-email-hofrat@osadl.org> Message-ID: References: <1545337437-673-1-git-send-email-hofrat@osadl.org> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 20 Dec 2018, Nicholas Mc Guire wrote: > diff --git a/mm/vmalloc.c b/mm/vmalloc.c > index 871e41c..1c118d7 100644 > --- a/mm/vmalloc.c > +++ b/mm/vmalloc.c > @@ -1258,7 +1258,7 @@ void __init vmalloc_init(void) > > /* Import existing vmlist entries. */ > for (tmp = vmlist; tmp; tmp = tmp->next) { > - va = kzalloc(sizeof(struct vmap_area), GFP_NOWAIT); > + va = kzalloc(sizeof(*va), GFP_NOWAIT | __GFP_NOFAIL); > va->flags = VM_VM_AREA; > va->va_start = (unsigned long)tmp->addr; > va->va_end = va->va_start + tmp->size; Hi Nicholas, You're right that this looks wrong because there's no guarantee that va is actually non-NULL. __GFP_NOFAIL won't help in init, unfortunately, since we're not giving the page allocator a chance to reclaim so this would likely just end up looping forever instead of crashing with a NULL pointer dereference, which would actually be the better result. You could do BUG_ON(!va); to make it obvious why we crashed, however. It makes it obvious that the crash is intentional rather than some error in the kernel code.