linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: ERROR: "min_low_pfn" undefined!
Date: Mon, 29 Jun 2020 19:13:30 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2006291911220.1118534@chino.kir.corp.google.com> (raw)
In-Reply-To: <202006300524.y9r1ZSHI%lkp@intel.com>

On Tue, 30 Jun 2020, kernel test robot wrote:

> Hi Alexander,
> 
> FYI, the error/warning still remains.
> 
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   7c30b859a947535f2213277e827d7ac7dcff9c84
> commit: f220df66f67684246ae1bf4a4e479efc7c2f325a intel_th: msu-sink: An example msu buffer "sink"
> date:   11 months ago
> config: microblaze-randconfig-c023-20200629 (attached as .config)
> compiler: microblaze-linux-gcc (GCC) 9.3.0
> 
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>):
> 
>    ERROR: "min_low_pfn" [drivers/rpmsg/virtio_rpmsg_bus.ko] undefined!
> >> ERROR: "min_low_pfn" [drivers/hwtracing/intel_th/intel_th_msu_sink.ko] undefined!
>    ERROR: "min_low_pfn" [drivers/hwtracing/intel_th/intel_th_msu.ko] undefined!
>    ERROR: "min_low_pfn" [drivers/mmc/core/mmc_core.ko] undefined!
>    ERROR: "min_low_pfn" [drivers/md/dm-crypt.ko] undefined!
>    ERROR: "min_low_pfn" [drivers/net/wireless/ath/ath6kl/ath6kl_sdio.ko] undefined!
>    ERROR: "min_low_pfn" [crypto/tcrypt.ko] undefined!
>    ERROR: "min_low_pfn" [crypto/asymmetric_keys/asym_tpm.ko] undefined!
> 

Looks like we have precedence for min_low_pfn failures and we can't blame 
this poor commit :)

I wonder why we don't simply do EXPORT_SYMBOL() in mm/memblock.c, 
non-microblaze architectures do this themselves because it doesn't get 
generically exported:

arch/ia64/kernel/ia64_ksyms.c:EXPORT_SYMBOL(min_low_pfn);       /* defined by bootmem.c, but not exported by generic code */
arch/sh/kernel/sh_ksyms_32.c:EXPORT_SYMBOL(min_low_pfn);

Adding Mike Rapoport.

  reply	other threads:[~2020-06-30  2:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 21:50 ERROR: "min_low_pfn" undefined! kernel test robot
2020-06-30  2:13 ` David Rientjes [this message]
2020-06-30 11:15   ` Mike Rapoport
  -- strict thread matches above, loose matches on Subject: below --
2020-09-01 12:05 kernel test robot
2020-09-01 17:59 ` Randy Dunlap
2020-09-01  5:41 kernel test robot
2020-09-01  5:47 ` Randy Dunlap
2020-08-25  2:29 kernel test robot
2020-08-22  3:30 kernel test robot
2020-08-20  2:11 kernel test robot
2020-08-11 10:27 kernel test robot
2020-08-01 20:42 kernel test robot
2020-08-01  2:35 kernel test robot
2020-07-20 16:23 kernel test robot
2020-07-10 10:29 kernel test robot
2020-07-05 19:40 kernel test robot
2020-07-01  0:41 kernel test robot
2020-06-29 22:28 kernel test robot
2020-06-27  6:54 kernel test robot
2020-06-27  3:19 kernel test robot
2020-06-24  3:42 kernel test robot
2020-06-23 15:57 kernel test robot
2020-06-21  9:54 kernel test robot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.22.394.2006291911220.1118534@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rppt@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).