From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.3 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 914ACC2D0E5 for ; Thu, 26 Mar 2020 22:12:43 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5FF242078C for ; Thu, 26 Mar 2020 22:12:43 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="VZKU2EoS" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726281AbgCZWMl (ORCPT ); Thu, 26 Mar 2020 18:12:41 -0400 Received: from mail-wm1-f67.google.com ([209.85.128.67]:35449 "EHLO mail-wm1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726260AbgCZWMl (ORCPT ); Thu, 26 Mar 2020 18:12:41 -0400 Received: by mail-wm1-f67.google.com with SMTP id m3so9856886wmi.0; Thu, 26 Mar 2020 15:12:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-disposition:in-reply-to:user-agent; bh=XV8ONxrhzLm1XRXAjklwNAD/3fXBeH2tcYtEjG9QsSY=; b=VZKU2EoSY8ifMMoVJmBY3z5r8LkOjG1oNvQZZUNdXTAjo6+/rbR+N3AhkJwd8B+m4e 9sleYSqmzyPDtmd1MeTgwKf3VE8rN2qLPUpc5+SiaWOfPhjifQ2stsCJ8p4Qb3lQ7JQj aACSd1WRQTwVEcwb8etKAq1hCr/+NohylSJoSGQukTfP5R770VjV4bBlHYcjUgEqwamX j9q483MQjuIg4kYAmLz36XSg7EIWchn66kA0R9c7O3XWO7E+NQBKsm2blO0aB3H/mqOi z6YKwPOHp/urIF3lcl+MaT768OZDjCIPbOUwtGvPa7DiQ38WnNyia80ysHOmYbPxdLPo ZIbQ== 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:message-id:reply-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=XV8ONxrhzLm1XRXAjklwNAD/3fXBeH2tcYtEjG9QsSY=; b=VMqr9YqIRXvr78LB2ZsW3Bhp/PxgIwBQrR/Vab82dF1tGa1WOS9XrlCQHSho3/ngyf IxslwoWjnhilFDmtSSvWFt5crkMS2AHUvPwvnRPz3rpq8yOSVbl/S1OIf/vGiZLVQNEh mQRXQW/O4/TdcW8I5X0y7jPreADyVY8XTCxe/KRew3dVtkvq8WlYy45GppjXL3tLKOht 0lpR5Zf7pJ4EeXDUdCS9eeqAnOLtgugkXR87/Ni81Hx14dDAnJXCf7/QWylJR0iL11Fx mEMmQgab0bNhjeEAkH/jo7iV98y57r1c/kWmWC3eRrG+hCWO+M53zjNIYBUZ+iO9HKOa FkOA== X-Gm-Message-State: ANhLgQ2wvV3z54cFNyims3hbwRaXDt9DekEB6XhSWBczrgENXdCLG/s5 UEO3/qAMaaPidAUeGk/8+bc= X-Google-Smtp-Source: ADFU+vt6ZLuyioBcFjmo9C2azZJw71RH9CqKsiPptR5/A2XORNRp5r6KHCHmmVX7iu5aUcM/sO7bzA== X-Received: by 2002:a1c:b105:: with SMTP id a5mr2007926wmf.57.1585260759713; Thu, 26 Mar 2020 15:12:39 -0700 (PDT) Received: from localhost ([185.92.221.13]) by smtp.gmail.com with ESMTPSA id 195sm5500455wmb.8.2020.03.26.15.12.38 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 26 Mar 2020 15:12:38 -0700 (PDT) Date: Thu, 26 Mar 2020 22:12:37 +0000 From: Wei Yang To: "Aneesh Kumar K.V" Cc: linux-mm@kvack.org, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org, Sachin Sant , Baoquan He , Dan Williams , Pankaj Gupta , David Hildenbrand , Michal Hocko , Wei Yang , Oscar Salvador , Mike Rapoport , stable@vger.kernel.org Subject: Re: [PATCH v2] mm/sparse: Fix kernel crash with pfn_section_valid check Message-ID: <20200326221237.fttur7yyfl7nrdsj@master> Reply-To: Wei Yang References: <20200326133235.343616-1-aneesh.kumar@linux.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200326133235.343616-1-aneesh.kumar@linux.ibm.com> User-Agent: NeoMutt/20170113 (1.7.2) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Thu, Mar 26, 2020 at 07:02:35PM +0530, Aneesh Kumar K.V wrote: >Fixes the below crash > >BUG: Kernel NULL pointer dereference on read at 0x00000000 >Faulting instruction address: 0xc000000000c3447c >Oops: Kernel access of bad area, sig: 11 [#1] >LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries >CPU: 11 PID: 7519 Comm: lt-ndctl Not tainted 5.6.0-rc7-autotest #1 >... >NIP [c000000000c3447c] vmemmap_populated+0x98/0xc0 >LR [c000000000088354] vmemmap_free+0x144/0x320 >Call Trace: > section_deactivate+0x220/0x240 > __remove_pages+0x118/0x170 > arch_remove_memory+0x3c/0x150 > memunmap_pages+0x1cc/0x2f0 > devm_action_release+0x30/0x50 > release_nodes+0x2f8/0x3e0 > device_release_driver_internal+0x168/0x270 > unbind_store+0x130/0x170 > drv_attr_store+0x44/0x60 > sysfs_kf_write+0x68/0x80 > kernfs_fop_write+0x100/0x290 > __vfs_write+0x3c/0x70 > vfs_write+0xcc/0x240 > ksys_write+0x7c/0x140 > system_call+0x5c/0x68 > >The crash is due to NULL dereference at > >test_bit(idx, ms->usage->subsection_map); due to ms->usage = NULL; in pfn_section_valid() > >With commit: d41e2f3bd546 ("mm/hotplug: fix hot remove failure in SPARSEMEM|!VMEMMAP case") >section_mem_map is set to NULL after depopulate_section_mem(). This >was done so that pfn_page() can work correctly with kernel config that disables >SPARSEMEM_VMEMMAP. With that config pfn_to_page does > > __section_mem_map_addr(__sec) + __pfn; >where > >static inline struct page *__section_mem_map_addr(struct mem_section *section) >{ > unsigned long map = section->section_mem_map; > map &= SECTION_MAP_MASK; > return (struct page *)map; >} > >Now with SPASEMEM_VMEMAP enabled, mem_section->usage->subsection_map is used to >check the pfn validity (pfn_valid()). Since section_deactivate release >mem_section->usage if a section is fully deactivated, pfn_valid() check after >a subsection_deactivate cause a kernel crash. > >static inline int pfn_valid(unsigned long pfn) >{ >... > return early_section(ms) || pfn_section_valid(ms, pfn); >} > >where > >static inline int pfn_section_valid(struct mem_section *ms, unsigned long pfn) >{ > int idx = subsection_map_index(pfn); > > return test_bit(idx, ms->usage->subsection_map); >} > >Avoid this by clearing SECTION_HAS_MEM_MAP when mem_section->usage is freed. >For architectures like ppc64 where large pages are used for vmmemap mapping (16MB), >a specific vmemmap mapping can cover multiple sections. Hence before a vmemmap >mapping page can be freed, the kernel needs to make sure there are no valid sections >within that mapping. Clearing the section valid bit before >depopulate_section_memap enables this. > >Fixes: d41e2f3bd546 ("mm/hotplug: fix hot remove failure in SPARSEMEM|!VMEMMAP case") >Reported-by: Sachin Sant >Tested-by: Sachin Sant >Cc: Baoquan He >Cc: Michael Ellerman >Cc: Dan Williams >Cc: Pankaj Gupta >Cc: David Hildenbrand >Cc: Michal Hocko >Cc: Wei Yang >Cc: Oscar Salvador >Cc: Mike Rapoport >Cc: >Signed-off-by: Aneesh Kumar K.V Reviewed-by: Wei Yang -- Wei Yang Help you, Help me