From: kernel test robot <lkp@intel.com>
To: Matthias Kaehlcke <mka@chromium.org>,
Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
Kees Cook <keescook@chromium.org>,
James Morris <jmorris@namei.org>,
"Serge E . Hallyn" <serge@hallyn.com>
Cc: kbuild-all@lists.01.org, linux-raid@vger.kernel.org,
linux-kernel@vger.kernel.org, Song Liu <song@kernel.org>,
linux-security-module@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
dm-devel@redhat.com, Matthias Kaehlcke <mka@chromium.org>
Subject: Re: [PATCH 2/3] LoadPin: Enable loading from trusted dm-verity devices
Date: Tue, 19 Apr 2022 12:32:43 +0800 [thread overview]
Message-ID: <202204191222.n0HWtNe0-lkp@intel.com> (raw)
In-Reply-To: <20220418141545.2.I01c67af41d2f6525c6d023101671d7339a9bc8b5@changeid>
Hi Matthias,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on device-mapper-dm/for-next]
[also build test ERROR on song-md/md-next kees/for-next/pstore v5.18-rc3 next-20220414]
[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/intel-lab-lkp/linux/commits/Matthias-Kaehlcke/LoadPin-Enable-loading-from-trusted-dm-verity-devices/20220419-051810
base: https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
config: powerpc-buildonly-randconfig-r002-20220417 (https://download.01.org/0day-ci/archive/20220419/202204191222.n0HWtNe0-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/5af892969b227a2602732e4be44a0c4a41967400
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Matthias-Kaehlcke/LoadPin-Enable-loading-from-trusted-dm-verity-devices/20220419-051810
git checkout 5af892969b227a2602732e4be44a0c4a41967400
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=powerpc SHELL=/bin/bash security/loadpin/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
security/loadpin/loadpin.c: In function 'loadpin_init':
>> security/loadpin/loadpin.c:404:44: error: 'loadpin_sysctl_path' undeclared (first use in this function)
404 | if (!register_sysctl_paths(loadpin_sysctl_path,
| ^~~~~~~~~~~~~~~~~~~
security/loadpin/loadpin.c:404:44: note: each undeclared identifier is reported only once for each function it appears in
>> security/loadpin/loadpin.c:405:44: error: 'loadpin_sysctl_table_verity' undeclared (first use in this function)
405 | loadpin_sysctl_table_verity))
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/loadpin_sysctl_path +404 security/loadpin/loadpin.c
395
396 static int __init loadpin_init(void)
397 {
398 pr_info("ready to pin (currently %senforcing)\n",
399 enforce ? "" : "not ");
400 parse_exclude();
401 security_add_hooks(loadpin_hooks, ARRAY_SIZE(loadpin_hooks), "loadpin");
402
403 if (IS_ENABLED(CONFIG_SECURITY_LOADPIN_VERITY)) {
> 404 if (!register_sysctl_paths(loadpin_sysctl_path,
> 405 loadpin_sysctl_table_verity))
406 pr_notice("sysctl registration failed!\n");
407 }
408
409 return 0;
410 }
411
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-04-19 4:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 21:15 [PATCH 0/3] LoadPin: Enable loading from trusted dm-verity devices Matthias Kaehlcke
2022-04-18 21:15 ` [PATCH 1/3] dm: Add verity helpers for LoadPin Matthias Kaehlcke
2022-04-18 21:15 ` [PATCH 2/3] LoadPin: Enable loading from trusted dm-verity devices Matthias Kaehlcke
2022-04-19 4:32 ` kernel test robot [this message]
2022-04-18 21:15 ` [PATCH 3/3] dm: verity-loadpin: Use CONFIG_SECURITY_LOADPIN_VERITY for conditional compilation Matthias Kaehlcke
2022-04-18 22:14 ` [PATCH 0/3] LoadPin: Enable loading from trusted dm-verity devices Kees Cook
2022-04-18 22:43 ` Matthias Kaehlcke
2022-04-19 2:33 ` 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=202204191222.n0HWtNe0-lkp@intel.com \
--to=lkp@intel.com \
--cc=agk@redhat.com \
--cc=dianders@chromium.org \
--cc=dm-devel@redhat.com \
--cc=jmorris@namei.org \
--cc=kbuild-all@lists.01.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mka@chromium.org \
--cc=serge@hallyn.com \
--cc=snitzer@kernel.org \
--cc=song@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;
as well as URLs for NNTP newsgroup(s).