mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: kernel test robot <lkp@intel.com>, Vasily Averin <vvs@virtuozzo.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: undefined reference to `memcg_bulk_charge_hook'
Date: Tue, 12 Oct 2021 14:55:52 -0700	[thread overview]
Message-ID: <2a5a496b-5b5e-0039-5bb2-d04268215e37@infradead.org> (raw)
In-Reply-To: <202110130513.t6y4KgaP-lkp@intel.com>

On 10/12/21 2:34 PM, kernel test robot wrote:
> tree:   https://github.com/0day-ci/linux/commits/UPDATE-20211012-182031/Vasily-Averin/memcg-enable-memory-accounting-in-__alloc_pages_bulk/20211008-172703
> head:   e10c5e64a0799c75d26d2a82c03f757335616711
> commit: e10c5e64a0799c75d26d2a82c03f757335616711 memcg: enable memory accounting in __alloc_pages_bulk
> date:   11 hours ago
> config: powerpc64-randconfig-r001-20211012 (attached as .config)
> compiler: powerpc-linux-gcc (GCC) 11.2.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://github.com/0day-ci/linux/commit/e10c5e64a0799c75d26d2a82c03f757335616711
>          git remote add linux-review https://github.com/0day-ci/linux
>          git fetch --no-tags linux-review UPDATE-20211012-182031/Vasily-Averin/memcg-enable-memory-accounting-in-__alloc_pages_bulk/20211008-172703
>          git checkout e10c5e64a0799c75d26d2a82c03f757335616711
>          # save the attached .config to linux build tree
>          mkdir build_dir
>          COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=powerpc SHELL=/bin/bash

Hi ktr/lkp,

Can you explain why the (previously) attached .config file says:
CONFIG_32BIT=y

but in the email text above, it says:
config: powerpc64-randconfig-r001-20211012

I would expect a powerpc64 randconfig to say
CONFIG_64BIT=y

Am I just confused?

Also, using (Arnd's) crosstools, the compiler for powerpc64 shows up
as powerpc64-linux-ld, not as powerpc-linux-ld.
Is that different for the 0day toolchains?
(not AFAICT)


> 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 >>):
> 
>     powerpc-linux-ld: mm/page_alloc.o: in function `__alloc_pages_bulk':
>>> (.text+0x857c): undefined reference to `memcg_bulk_charge_hook'
>>> powerpc-linux-ld: (.text+0x86d0): undefined reference to `memcg_bulk_post_charge_hook'
>     powerpc-linux-ld: (.text+0x870c): undefined reference to `memcg_bulk_post_charge_hook'
>>> powerpc-linux-ld: (.text+0x87c8): undefined reference to `memcg_bulk_pre_charge_hook'
> 
> ---

thanks.
-- 
~Randy

  reply	other threads:[~2021-10-12 21:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12 21:34 kernel test robot
2021-10-12 21:55 ` Randy Dunlap [this message]
2021-10-13  3:09   ` [kbuild-all] " Chen, Rong A

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=2a5a496b-5b5e-0039-5bb2-d04268215e37@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=arnd@arndb.de \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=vvs@virtuozzo.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

all inboxes | Powered by JetHome®