From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH v3 2/2] security/inode.c: Add capabilities file.
Date: Fri, 21 Jan 2022 12:01:42 +0800 [thread overview]
Message-ID: <202201211107.0Qa4Y0bI-lkp@intel.com> (raw)
In-Reply-To: <20220120180116.167702-3-flaniel@linux.microsoft.com>
[-- Attachment #1: Type: text/plain, Size: 2894 bytes --]
Hi Francis,
[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on linux/master]
[also build test ERROR on linus/master jmorris-security/next-testing v5.16 next-20220120]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Francis-Laniel/Add-capabilities-file-to-sysfs/20220121-020524
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 1d1df41c5a33359a00e919d54eaebfb789711fdc
config: x86_64-randconfig-a011 (https://download.01.org/0day-ci/archive/20220121/202201211107.0Qa4Y0bI-lkp(a)intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/48b37f6e79a73709d7bcf17ea19464073f5da9b6
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Francis-Laniel/Add-capabilities-file-to-sysfs/20220121-020524
git checkout 48b37f6e79a73709d7bcf17ea19464073f5da9b6
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All error/warnings (new ones prefixed by >>):
security/inode.c: In function 'securityfs_init':
>> security/inode.c:362:24: error: implicit declaration of function 'securityfs'; did you mean 'security_bpf'? [-Werror=implicit-function-declaration]
362 | capabilities_dentry = securityfs("capabilities", 0444, NULL, NULL,
| ^~~~~~~~~~
| security_bpf
>> security/inode.c:362:22: warning: assignment to 'struct dentry *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
362 | capabilities_dentry = securityfs("capabilities", 0444, NULL, NULL,
| ^
cc1: some warnings being treated as errors
vim +362 security/inode.c
344
345 static int __init securityfs_init(void)
346 {
347 int retval;
348
349 retval = sysfs_create_mount_point(kernel_kobj, "security");
350 if (retval)
351 return retval;
352
353 retval = register_filesystem(&fs_type);
354 if (retval) {
355 sysfs_remove_mount_point(kernel_kobj, "security");
356 return retval;
357 }
358 #ifdef CONFIG_SECURITY
359 lsm_dentry = securityfs_create_file("lsm", 0444, NULL, NULL,
360 &lsm_ops);
361 #endif
> 362 capabilities_dentry = securityfs("capabilities", 0444, NULL, NULL,
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next prev parent reply other threads:[~2022-01-21 4:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 18:01 [RFC PATCH v3 0/2] Add capabilities file to sysfs Francis Laniel
2022-01-20 18:01 ` [RFC PATCH v3 1/2] capability: Add cap_string Francis Laniel
2022-01-20 18:01 ` [RFC PATCH v3 2/2] security/inode.c: Add capabilities file Francis Laniel
2022-01-21 4:01 ` kernel test robot [this message]
2022-01-21 8:58 ` Francis Laniel
2022-01-22 14:44 ` kernel test robot
2022-01-22 14:44 ` kernel test robot
2022-01-20 18:09 ` [RFC PATCH v3 0/2] Add capabilities file to sysfs Casey Schaufler
2022-01-20 18:14 ` Francis Laniel
2022-01-20 18:20 ` Eric W. Biederman
2022-01-20 19:01 ` Francis Laniel
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=202201211107.0Qa4Y0bI-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.