All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suren Baghdasaryan <surenb@google.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 1/1] mm: introduce process_reap system call
Date: Thu, 24 Jun 2021 12:39:17 -0700	[thread overview]
Message-ID: <CAJuCfpGqce2XK-GRRDN=QL0=ZXAO3k=dsBCm7tnA4fKu0XNxYA@mail.gmail.com> (raw)
In-Reply-To: <202106241900.PfrrSrWZ-lkp@intel.com>

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

On Thu, Jun 24, 2021 at 5:06 AM kernel test robot <lkp@intel.com> wrote:
>
> Hi Suren,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on arm64/for-next/core]
> [also build test ERROR on tip/x86/asm linus/master v5.13-rc7]
> [cannot apply to hnaz-linux-mm/master next-20210623]
> [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/mm-introduce-process_reap-system-call/20210624-032923
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
> config: arm-randconfig-s032-20210622 (attached as .config)
> compiler: arm-linux-gnueabi-gcc (GCC) 9.3.0
> reproduce:
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # apt-get install sparse
>         # sparse version: v0.6.3-341-g8af24329-dirty
>         # https://github.com/0day-ci/linux/commit/64bd00602e706bc1b2e2267ca1434646c0900fa1
>         git remote add linux-review https://github.com/0day-ci/linux
>         git fetch --no-tags linux-review Suren-Baghdasaryan/mm-introduce-process_reap-system-call/20210624-032923
>         git checkout 64bd00602e706bc1b2e2267ca1434646c0900fa1
>         # save the attached .config to linux build tree
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' W=1 ARCH=arm
>
> 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 >>):
>
>    arm-linux-gnueabi-ld: mm/oom_kill.o: in function `__se_sys_process_reap':
> >> oom_kill.c:(.text+0x157e): undefined reference to `__oom_reap_task_mm'

Thanks kernel test robot! I missed that __oom_reap_task_mm is
undefined when CONFIG_MMU=n. Will fix it in the next revision. I think
returning -ENOSYS in this case would be appropriate for the syscall.

>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

  reply	other threads:[~2021-06-24 19:39 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23 19:28 [PATCH 1/1] mm: introduce process_reap system call Suren Baghdasaryan
2021-06-23 19:28 ` Suren Baghdasaryan
2021-06-23 19:34 ` Suren Baghdasaryan
2021-06-23 19:34   ` Suren Baghdasaryan
2021-06-24  6:47 ` kernel test robot
2021-06-24 11:30 ` kernel test robot
2021-06-24 12:05 ` kernel test robot
2021-06-24 19:39   ` Suren Baghdasaryan [this message]
2021-06-29 13:13 ` Christian Brauner
2021-06-29 16:15   ` Suren Baghdasaryan
2021-06-29 16:15     ` Suren Baghdasaryan
2021-06-30 18:00 ` Shakeel Butt
2021-06-30 18:00   ` Shakeel Butt
2021-06-30 18:43   ` Suren Baghdasaryan
2021-06-30 18:43     ` Suren Baghdasaryan
2021-06-30 19:00     ` Shakeel Butt
2021-06-30 19:00       ` Shakeel Butt
2021-06-30 19:06       ` Suren Baghdasaryan
2021-06-30 19:06         ` Suren Baghdasaryan
2021-06-30 18:26 ` Andy Lutomirski
2021-06-30 18:26   ` Andy Lutomirski
2021-06-30 18:51   ` Suren Baghdasaryan
2021-06-30 18:51     ` Suren Baghdasaryan
2021-06-30 21:45     ` Johannes Weiner
2021-07-01  0:44       ` Andy Lutomirski
2021-07-01  0:44         ` Andy Lutomirski
2021-07-01 22:59         ` Suren Baghdasaryan
2021-07-01 22:59           ` Suren Baghdasaryan
2021-07-02 15:27           ` Christian Brauner
2021-07-05  7:41             ` David Hildenbrand
2021-07-07 12:38               ` Michal Hocko
2021-07-07 21:14                 ` Suren Baghdasaryan
2021-07-07 21:14                   ` Suren Baghdasaryan
2021-07-09  8:58                   ` Christian Brauner
2021-07-09 20:05                     ` Suren Baghdasaryan
2021-07-09 20:05                       ` Suren Baghdasaryan
2021-07-01  0:45     ` Andy Lutomirski
2021-07-01  0:45       ` Andy Lutomirski
2021-07-01 23:08       ` Suren Baghdasaryan
2021-07-01 23:08         ` Suren Baghdasaryan
2021-07-07  9:46 ` Florian Weimer
2021-07-07  9:46   ` Florian Weimer
2021-07-07 21:07   ` Suren Baghdasaryan
2021-07-07 21:07     ` Suren Baghdasaryan
2021-07-08  5:40     ` Florian Weimer
2021-07-08  5:40       ` Florian Weimer
2021-07-08  6:05       ` Suren Baghdasaryan
2021-07-08  6:05         ` Suren Baghdasaryan
2021-07-08  6:14         ` Florian Weimer
2021-07-08  6:14           ` Florian Weimer
2021-07-08  6:39           ` Suren Baghdasaryan
2021-07-08  6:39             ` Suren Baghdasaryan
2021-07-08  7:13             ` Florian Weimer
2021-07-08  7:13               ` Florian Weimer
2021-07-12 12:51         ` Jan Engelhardt
2021-07-12 18:39           ` Suren Baghdasaryan
2021-07-12 18:39             ` Suren Baghdasaryan
2021-07-12 19:16             ` Jan Engelhardt
2021-06-23 20:43 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='CAJuCfpGqce2XK-GRRDN=QL0=ZXAO3k=dsBCm7tnA4fKu0XNxYA@mail.gmail.com' \
    --to=surenb@google.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.