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: Douglas Anderson <dianders@chromium.org>,
kbuild-all@lists.01.org, dm-devel@redhat.com,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
Song Liu <song@kernel.org>,
linux-security-module@vger.kernel.org,
Matthias Kaehlcke <mka@chromium.org>
Subject: Re: [dm-devel] [PATCH v4 2/3] LoadPin: Enable loading from trusted dm-verity devices
Date: Wed, 18 May 2022 16:58:06 +0800 [thread overview]
Message-ID: <202205181616.3eTP2DaC-lkp@intel.com> (raw)
In-Reply-To: <20220517163437.v4.2.I01c67af41d2f6525c6d023101671d7339a9bc8b5@changeid>
Hi Matthias,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on device-mapper-dm/for-next]
[also build test WARNING on song-md/md-next kees/for-next/pstore linus/master v5.18-rc7 next-20220517]
[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/20220518-073635
base: https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20220518/202205181616.3eTP2DaC-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 11.3.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/755e5d82e4d054b2b58a54c94681080cc8cb4582
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/20220518-073635
git checkout 755e5d82e4d054b2b58a54c94681080cc8cb4582
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=m68k 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 warnings (new ones prefixed by >>):
In file included from security/loadpin/loadpin.c:21:
include/linux/dm-verity-loadpin.h:22:1: error: expected identifier or '(' before '{' token
22 | {
| ^
>> include/linux/dm-verity-loadpin.h:21:20: warning: 'dm_verity_loadpin_is_sb_trusted' used but never defined
21 | static inline bool dm_verity_loadpin_is_sb_trusted(struct super_block *sb);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/dm_verity_loadpin_is_sb_trusted +21 include/linux/dm-verity-loadpin.h
afd03270f57b8c Matthias Kaehlcke 2022-05-17 17
afd03270f57b8c Matthias Kaehlcke 2022-05-17 18 #if IS_ENABLED(CONFIG_SECURITY_LOADPIN) && IS_BUILTIN(CONFIG_DM_VERITY)
afd03270f57b8c Matthias Kaehlcke 2022-05-17 19 bool dm_verity_loadpin_is_sb_trusted(struct super_block *sb);
afd03270f57b8c Matthias Kaehlcke 2022-05-17 20 #else
afd03270f57b8c Matthias Kaehlcke 2022-05-17 @21 static inline bool dm_verity_loadpin_is_sb_trusted(struct super_block *sb);
afd03270f57b8c Matthias Kaehlcke 2022-05-17 @22 {
afd03270f57b8c Matthias Kaehlcke 2022-05-17 23 return false;
afd03270f57b8c Matthias Kaehlcke 2022-05-17 24 }
afd03270f57b8c Matthias Kaehlcke 2022-05-17 25 #endif
afd03270f57b8c Matthias Kaehlcke 2022-05-17 26
--
0-DAY CI Kernel Test Service
https://01.org/lkp
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
WARNING: multiple messages have this Message-ID (diff)
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-security-module@vger.kernel.org,
dm-devel@redhat.com, linux-kernel@vger.kernel.org,
linux-raid@vger.kernel.org, Song Liu <song@kernel.org>,
Douglas Anderson <dianders@chromium.org>,
Matthias Kaehlcke <mka@chromium.org>
Subject: Re: [PATCH v4 2/3] LoadPin: Enable loading from trusted dm-verity devices
Date: Wed, 18 May 2022 16:58:06 +0800 [thread overview]
Message-ID: <202205181616.3eTP2DaC-lkp@intel.com> (raw)
In-Reply-To: <20220517163437.v4.2.I01c67af41d2f6525c6d023101671d7339a9bc8b5@changeid>
Hi Matthias,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on device-mapper-dm/for-next]
[also build test WARNING on song-md/md-next kees/for-next/pstore linus/master v5.18-rc7 next-20220517]
[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/20220518-073635
base: https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20220518/202205181616.3eTP2DaC-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 11.3.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/755e5d82e4d054b2b58a54c94681080cc8cb4582
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/20220518-073635
git checkout 755e5d82e4d054b2b58a54c94681080cc8cb4582
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=m68k 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 warnings (new ones prefixed by >>):
In file included from security/loadpin/loadpin.c:21:
include/linux/dm-verity-loadpin.h:22:1: error: expected identifier or '(' before '{' token
22 | {
| ^
>> include/linux/dm-verity-loadpin.h:21:20: warning: 'dm_verity_loadpin_is_sb_trusted' used but never defined
21 | static inline bool dm_verity_loadpin_is_sb_trusted(struct super_block *sb);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/dm_verity_loadpin_is_sb_trusted +21 include/linux/dm-verity-loadpin.h
afd03270f57b8c Matthias Kaehlcke 2022-05-17 17
afd03270f57b8c Matthias Kaehlcke 2022-05-17 18 #if IS_ENABLED(CONFIG_SECURITY_LOADPIN) && IS_BUILTIN(CONFIG_DM_VERITY)
afd03270f57b8c Matthias Kaehlcke 2022-05-17 19 bool dm_verity_loadpin_is_sb_trusted(struct super_block *sb);
afd03270f57b8c Matthias Kaehlcke 2022-05-17 20 #else
afd03270f57b8c Matthias Kaehlcke 2022-05-17 @21 static inline bool dm_verity_loadpin_is_sb_trusted(struct super_block *sb);
afd03270f57b8c Matthias Kaehlcke 2022-05-17 @22 {
afd03270f57b8c Matthias Kaehlcke 2022-05-17 23 return false;
afd03270f57b8c Matthias Kaehlcke 2022-05-17 24 }
afd03270f57b8c Matthias Kaehlcke 2022-05-17 25 #endif
afd03270f57b8c Matthias Kaehlcke 2022-05-17 26
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-05-18 8:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 23:34 [dm-devel] [PATCH v4 0/3] LoadPin: Enable loading from trusted dm-verity devices Matthias Kaehlcke
2022-05-17 23:34 ` Matthias Kaehlcke
2022-05-17 23:34 ` [dm-devel] [PATCH v4 1/3] dm: Add verity helpers for LoadPin Matthias Kaehlcke
2022-05-17 23:34 ` Matthias Kaehlcke
2022-05-18 7:57 ` [dm-devel] " Milan Broz
2022-05-18 7:57 ` Milan Broz
2022-05-18 15:13 ` Matthias Kaehlcke
2022-05-18 15:13 ` Matthias Kaehlcke
2022-05-18 20:03 ` Mike Snitzer
2022-05-18 20:03 ` Mike Snitzer
2022-05-18 20:34 ` [dm-devel] " Matthias Kaehlcke
2022-05-18 20:34 ` Matthias Kaehlcke
2022-05-18 19:52 ` [dm-devel] " Mike Snitzer
2022-05-18 19:52 ` Mike Snitzer
2022-05-18 20:35 ` [dm-devel] " Matthias Kaehlcke
2022-05-18 20:35 ` Matthias Kaehlcke
2022-05-17 23:34 ` [dm-devel] [PATCH v4 2/3] LoadPin: Enable loading from trusted dm-verity devices Matthias Kaehlcke
2022-05-17 23:34 ` Matthias Kaehlcke
2022-05-18 8:58 ` kernel test robot [this message]
2022-05-18 8:58 ` kernel test robot
2022-05-18 14:40 ` [dm-devel] " Matthias Kaehlcke
2022-05-18 14:40 ` Matthias Kaehlcke
2022-05-18 14:40 ` Matthias Kaehlcke
2022-05-18 12:40 ` [dm-devel] " kernel test robot
2022-05-18 12:40 ` kernel test robot
2022-05-17 23:34 ` [dm-devel] [PATCH v4 3/3] dm: verity-loadpin: Use CONFIG_SECURITY_LOADPIN_VERITY for conditional compilation Matthias Kaehlcke
2022-05-17 23:34 ` Matthias Kaehlcke
2022-05-18 19:23 ` [dm-devel] [PATCH v4 0/3] LoadPin: Enable loading from trusted dm-verity devices Kees Cook
2022-05-18 19:23 ` Kees Cook
2022-05-18 19:43 ` [dm-devel] " Mike Snitzer
2022-05-18 19:43 ` Mike Snitzer
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=202205181616.3eTP2DaC-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 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.