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=-10.5 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,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 3E6E5C2B9F4 for ; Fri, 18 Jun 2021 02:31:06 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id B559F613BF for ; Fri, 18 Jun 2021 02:31:05 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B559F613BF Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 344516B0070; Thu, 17 Jun 2021 22:31:05 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 2CD9A6B0071; Thu, 17 Jun 2021 22:31:05 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 148596B0072; Thu, 17 Jun 2021 22:31:05 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0009.hostedemail.com [216.40.44.9]) by kanga.kvack.org (Postfix) with ESMTP id D2BCB6B0070 for ; Thu, 17 Jun 2021 22:31:04 -0400 (EDT) Received: from smtpin07.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id 6B4E9180AD817 for ; Fri, 18 Jun 2021 02:31:04 +0000 (UTC) X-FDA: 78265267248.07.2BCC3DD Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by imf23.hostedemail.com (Postfix) with ESMTP id E158EA00027A for ; Fri, 18 Jun 2021 02:31:01 +0000 (UTC) IronPort-SDR: gFZfEd1jJuUp5kXjrLOhRPrIA2NKa8wQ+hKQ58Gr9WEfSFYcpp92RtV7Inm0wZs/vKoZlEusz2 2WvopwZQuJ+Q== X-IronPort-AV: E=McAfee;i="6200,9189,10018"; a="206522315" X-IronPort-AV: E=Sophos;i="5.83,281,1616482800"; d="scan'208";a="206522315" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Jun 2021 19:30:57 -0700 IronPort-SDR: LNeRt7jcTgmZlUFvpESLy6HA+G0PZ5HL8MhZtrJewFA7LvAtcqfgcFBDpBo6CDPy0r5Ck5Nil/ nLym5qVldoFg== X-IronPort-AV: E=Sophos;i="5.83,281,1616482800"; d="scan'208";a="485524622" Received: from shao2-debian.sh.intel.com (HELO [10.239.13.11]) ([10.239.13.11]) by orsmga001-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Jun 2021 19:30:55 -0700 Subject: Re: [linux-next:master 6856/7430] hppa64-linux-ld: init/do_mounts.o(.text.unlikely+0x88): cannot reach dump_page To: Arnd Bergmann Cc: kernel test robot , kbuild-all@lists.01.org, Linux Memory Management List , Helge Deller , Linux Kbuild mailing list , Philip Li References: <202106051816.t4mlM0Df-lkp@intel.com> From: Rong Chen Message-ID: <46eaef63-0e65-94fa-2400-39524faf32c6@intel.com> Date: Fri, 18 Jun 2021 10:30:53 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Authentication-Results: imf23.hostedemail.com; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=intel.com (policy=none); spf=none (imf23.hostedemail.com: domain of rong.a.chen@intel.com has no SPF policy when checking 134.134.136.65) smtp.mailfrom=rong.a.chen@intel.com X-Stat-Signature: n5733z7isgdchgfxot11gwkbx5b9d1md X-Rspamd-Queue-Id: E158EA00027A X-Rspamd-Server: rspam06 X-HE-Tag: 1623983461-184900 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 6/7/21 3:19 PM, Arnd Bergmann wrote: > On Mon, Jun 7, 2021 at 8:27 AM Rong Chen wrote: >> On 6/5/21 7:08 PM, Arnd Bergmann wrote: >>> On Sat, Jun 5, 2021 at 12:59 PM kernel test robot wrote: >>>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master >>>> head: ccc252d2e818f6a479441119ad453c3ce7c7c461 >>>> commit: 2ada05c3a46dda2e2b065a02307c0c6268d9678f [6856/7430] Merge remote-tracking branch 'asm-generic/master' >>>> config: parisc-randconfig-r012-20210604 (attached as .config) >>>> compiler: hppa64-linux-gcc (GCC) 9.3.0 >>>> reproduce (this is a W=1 build): >>>> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross >>>> chmod +x ~/bin/make.cross >>>> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=2ada05c3a46dda2e2b065a02307c0c6268d9678f >>>> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git >>>> git fetch --no-tags linux-next master >>>> git checkout 2ada05c3a46dda2e2b065a02307c0c6268d9678f >>>> # save the attached .config to linux build tree >>>> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=parisc >>>> >>>> If you fix the issue, kindly add following tag as appropriate >>>> Reported-by: kernel test robot >>> Helge Deller already fixed this problem with commit 778e45d7720d >>> ("parisc: E >> We will ignore the error firstly, I'm a little confused, who can handle >> the randconfig failures if COMPILE_TEST=n? > The failures that you only see with COMPILE_TEST=n are the ones that > someone has previously decided can not be handled properly, for one > reason or another, examples include: > > - rebuilding generated files that require additional tools to be > installed on the host, > e.g. CONFIG_PREVENT_FIRMWARE_BUILD > - configurations that may or may not work but result in excessive > compiler warnings > that are not otherwise interesting, e.g. GCC_PLUGIN_CYC_COMPLEXITY > - options that enable compile-time warnings about pointless configurations > such as leaving out support for every machine > - options that are unlikely to have an effect on testing but slow down the build > time (e.g. CONFIG_DEBUG_INFO) for build bots finite hardware resources. > > On the primary architectures, randconfig builds with 'make -s' should generally > result in no output from the build, and I would consider any output > you get a bug. > When COMPILE_TEST is disabled, there are countless known issues in > configurations that make no practical sense. > > Arnd Hi Arnd, Thanks for the detailed explanation, and we have asked advice of internal developers, we'll enable COMPILE_TEST for randconfig, and check the failures if COMPILE_TEST=n in future. BTW is there any issue that found by randconfig with COMPILE_TEST=n should be reported? Best Regards, Rong Chen