From: kbuild test robot <lkp@intel.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: kbuild-all@01.org, Jessica Yu <jeyu@redhat.com>,
Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
Petr Mladek <pmladek@suse.com>,
linux-kernel@vger.kernel.org, live-patching@vger.kernel.org,
Chunyu Hu <chuhu@redhat.com>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH] livepatch/module: make TAINT_LIVEPATCH module-specific
Date: Thu, 25 Aug 2016 14:40:28 +0800 [thread overview]
Message-ID: <201608251420.RyMc1Xdh%fengguang.wu@intel.com> (raw)
In-Reply-To: <c6a606f6c1e291c6c292403ade24833801ad243d.1472074373.git.jpoimboe@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1691 bytes --]
Hi Josh,
[auto build test ERROR on jikos-livepatching/for-next]
[also build test ERROR on v4.8-rc3 next-20160824]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]
url: https://github.com/0day-ci/linux/commits/Josh-Poimboeuf/livepatch-module-make-TAINT_LIVEPATCH-module-specific/20160825-053847
base: https://git.kernel.org/pub/scm/linux/kernel/git/jikos/livepatching.git for-next
config: x86_64-kexec (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
kernel/module.c: In function 'check_modinfo':
>> kernel/module.c:2960:6: error: 'struct module' has no member named 'klp'; did you mean 'kp'?
mod->klp = true;
^~
vim +2960 kernel/module.c
2954 if (get_modinfo(info, "livepatch")) {
2955 if (!IS_ENABLED(CONFIG_LIVEPATCH)) {
2956 pr_err("%s: module is marked as livepatch module, but livepatch support is disabled\n",
2957 mod->name);
2958 return -ENOEXEC;
2959 }
> 2960 mod->klp = true;
2961 pr_warn("%s: loading livepatch module.\n", mod->name);
2962 add_taint_module(mod, TAINT_LIVEPATCH, LOCKDEP_STILL_OK);
2963 }
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 22949 bytes --]
next prev parent reply other threads:[~2016-08-25 6:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 21:33 [PATCH] livepatch/module: make TAINT_LIVEPATCH module-specific Josh Poimboeuf
2016-08-24 21:43 ` Josh Poimboeuf
2016-08-25 0:54 ` Jiri Kosina
2016-08-25 4:14 ` Rusty Russell
2016-08-25 2:53 ` Jessica Yu
2016-08-25 3:23 ` [PATCH] " Josh Poimboeuf
2016-08-25 6:40 ` kbuild test robot [this message]
2016-08-25 7:46 ` Petr Mladek
2016-08-25 12:31 ` Josh Poimboeuf
2016-08-25 14:25 ` Miroslav Benes
2016-08-25 14:42 ` Josh Poimboeuf
2016-08-25 14:47 ` Miroslav Benes
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=201608251420.RyMc1Xdh%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=chuhu@redhat.com \
--cc=jeyu@redhat.com \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.com \
--cc=rusty@rustcorp.com.au \
/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;
as well as URLs for NNTP newsgroup(s).