From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 1/1] RFC: add pidfd_send_signal flag to reclaim mm while killing a process
Date: Sun, 15 Nov 2020 02:18:20 +0800 [thread overview]
Message-ID: <202011150248.y1OfdVNH-lkp@intel.com> (raw)
In-Reply-To: <20201113173448.1863419-1-surenb@google.com>
[-- Attachment #1: Type: text/plain, Size: 1805 bytes --]
Hi Suren,
[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on linus/master]
[also build test ERROR on v5.10-rc3]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Suren-Baghdasaryan/RFC-add-pidfd_send_signal-flag-to-reclaim-mm-while-killing-a-process/20201114-013551
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 585e5b17b92dead8a3aca4e3c9876fbca5f7e0ba
config: h8300-randconfig-r023-20201113 (attached as .config)
compiler: h8300-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://github.com/0day-ci/linux/commit/f350a31b4bb718aa40224cb93f82197839581274
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Suren-Baghdasaryan/RFC-add-pidfd_send_signal-flag-to-reclaim-mm-while-killing-a-process/20201114-013551
git checkout f350a31b4bb718aa40224cb93f82197839581274
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=h8300
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 >>):
h8300-linux-ld: kernel/signal.o: in function `.L974':
>> signal.c:(.text+0x50d5): undefined reference to `__oom_reap_task_mm'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 35422 bytes --]
prev parent reply other threads:[~2020-11-14 18:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 17:34 [PATCH 1/1] RFC: add pidfd_send_signal flag to reclaim mm while killing a process Suren Baghdasaryan
2020-11-13 23:11 ` kernel test robot
2020-11-13 23:55 ` Andrew Morton
2020-11-14 0:06 ` Suren Baghdasaryan
2020-11-14 1:00 ` Andrew Morton
2020-11-14 1:09 ` Suren Baghdasaryan
2020-11-14 1:18 ` Andrew Morton
2020-11-14 1:57 ` Suren Baghdasaryan
2020-11-14 2:16 ` Andrew Morton
2020-11-14 2:51 ` Suren Baghdasaryan
2020-11-16 23:24 ` Minchan Kim
2020-11-18 19:10 ` Michal Hocko
2020-11-18 19:22 ` Suren Baghdasaryan
2020-11-18 19:32 ` Michal Hocko
2020-11-18 19:51 ` Suren Baghdasaryan
2020-11-18 19:55 ` Suren Baghdasaryan
2020-11-19 0:13 ` Suren Baghdasaryan
2020-11-24 5:45 ` Suren Baghdasaryan
2020-11-18 10:32 ` Christian Brauner
2020-11-14 18:18 ` kernel test robot [this message]
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=202011150248.y1OfdVNH-lkp@intel.com \
--to=lkp@intel.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.