linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Chris Down <chris@chrisdown.name>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 49/120] mm/memcontrol.c:2418: undefined reference to `__udivdi3'
Date: Sat, 27 Jul 2019 04:16:28 +0800	[thread overview]
Message-ID: <201907270424.JeLLgbe6%lkp@intel.com> (raw)

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

tree:   git://git.cmpxchg.org/linux-mmotm.git master
head:   79b3e476080beb7faf41bddd6c3d7059cd1a5f31
commit: ed1a3a688c413aae92395c71c142d3fdd2190069 [49/120] mm, memcg: throttle allocators when failing reclaim over memory.high
config: i386-randconfig-h003-201929 (attached as .config)
compiler: gcc-7 (Debian 7.4.0-10) 7.4.0
reproduce:
        git checkout ed1a3a688c413aae92395c71c142d3fdd2190069
        # save the attached .config to linux build tree
        make ARCH=i386 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   ld: mm/memcontrol.o: in function `mem_cgroup_handle_over_high':
>> mm/memcontrol.c:2418: undefined reference to `__udivdi3'

vim +2418 mm/memcontrol.c

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 31975 bytes --]

             reply	other threads:[~2019-07-26 20:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-26 20:16 kbuild test robot [this message]
2019-07-26 22:34 ` Chris Down

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=201907270424.JeLLgbe6%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=chris@chrisdown.name \
    --cc=hannes@cmpxchg.org \
    --cc=kbuild-all@01.org \
    --cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox