From: kbuild test robot <lkp@intel.com>
To: Petko Manolov <petkan@mip-labs.com>
Cc: kbuild-all@01.org, Al Viro <viro@ZenIV.linux.org.uk>,
Stephen Rothwell <sfr@canb.auug.org.au>,
James Morris <jmorris@namei.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Mimi Zohar <zohar@linux.vnet.ibm.com>
Subject: Re: [PATCH] ima_write_policy() optimizations;
Date: Sat, 2 Jan 2016 01:41:26 +0800 [thread overview]
Message-ID: <201601020148.FnlbXVDc%fengguang.wu@intel.com> (raw)
In-Reply-To: <20160101172937.GD13634@localhost>
[-- Attachment #1: Type: text/plain, Size: 2369 bytes --]
Hi Petko,
[auto build test ERROR on integrity/next]
[cannot apply to v4.4-rc7 next-20151231]
[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/Petko-Manolov/ima_write_policy-optimizations/20160102-013037
base: https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git next
config: i386-randconfig-x002-12300610 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
security/integrity/ima/ima_fs.c:275:9: sparse: undefined identifier 'data'
security/integrity/ima/ima_fs.c:276:14: sparse: undefined identifier 'data'
security/integrity/ima/ima_fs.c:279:11: sparse: undefined identifier 'data'
security/integrity/ima/ima_fs.c:282:28: sparse: undefined identifier 'data'
security/integrity/ima/ima_fs.c:289:37: sparse: undefined identifier 'data'
security/integrity/ima/ima_fs.c:296:15: sparse: undefined identifier 'data'
security/integrity/ima/ima_fs.c: In function 'ima_write_policy':
>> security/integrity/ima/ima_fs.c:275:2: error: 'data' undeclared (first use in this function)
data = kmalloc(datalen + 1, GFP_KERNEL);
^
security/integrity/ima/ima_fs.c:275:2: note: each undeclared identifier is reported only once for each function it appears in
vim +/data +275 security/integrity/ima/ima_fs.c
4af4662f Mimi Zohar 2009-02-04 269 /* No partial writes. */
6ccd0456 Eric Paris 2010-04-20 270 result = -EINVAL;
6ccd0456 Eric Paris 2010-04-20 271 if (*ppos != 0)
6ccd0456 Eric Paris 2010-04-20 272 goto out;
6ccd0456 Eric Paris 2010-04-20 273
6ccd0456 Eric Paris 2010-04-20 274 result = -ENOMEM;
4af4662f Mimi Zohar 2009-02-04 @275 data = kmalloc(datalen + 1, GFP_KERNEL);
4af4662f Mimi Zohar 2009-02-04 276 if (!data)
6ccd0456 Eric Paris 2010-04-20 277 goto out;
4af4662f Mimi Zohar 2009-02-04 278
:::::: The code at line 275 was first introduced by commit
:::::: 4af4662fa4a9dc62289c580337ae2506339c4729 integrity: IMA policy
:::::: TO: Mimi Zohar <zohar@linux.vnet.ibm.com>
:::::: CC: James Morris <jmorris@namei.org>
---
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: 18304 bytes --]
next prev parent reply other threads:[~2016-01-01 17:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 4:24 linux-next: manual merge of the security tree with the vfs tree Stephen Rothwell
2015-12-31 4:30 ` Al Viro
2015-12-31 10:45 ` Petko Manolov
2016-01-01 4:34 ` Al Viro
2016-01-01 17:29 ` Petko Manolov
2016-01-01 17:41 ` kbuild test robot [this message]
2016-01-04 1:37 ` Mimi Zohar
2016-01-04 1:55 ` Stephen Rothwell
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=201601020148.FnlbXVDc%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=jmorris@namei.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=petkan@mip-labs.com \
--cc=sfr@canb.auug.org.au \
--cc=viro@ZenIV.linux.org.uk \
--cc=zohar@linux.vnet.ibm.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 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).