All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Price <steven.price@arm.com>
To: kbuild-all@lists.01.org
Subject: Re: [linux-next:master 1000/5337] mm/page_alloc.o:undefined reference to `node_reclaim_distance'
Date: Mon, 23 Dec 2019 10:39:45 +0000	[thread overview]
Message-ID: <20191223103944.GA17380@arm.com> (raw)
In-Reply-To: <201912221440.v4Pf5CrF%lkp@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1825 bytes --]

On Sun, Dec 22, 2019 at 06:30:44AM +0000, kbuild test robot wrote:
> Hi Steven,
> 
> It's probably a bug fix that unveils the link errors.

I've no idea why this has been bisected to my commit. I repeated the
bisection manually and that fingered:

a55c7454a8c8 ("sched/topology: Improve load balancing on AMD EPYC systems")

which certainly looks like it could be the culprit given it introduces
the node_reclaim_distance variable.

Steve

> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head:   7ddd09fc4b745fb1d8942f95389583e08412e0cd
> commit: ffbbaa7420f7a7ee6d547cd9adc286fe2e3753e0 [1000/5337] dma_resv: prime lockdep annotations
> config: powerpc-randconfig-a001-20191220 (attached as .config)
> compiler: powerpc64-linux-gcc (GCC) 7.5.0
> reproduce:
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         git checkout ffbbaa7420f7a7ee6d547cd9adc286fe2e3753e0
>         # save the attached .config to linux build tree
>         GCC_VERSION=7.5.0 make.cross ARCH=powerpc 
> 
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>):
> 
>    powerpc64-linux-ld: warning: orphan section `.gnu.hash' from `linker stubs' being placed in section `.gnu.hash'.
>    arch/powerpc/perf/perf_regs.o: In function `perf_reg_value':
>    arch/powerpc/perf/perf_regs.c:80: undefined reference to `.is_sier_available'
> >> mm/page_alloc.o:(.toc+0x0): undefined reference to `node_reclaim_distance'
> 
> ---
> 0-DAY kernel test infrastructure                 Open Source Technology Center
> https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation


  reply	other threads:[~2019-12-23 10:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-22  6:30 [linux-next:master 1000/5337] mm/page_alloc.o:undefined reference to `node_reclaim_distance' kbuild test robot
2019-12-23 10:39 ` Steven Price [this message]
2019-12-25  8:44   ` Rong Chen

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=20191223103944.GA17380@arm.com \
    --to=steven.price@arm.com \
    --cc=kbuild-all@lists.01.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.