Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp2616848iog; Mon, 20 Jun 2022 00:29:55 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tgJCV7wn0K9i2WaQ693wfrFPcLLbydDKpFCfQr2zoIa8Q1PwTpvXlc0OS3urKUYwf2i3S/ X-Received: by 2002:a17:906:3985:b0:70c:a5fe:d4fb with SMTP id h5-20020a170906398500b0070ca5fed4fbmr20349208eje.127.1655710194842; Mon, 20 Jun 2022 00:29:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1655710194; cv=none; d=google.com; s=arc-20160816; b=LVrTWXk81HqL57gDENMwOut1cshrumAPVeLfL/vSZ5meWyEiulWDWnYkkO8tMhGnq9 aDemb9OVZKI5K8zEdW0SeCi4E6YWnxElATfJokRZTrqSEHTwjS9ftyORhn/nQ2Lg/cHp pR3xpDB9GTXPL3AA9o2jWl5qn8ZUuqBA6x9ayvt/D6pa9qDH7mZ7aTnra1qCWlARHs+t AvyoAZubCiIbMKpnqphS+QthGugBLZcFZsafuzthQNm9Tjwd/rOEKjRl69edv5iD4m1v snrBcRxKhPNRNSmw4h0JGgPel7YFVxkLyESyWVYlb4xjCAlftre7Ddu/i4A74TEo9qMB g/JQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=W4HgBL+rarePRfhToeCDFreePibGLonEGtpm7wVJr5M=; b=LM34E9apPmV4quujr2xjyE2b4DVfDiqk9YFMgIWdXnJY10SB+j4onXP1uJIiJ/li9T iGSlQt6JSv7SDgZKFgKnV3giDWdbIYPTvDVhRb9/XoiefEAu79wr5wpryGGBD7Fw10Lu I91MBF3rvu7SKvCWvI9ITZKQFr7xPWSXYkiBHPYJA/VAi165jTHVfHIquEksSfemg6qV jUYXxwNhCpt+wn7myMH7XoCC6Uiu/tpPTmBFEaJGC7kcV0MAhdoW3AH6aE9RTicKRKT3 1V0GYZ4B4grMsH6qx8OndFrBIZekjHXjxvHoQu3b4os45JpCWPOp3ZmceyHgvIVpps4L 7SVg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@bytedance-com.20210112.gappssmtp.com header.s=20210112 header.b=I2cwsbIn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=bytedance.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id t13-20020a056402240d00b00435706af0ccsi6137154eda.551.2022.06.20.00.29.28; Mon, 20 Jun 2022 00:29:54 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@bytedance-com.20210112.gappssmtp.com header.s=20210112 header.b=I2cwsbIn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=bytedance.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239124AbiFTHMS (ORCPT + 99 others); Mon, 20 Jun 2022 03:12:18 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49726 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239143AbiFTHML (ORCPT ); Mon, 20 Jun 2022 03:12:11 -0400 Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A0A3AE016 for ; Mon, 20 Jun 2022 00:12:09 -0700 (PDT) Received: by mail-yb1-xb2a.google.com with SMTP id n144so13333368ybf.12 for ; Mon, 20 Jun 2022 00:12:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bytedance-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=W4HgBL+rarePRfhToeCDFreePibGLonEGtpm7wVJr5M=; b=I2cwsbInE4YE+M/nciNA1a3jf9o6ZJiJzkLTwACB4ctl+mf6GwJAg3y5bE9U3MuKRC ZBi4z/b2qsRihjxkPs5Mhst6hFIJ7l+Kx6QYtsCspiFvtw+VG8MSa0z9hovtnuxDZ88U 8VuWt7Cmn0gNISnGss0oC3Pxcufi0d+AK3EBAZyi8t7STPePyCF6qb7KQP83wg8SFSnr HX594jybe01mCEH6sC/82/zdAf6tTDXiPsXzohvL5cxlyyCAZhA3iLO4hmnKSN0O3eeW MUKDZdnV9ci6Dkwa7CQ69uic2oCT5xyCfAIE9GpFIXXgTcND/xeqGAx5ypxsH47pq8K8 LMoA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=W4HgBL+rarePRfhToeCDFreePibGLonEGtpm7wVJr5M=; b=0S42ioohYqjqM0fWLfY7mM4DoecykzfBcgYkyaEf03yYKRxCqn6N0jp/3BhrcVCHAJ Y3VsNPIJ+aGkjApgsOQk72CHGa+zpXoJsPUgLruVXhR1+YADsxUIG3rZe3NrRhPcKteq p1hBBDDsm1B9uNong0mAA/qwvPQyDDqhgsCkIliWJeumTunvsSR2zOfZhf5EyfKLe5J+ iF/5e8zX0dEd0fAm2OwU+GW2AqZlQvlYt6wMhcFywtqNR6ZdHsunwB5W4GDHk+XJwTEL vhnTKQFRjG/ijO6MmL97e/IACd3hpRb0g6wQQlzi1uoNc3AgRBls3vh+Om+hWMSZoZ96 UEFw== X-Gm-Message-State: AJIora9U76ZExUBqh6AsZ0YKISAT8zLGucbjpkbAw87s32zxTG4ExR6c Gm2AvphgrNjXN8gA8t5u0J7DAjyHBwtmhCj0Fb+T7Q== X-Received: by 2002:a25:d146:0:b0:668:aa24:c321 with SMTP id i67-20020a25d146000000b00668aa24c321mr19499821ybg.89.1655709128850; Mon, 20 Jun 2022 00:12:08 -0700 (PDT) MIME-Version: 1.0 References: <20220620164246.0d3f7784@canb.auug.org.au> In-Reply-To: <20220620164246.0d3f7784@canb.auug.org.au> From: Muchun Song Date: Mon, 20 Jun 2022 15:11:31 +0800 Message-ID: Subject: Re: linux-next: build failures after merge of the mm tree To: Stephen Rothwell Cc: Andrew Morton , "Matthew Wilcox (Oracle)" , Linux Kernel Mailing List , Linux Next Mailing List , Oscar Salvador Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Thanks for your report. It is fixed in thread [1]. https://lore.kernel.org/all/20220619133851.68184-3-songmuchun@bytedance.com/ [1] On Mon, Jun 20, 2022 at 2:42 PM Stephen Rothwell wrote: > > Hi all, > > After merging the mm tree, today's linux-next build (x86_64 allnoconfig) > failed like this: > > In file included from arch/x86/include/asm/page.h:86, > from arch/x86/include/asm/thread_info.h:12, > from include/linux/thread_info.h:60, > from arch/x86/include/asm/preempt.h:7, > from include/linux/preempt.h:78, > from include/linux/spinlock.h:55, > from include/linux/mmzone.h:8, > from include/linux/gfp.h:6, > from include/linux/slab.h:15, > from include/linux/crypto.h:20, > from arch/x86/kernel/asm-offsets.c:9: > include/linux/mm.h: In function 'destroy_large_folio': > include/asm-generic/memory_model.h:35:21: error: implicit declaration of function 'page_to_section'; did you mean 'present_section'? [-Werror=implicit-function-declaration] > 35 | int __sec = page_to_section(__pg); \ > | ^~~~~~~~~~~~~~~ > include/asm-generic/memory_model.h:40:32: note: in definition of macro '__pfn_to_page' > 40 | ({ unsigned long __pfn = (pfn); \ > | ^~~ > include/asm-generic/memory_model.h:52:21: note: in expansion of macro '__page_to_pfn' > 52 | #define page_to_pfn __page_to_pfn > | ^~~~~~~~~~~~~ > include/linux/mm.h:214:38: note: in expansion of macro 'page_to_pfn' > 214 | #define nth_page(page,n) pfn_to_page(page_to_pfn((page)) + (n)) > | ^~~~~~~~~~~ > include/linux/page-flags.h:312:33: note: in expansion of macro 'nth_page' > 312 | #define folio_page(folio, n) nth_page(&(folio)->page, n) > | ^~~~~~~~ > include/linux/mm.h:928:38: note: in expansion of macro 'folio_page' > 928 | enum compound_dtor_id dtor = folio_page(folio, 1)->compound_dtor; > | ^~~~~~~~~~ > In file included from include/linux/memcontrol.h:20, > from include/linux/swap.h:9, > from include/linux/suspend.h:5, > from arch/x86/kernel/asm-offsets.c:13: > include/linux/mm.h: At top level: > include/linux/mm.h:1556:29: error: conflicting types for 'page_to_section'; have 'long unsigned int(const struct page *)' > 1556 | static inline unsigned long page_to_section(const struct page *page) > | ^~~~~~~~~~~~~~~ > In file included from arch/x86/include/asm/page.h:86, > from arch/x86/include/asm/thread_info.h:12, > from include/linux/thread_info.h:60, > from arch/x86/include/asm/preempt.h:7, > from include/linux/preempt.h:78, > from include/linux/spinlock.h:55, > from include/linux/mmzone.h:8, > from include/linux/gfp.h:6, > from include/linux/slab.h:15, > from include/linux/crypto.h:20, > from arch/x86/kernel/asm-offsets.c:9: > include/asm-generic/memory_model.h:35:21: note: previous implicit declaration of 'page_to_section' with type 'int()' > 35 | int __sec = page_to_section(__pg); \ > | ^~~~~~~~~~~~~~~ > include/asm-generic/memory_model.h:40:32: note: in definition of macro '__pfn_to_page' > 40 | ({ unsigned long __pfn = (pfn); \ > | ^~~ > include/asm-generic/memory_model.h:52:21: note: in expansion of macro '__page_to_pfn' > 52 | #define page_to_pfn __page_to_pfn > | ^~~~~~~~~~~~~ > include/linux/mm.h:214:38: note: in expansion of macro 'page_to_pfn' > 214 | #define nth_page(page,n) pfn_to_page(page_to_pfn((page)) + (n)) > | ^~~~~~~~~~~ > include/linux/page-flags.h:312:33: note: in expansion of macro 'nth_page' > 312 | #define folio_page(folio, n) nth_page(&(folio)->page, n) > | ^~~~~~~~ > include/linux/mm.h:928:38: note: in expansion of macro 'folio_page' > 928 | enum compound_dtor_id dtor = folio_page(folio, 1)->compound_dtor; > | ^~~~~~~~~~ > cc1: some warnings being treated as errors > > Caused by commit (I think) > > d3b90b76e101 ("mm: convert destroy_compound_page() to destroy_large_folio()") > > I have reverted these commits fot today: > > 56629699b3dd mm/swap: convert __delete_from_swap_cache() to a folio > e5085f2cc241 mm/swap: convert delete_from_swap_cache() to take a folio > 169f02f4efb1 mm: convert page_swap_flags to folio_swap_flags > d3b90b76e101 mm: convert destroy_compound_page() to destroy_large_folio() > > Then I got: > > mm/hugetlb_vmemmap.c: In function 'vmemmap_optimizable_pages': > mm/hugetlb_vmemmap.c:110:24: error: implicit declaration of function 'sparse_decode_mem_map' [-Werror=implicit-function-declaration] > 110 | vmemmap_page = sparse_decode_mem_map(ms->section_mem_map, > | ^~~~~~~~~~~~~~~~~~~~~ > mm/hugetlb_vmemmap.c:110:22: warning: assignment to 'struct page *' from 'int' makes pointer from integer without a cast [-Wint-conversion] > 110 | vmemmap_page = _sparsedecode_mem_map(ms->section_mem_map, > | ^ > cc1: some warnings being treated as errors > > from my arm64 defconfig build. > > Caused by commit > > 10a768735470 ("mm: memory_hotplug: make hugetlb_optimize_vmemmap compatible with memmap_on_memory") > > So I gave up and used the mm tree from next-20220617 for today. > -- > Cheers, > Stephen Rothwell