From: kbuild test robot <lkp@intel.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Jaegeuk Kim <jaegeuk@kernel.org>
Subject: Re: [PATCH] f2fs: support access control via key management
Date: Thu, 10 Mar 2016 10:18:45 +0800 [thread overview]
Message-ID: <201603101017.Kl8LkQFA%fengguang.wu@intel.com> (raw)
In-Reply-To: <1457571168-56724-1-git-send-email-jaegeuk@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 3474 bytes --]
Hi Jaegeuk,
[auto build test ERROR on f2fs/dev]
[also build test ERROR on next-20160309]
[cannot apply to v4.5-rc7]
[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/Jaegeuk-Kim/f2fs-support-access-control-via-key-management/20160310-085442
base: https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs dev
config: x86_64-randconfig-s0-03100948 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
fs/f2fs/file.c: In function 'validate_access_key':
>> fs/f2fs/file.c:462:16: error: implicit declaration of function 'request_key' [-Werror=implicit-function-declaration]
keyring_key = request_key(&key_type_logon, full_key_descriptor, NULL);
^
>> fs/f2fs/file.c:462:29: error: 'key_type_logon' undeclared (first use in this function)
keyring_key = request_key(&key_type_logon, full_key_descriptor, NULL);
^
fs/f2fs/file.c:462:29: note: each undeclared identifier is reported only once for each function it appears in
>> fs/f2fs/file.c:466:17: error: dereferencing pointer to incomplete type 'struct key'
if (keyring_key->type != &key_type_logon) {
^
In file included from include/uapi/linux/posix_types.h:4:0,
from include/uapi/linux/types.h:13,
from include/linux/compiler.h:199,
from include/linux/linkage.h:4,
from include/linux/fs.h:4,
from fs/f2fs/file.c:11:
fs/f2fs/file.c: In function 'f2fs_ioc_keyctl':
include/linux/stddef.h:7:14: warning: passing argument 6 of 'f2fs_setxattr' makes integer from pointer without a cast [-Wint-conversion]
#define NULL ((void *)0)
^
fs/f2fs/file.c:1599:27: note: in expansion of macro 'NULL'
value, F2FS_KEY_SIZE, NULL, type);
^
In file included from fs/f2fs/file.c:29:0:
fs/f2fs/xattr.h:129:19: note: expected 'int' but argument is of type 'void *'
static inline int f2fs_setxattr(struct inode *inode, int index,
^
fs/f2fs/file.c:1597:9: error: too many arguments to function 'f2fs_setxattr'
return f2fs_setxattr(inode, F2FS_XATTR_INDEX_KEY,
^
In file included from fs/f2fs/file.c:29:0:
fs/f2fs/xattr.h:129:19: note: declared here
static inline int f2fs_setxattr(struct inode *inode, int index,
^
cc1: some warnings being treated as errors
vim +/request_key +462 fs/f2fs/file.c
456 memcpy(full_key_descriptor, F2FS_KEY_DESC_PREFIX,
457 F2FS_KEY_DESC_PREFIX_SIZE);
458 sprintf(full_key_descriptor + F2FS_KEY_DESC_PREFIX_SIZE,
459 "%*phN", F2FS_KEY_SIZE, key);
460 full_key_descriptor[F2FS_KEY_DESC_PREFIX_SIZE +
461 (2 * F2FS_KEY_SIZE)] = '\0';
> 462 keyring_key = request_key(&key_type_logon, full_key_descriptor, NULL);
463 if (IS_ERR(keyring_key))
464 return PTR_ERR(keyring_key);
465
> 466 if (keyring_key->type != &key_type_logon) {
467 printk_once(KERN_WARNING
468 "%s: key type must be logon\n", __func__);
469 key_put(keyring_key);
---
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: 28618 bytes --]
next prev parent reply other threads:[~2016-03-10 2:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 0:52 Jaegeuk Kim
2016-03-10 2:05 ` kbuild test robot
2016-03-10 2:18 ` kbuild test robot [this message]
2016-03-15 7:24 ` Christoph Hellwig
2016-03-15 16:37 ` Jaegeuk Kim
2016-03-21 15:39 ` Christoph Hellwig
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=201603101017.Kl8LkQFA%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=jaegeuk@kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®