From: kbuild test robot <lkp@intel.com>
To: Kirill Marinushkin <k.marinushkin@gmail.com>
Cc: kbuild-all@01.org, dhowells@redhat.com,
linux-kernel@vger.kernel.org, keyrings@vger.kernel.org,
linux-security-module@vger.kernel.org, k.marinushkin@gmail.com
Subject: Re: [PATCH] Security: Keys: Added derived keytype
Date: Tue, 22 Mar 2016 10:04:11 +0800 [thread overview]
Message-ID: <201603221004.DFEo40Cj%fengguang.wu@intel.com> (raw)
In-Reply-To: <1458607577-25578-1-git-send-email-k.marinushkin@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1933 bytes --]
Hi Kirill,
[auto build test WARNING on v4.5-rc7]
[also build test WARNING on next-20160321]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Kirill-Marinushkin/Security-Keys-Added-derived-keytype/20160322-084809
config: sparc64-allyesconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=sparc64
All warnings (new ones prefixed by >>):
security/keys/derived.c: In function 'parse_options':
>> security/keys/derived.c:217:15: warning: assignment from incompatible pointer type
usalt.lenp = &payload->saltlen;
^
vim +217 security/keys/derived.c
201 switch (token) {
202
203 case OPT_SHORT_SALT: /* salt */
204 case OPT_LONG_SALT:
205 templen = args[0].to - args[0].from;
206 if (templen < 0 || templen > SALT_MAX_SIZE) {
207 pr_err(PREFIX "invalid salt length");
208 return -EINVAL;
209 }
210 payload->salt = kstrndup(args[0].from, templen, GFP_KERNEL);
211 if (!payload->salt) {
212 pr_err(PREFIX "salt alloc failed");
213 return -ENOMEM;
214 }
215 payload->saltlen = templen;
216 usalt.data = payload->salt;
> 217 usalt.lenp = &payload->saltlen;
218 break;
219
220 case OPT_SHORT_ITER: /* iterations */
221 case OPT_LONG_ITER:
222 if (kstrtou64(args[0].from, 0, &tempul)
223 || tempul == 0
224 || tempul > ITER_MAX_VAL) {
225 pr_err(PREFIX "invalid iterations number");
---
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: 45105 bytes --]
next prev parent reply other threads:[~2016-03-22 2:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 0:46 Kirill Marinushkin
2016-03-22 2:04 ` kbuild test robot [this message]
2016-03-22 9:53 ` David Howells
2016-04-01 15:56 ` David Howells
2016-03-30 7:34 Kirill Marinushkin
2016-04-01 15:17 ` David Howells
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=201603221004.DFEo40Cj%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.com \
--cc=k.marinushkin@gmail.com \
--cc=kbuild-all@01.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome