From: kbuild test robot <lkp@intel.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: kbuild-all@01.org, LSM <linux-security-module@vger.kernel.org>,
James Morris <jmorris@namei.org>,
John Johansen <john.johansen@canonical.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
Paul Moore <paul@paul-moore.com>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Kees Cook <keescook@chromium.org>,
LKLM <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] LSM: module hierarchy in /proc/.../attr
Date: Thu, 9 Jun 2016 06:56:20 +0800 [thread overview]
Message-ID: <201606090609.TTPZsO9T%fengguang.wu@intel.com> (raw)
In-Reply-To: <3fb59e68-4448-84fd-dcbd-ed0b1731096a@schaufler-ca.com>
[-- Attachment #1: Type: text/plain, Size: 2187 bytes --]
Hi,
[auto build test WARNING on security/next]
[also build test WARNING on v4.7-rc2 next-20160608]
[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/Casey-Schaufler/LSM-module-hierarchy-in-proc-attr/20160609-055140
base: https://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next
reproduce: make htmldocs
All warnings (new ones prefixed by >>):
lib/crc32.c:148: warning: No description found for parameter 'tab)[256]'
lib/crc32.c:148: warning: Excess function parameter 'tab' description in 'crc32_le_generic'
lib/crc32.c:293: warning: No description found for parameter 'tab)[256]'
lib/crc32.c:293: warning: Excess function parameter 'tab' description in 'crc32_be_generic'
lib/crc32.c:1: warning: no structured comments found
mm/memory.c:2881: warning: No description found for parameter 'old'
>> security/security.c:127: warning: No description found for parameter 'hooks'
>> security/security.c:127: warning: No description found for parameter 'count'
>> security/security.c:127: warning: No description found for parameter 'lsm'
vim +/hooks +127 security/security.c
111 * Otherwise, return false.
112 */
113 int __init security_module_enable(const char *module)
114 {
115 return !strcmp(module, chosen_lsm);
116 }
117
118 /**
119 * security_add_hooks - Add a modules hooks to the hook lists.
120 * @hooks - the hooks to add
121 * @count - the number of hooks to add
122 *
123 * Each LSM has to register its hooks with the infrastructure.
124 */
125 void __init security_add_hooks(struct security_hook_list *hooks, int count,
126 char *lsm)
> 127 {
128 int i;
129
130 for (i = 0; i < count; i++) {
131 hooks[i].lsm = lsm;
132 list_add_tail_rcu(&hooks[i].list, hooks[i].head);
133 }
134 if (lsm_append(lsm, &lsm_names) < 0)
135 panic("%s - Cannot get early memory.\n", __func__);
---
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: 6370 bytes --]
next prev parent reply other threads:[~2016-06-08 22:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 21:49 Casey Schaufler
2016-06-08 22:49 ` kbuild test robot
2016-06-08 22:56 ` kbuild test robot [this message]
2016-06-09 17:18 ` [PATCH v2] " Casey Schaufler
2016-06-09 18:43 ` [PATCH] " Kees Cook
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=201606090609.TTPZsO9T%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=kbuild-all@01.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=sds@tycho.nsa.gov \
/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
all inboxes | Powered by JetHome®