Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp2026839ybi; Mon, 1 Jul 2019 04:57:13 -0700 (PDT) X-Google-Smtp-Source: APXvYqwj8ZDSWxgmCewKH8Xp3YfVdh3QAOVZmoVHrHo+V6DIP2DglbnerGOLCEezN7hq2uZ9PISi X-Received: by 2002:a17:902:42a5:: with SMTP id h34mr29667756pld.16.1561982233070; Mon, 01 Jul 2019 04:57:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561982233; cv=none; d=google.com; s=arc-20160816; b=iDuHorurgjQ+MAqKcZft1hlpL+54iwteDUAqZp1qTXmB23eTAXqEVkGDfXn2FKztNF o0B5XS2MehnDXCIZ54Gf36R31zHVRuXH/p7Rp3SN7crZE7obREIV5/nYISoTjK2hS1dP wLZH6mUlZZEfKa7Pd6epHbAidqXoj/dt6ZgFi5BdZsKoOnAaVNdCCtnH0Ds/z9VXTzY/ noau69U14gAlR7gM3LEr7jKoaRGRYiR/HaKu9PKUFrEqvlkEGahtJNF8BRqEOpNOfwEL IE/AnV/6UPy11rn84KwGjadvvUzLlDtUYmR6iEnGsPkQ5PiJl8zCBqGJG0iW0t59mblX R6DQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=uGdDddJBdJpBa1UkXgnQ/Zcc02heFyJUY26VzUcvXV4=; b=A90GQlAhQ4phTU4kddeMlQfRCj4C5PGHhiHvD90jdKZndIdGCnjfXcV/6PAgarcxlN leI/x6q/TVYO75xAtKmyE/gXAFE4eDghXf0HuuDjku1DA2fHiHUrsnW3B0f/1Ac3jE8C cC92jgDs8FnI8oTHMoE5HBoFg7+DF3ys+lf6eilDcAYDuSTrjuGbOgao7TjvcSUsklrG wKYuwqbzRFeIzNheF9XAW6ewXKhvcgb4MtnWwpEIhaUTdVjOW1KSjwWmQ/QDdtoBM3Xz NKVX+L7H5fhBK0jKeIcMMyOVwd+myaksaH2/HqoINY2NgcvN7AQP8cz8YVtKB4o5uMbp azWw== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id cj14si10086236plb.141.2019.07.01.04.56.57; Mon, 01 Jul 2019 04:57:13 -0700 (PDT) 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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727813AbfGAKrB (ORCPT + 99 others); Mon, 1 Jul 2019 06:47:01 -0400 Received: from mx2.suse.de ([195.135.220.15]:43316 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727041AbfGAKrA (ORCPT ); Mon, 1 Jul 2019 06:47:00 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 972EBAD8D; Mon, 1 Jul 2019 10:46:59 +0000 (UTC) Date: Mon, 1 Jul 2019 12:46:58 +0200 From: Michal Hocko To: Alastair D'Silva Cc: Greg Kroah-Hartman , "Rafael J. Wysocki" , Andrew Morton , Pavel Tatashin , Oscar Salvador , Mike Rapoport , Baoquan He , Wei Yang , Logan Gunthorpe , linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH v2 1/3] mm: Trigger bug on if a section is not found in __section_nr Message-ID: <20190701104658.GA6549@dhcp22.suse.cz> References: <20190626061124.16013-1-alastair@au1.ibm.com> <20190626061124.16013-2-alastair@au1.ibm.com> <20190626062113.GF17798@dhcp22.suse.cz> <20190626065751.GK17798@dhcp22.suse.cz> <20190627080724.GK17798@dhcp22.suse.cz> <833b9675bc363342827cb8f7c76ebb911f7f960d.camel@d-silva.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <833b9675bc363342827cb8f7c76ebb911f7f960d.camel@d-silva.org> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 28-06-19 10:46:28, Alastair D'Silva wrote: [...] > Given that there is already a VM_BUG_ON in the code, how do you feel > about broadening the scope from 'VM_BUG_ON(!root)' to 'VM_BUG_ON(!root > || (root_nr == NR_SECTION_ROOTS))'? As far as I understand the existing VM_BUG_ON will hit when the mem_section tree gets corrupted. This is a different situation to an incorrect section given so I wouldn't really mix those two. And I still do not see much point to protect from unexpected input parameter as this is internal function as already pointed out. -- Michal Hocko SUSE Labs