From: kbuild test robot <lkp@intel.com>
To: Matteo Croce <mcroce@redhat.com>
Cc: kbuild-all@01.org, LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2] proc/sysctl: add shared variables for range check
Date: Wed, 17 Apr 2019 13:26:52 +0800 [thread overview]
Message-ID: <201904171348.0RXpr02p%lkp@intel.com> (raw)
In-Reply-To: <20190417005943.17448-1-mcroce@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
Hi Matteo,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v5.1-rc5]
[cannot apply to next-20190416]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Matteo-Croce/proc-sysctl-add-shared-variables-for-range-check/20190417-105810
config: x86_64-randconfig-m0-04170939 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
ERROR: "sysctl_zero" [net/sctp/sctp.ko] undefined!
ERROR: "sysctl_one" [net/sctp/sctp.ko] undefined!
ERROR: "sysctl_int_max" [net/sctp/sctp.ko] undefined!
>> ERROR: "sysctl_one" [net/rxrpc/rxrpc.ko] undefined!
>> ERROR: "sysctl_zero" [net/ipv6/ipv6.ko] undefined!
>> ERROR: "sysctl_one" [net/ipv6/ipv6.ko] undefined!
make[2]: *** [__modpost] Error 1
make[2]: Target '_modpost' not remade because of errors.
make[1]: *** [modules] Error 2
make[1]: Target '_all' not remade because of errors.
---
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: 33154 bytes --]
next prev parent reply other threads:[~2019-04-17 5:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 0:59 [PATCH v2] proc/sysctl: add shared variables for range check Matteo Croce
2019-04-17 3:17 ` Andrew Morton
2019-04-17 5:56 ` Matteo Croce
2019-04-17 5:26 ` kbuild test robot [this message]
2019-04-17 5:51 ` kbuild 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=201904171348.0RXpr02p%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcroce@redhat.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 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.