From: kernel test robot <lkp@intel.com> To: Stefan Berger <stefanb@linux.ibm.com>, linux-integrity@vger.kernel.org Cc: kbuild-all@lists.01.org, zohar@linux.ibm.com, serge@hallyn.com, christian.brauner@ubuntu.com, containers@lists.linux.dev, dmitry.kasatkin@gmail.com, ebiederm@xmission.com, krzysztof.struczynski@huawei.com, roberto.sassu@huawei.com, mpeters@redhat.com Subject: Re: [PATCH v5 01/16] ima: Add IMA namespace support Date: Sat, 11 Dec 2021 00:00:06 +0800 [thread overview] Message-ID: <202112102358.AmVci5Ag-lkp@intel.com> (raw) In-Reply-To: <20211208221818.1519628-2-stefanb@linux.ibm.com> Hi Stefan, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on zohar-integrity/next-integrity] [also build test WARNING on linux/master linus/master v5.16-rc4 next-20211208] [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/Stefan-Berger/ima-Namespace-IMA-with-audit-support-in-IMA-ns/20211209-062017 base: https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git next-integrity config: i386-randconfig-s031-20211207 (https://download.01.org/0day-ci/archive/20211210/202112102358.AmVci5Ag-lkp@intel.com/config) compiler: gcc-9 (Debian 9.3.0-22) 9.3.0 reproduce: # apt-get install sparse # sparse version: v0.6.4-dirty # https://github.com/0day-ci/linux/commit/0e5d16c2da02e9c61692836edf0b6f7f227e1867 git remote add linux-review https://github.com/0day-ci/linux git fetch --no-tags linux-review Stefan-Berger/ima-Namespace-IMA-with-audit-support-in-IMA-ns/20211209-062017 git checkout 0e5d16c2da02e9c61692836edf0b6f7f227e1867 # save the config file to linux build tree mkdir build_dir make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash If you fix the issue, kindly add following tag as appropriate Reported-by: kernel test robot <lkp@intel.com> sparse warnings: (new ones prefixed by >>) drivers/md/dm-ioctl.c: note: in included file: >> include/linux/ima.h:263:5: sparse: sparse: undefined preprocessor identifier 'CONFIG_IMA' -- fs/open.c: note: in included file: >> include/linux/ima.h:263:5: sparse: sparse: undefined preprocessor identifier 'CONFIG_IMA' fs/open.c:1011:21: sparse: sparse: restricted fmode_t degrades to integer -- fs/file_table.c: note: in included file: >> include/linux/ima.h:263:5: sparse: sparse: undefined preprocessor identifier 'CONFIG_IMA' -- fs/namei.c: note: in included file: >> include/linux/ima.h:263:5: sparse: sparse: undefined preprocessor identifier 'CONFIG_IMA' fs/namei.c:680:17: sparse: sparse: context imbalance in 'terminate_walk' - unexpected unlock fs/namei.c: note: in included file (through include/linux/rbtree.h, include/linux/mm_types.h, include/linux/mmzone.h, ...): include/linux/rcupdate.h:718:9: sparse: sparse: context imbalance in 'try_to_unlazy' - unexpected unlock include/linux/rcupdate.h:718:9: sparse: sparse: context imbalance in 'try_to_unlazy_next' - unexpected unlock fs/namei.c:2318:19: sparse: sparse: context imbalance in 'path_init' - different lock contexts for basic block -- fs/attr.c: note: in included file: >> include/linux/ima.h:263:5: sparse: sparse: undefined preprocessor identifier 'CONFIG_IMA' -- security/security.c: note: in included file: >> include/linux/ima.h:263:5: sparse: sparse: undefined preprocessor identifier 'CONFIG_IMA' security/security.c:358:25: sparse: sparse: cast removes address space '__rcu' of expression -- security/keys/key.c: note: in included file: >> include/linux/ima.h:263:5: sparse: sparse: undefined preprocessor identifier 'CONFIG_IMA' security/keys/key.c:123:17: sparse: sparse: context imbalance in 'key_user_put' - unexpected unlock vim +/CONFIG_IMA +263 include/linux/ima.h 260 261 static inline int create_ima_ns(struct user_namespace *user_ns) 262 { > 263 #if CONFIG_IMA 264 user_ns->ima_ns = get_ima_ns(&init_ima_ns); 265 #endif 266 return 0; 267 } 268 --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com> To: kbuild-all@lists.01.org Subject: Re: [PATCH v5 01/16] ima: Add IMA namespace support Date: Sat, 11 Dec 2021 00:00:06 +0800 [thread overview] Message-ID: <202112102358.AmVci5Ag-lkp@intel.com> (raw) In-Reply-To: <20211208221818.1519628-2-stefanb@linux.ibm.com> [-- Attachment #1: Type: text/plain, Size: 3798 bytes --] Hi Stefan, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on zohar-integrity/next-integrity] [also build test WARNING on linux/master linus/master v5.16-rc4 next-20211208] [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/Stefan-Berger/ima-Namespace-IMA-with-audit-support-in-IMA-ns/20211209-062017 base: https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git next-integrity config: i386-randconfig-s031-20211207 (https://download.01.org/0day-ci/archive/20211210/202112102358.AmVci5Ag-lkp(a)intel.com/config) compiler: gcc-9 (Debian 9.3.0-22) 9.3.0 reproduce: # apt-get install sparse # sparse version: v0.6.4-dirty # https://github.com/0day-ci/linux/commit/0e5d16c2da02e9c61692836edf0b6f7f227e1867 git remote add linux-review https://github.com/0day-ci/linux git fetch --no-tags linux-review Stefan-Berger/ima-Namespace-IMA-with-audit-support-in-IMA-ns/20211209-062017 git checkout 0e5d16c2da02e9c61692836edf0b6f7f227e1867 # save the config file to linux build tree mkdir build_dir make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash If you fix the issue, kindly add following tag as appropriate Reported-by: kernel test robot <lkp@intel.com> sparse warnings: (new ones prefixed by >>) drivers/md/dm-ioctl.c: note: in included file: >> include/linux/ima.h:263:5: sparse: sparse: undefined preprocessor identifier 'CONFIG_IMA' -- fs/open.c: note: in included file: >> include/linux/ima.h:263:5: sparse: sparse: undefined preprocessor identifier 'CONFIG_IMA' fs/open.c:1011:21: sparse: sparse: restricted fmode_t degrades to integer -- fs/file_table.c: note: in included file: >> include/linux/ima.h:263:5: sparse: sparse: undefined preprocessor identifier 'CONFIG_IMA' -- fs/namei.c: note: in included file: >> include/linux/ima.h:263:5: sparse: sparse: undefined preprocessor identifier 'CONFIG_IMA' fs/namei.c:680:17: sparse: sparse: context imbalance in 'terminate_walk' - unexpected unlock fs/namei.c: note: in included file (through include/linux/rbtree.h, include/linux/mm_types.h, include/linux/mmzone.h, ...): include/linux/rcupdate.h:718:9: sparse: sparse: context imbalance in 'try_to_unlazy' - unexpected unlock include/linux/rcupdate.h:718:9: sparse: sparse: context imbalance in 'try_to_unlazy_next' - unexpected unlock fs/namei.c:2318:19: sparse: sparse: context imbalance in 'path_init' - different lock contexts for basic block -- fs/attr.c: note: in included file: >> include/linux/ima.h:263:5: sparse: sparse: undefined preprocessor identifier 'CONFIG_IMA' -- security/security.c: note: in included file: >> include/linux/ima.h:263:5: sparse: sparse: undefined preprocessor identifier 'CONFIG_IMA' security/security.c:358:25: sparse: sparse: cast removes address space '__rcu' of expression -- security/keys/key.c: note: in included file: >> include/linux/ima.h:263:5: sparse: sparse: undefined preprocessor identifier 'CONFIG_IMA' security/keys/key.c:123:17: sparse: sparse: context imbalance in 'key_user_put' - unexpected unlock vim +/CONFIG_IMA +263 include/linux/ima.h 260 261 static inline int create_ima_ns(struct user_namespace *user_ns) 262 { > 263 #if CONFIG_IMA 264 user_ns->ima_ns = get_ima_ns(&init_ima_ns); 265 #endif 266 return 0; 267 } 268 --- 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:[~2021-12-10 16:01 UTC|newest] Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-08 22:18 [PATCH v5 00/16] ima: Namespace IMA with audit support in IMA-ns Stefan Berger 2021-12-08 22:18 ` [PATCH v5 01/16] ima: Add IMA namespace support Stefan Berger 2021-12-09 4:40 ` kernel test robot 2021-12-09 4:40 ` kernel test robot 2021-12-09 10:56 ` kernel test robot 2021-12-09 10:56 ` kernel test robot 2021-12-09 13:19 ` kernel test robot 2021-12-09 13:19 ` kernel test robot 2021-12-10 16:00 ` kernel test robot [this message] 2021-12-10 16:00 ` kernel test robot 2021-12-08 22:18 ` [PATCH v5 02/16] ima: Define ns_status for storing namespaced iint data Stefan Berger 2021-12-08 22:18 ` [PATCH v5 03/16] ima: Namespace audit status flags Stefan Berger 2021-12-08 22:18 ` [PATCH v5 04/16] ima: Move delayed work queue and variables into ima_namespace Stefan Berger 2021-12-09 13:11 ` Christian Brauner 2021-12-09 15:09 ` Stefan Berger 2021-12-08 22:18 ` [PATCH v5 05/16] ima: Move IMA's keys queue related " Stefan Berger 2021-12-08 22:18 ` [PATCH v5 06/16] ima: Move policy " Stefan Berger 2021-12-08 22:18 ` [PATCH v5 07/16] ima: Move ima_htable " Stefan Berger 2021-12-09 16:26 ` kernel test robot 2021-12-09 16:26 ` kernel test robot 2021-12-08 22:18 ` [PATCH v5 08/16] ima: Move measurement list related variables " Stefan Berger 2021-12-08 22:18 ` [PATCH v5 09/16] ima: Only accept AUDIT rules for IMA non-init_ima_ns namespaces for now Stefan Berger 2021-12-08 22:18 ` [PATCH v5 10/16] ima: Implement hierarchical processing of file accesses Stefan Berger 2021-12-08 22:18 ` [PATCH v5 11/16] securityfs: Only use simple_pin_fs/simple_release_fs for init_user_ns Stefan Berger 2021-12-08 22:18 ` [PATCH v5 12/16] securityfs: Extend securityfs with namespacing support Stefan Berger 2021-12-08 22:18 ` [PATCH v5 13/16] ima: Move some IMA policy and filesystem related variables into ima_namespace Stefan Berger 2021-12-09 19:11 ` Christian Brauner 2021-12-09 20:42 ` Stefan Berger 2021-12-10 0:57 ` Stefan Berger 2021-12-10 11:32 ` Christian Brauner 2021-12-10 13:57 ` Stefan Berger 2021-12-10 14:21 ` James Bottomley 2021-12-11 9:50 ` Christian Brauner 2021-12-11 10:45 ` Christian Brauner 2021-12-13 15:33 ` Stefan Berger 2021-12-13 15:50 ` Christian Brauner 2021-12-13 16:03 ` Christian Brauner 2021-12-13 16:25 ` Stefan Berger 2021-12-13 16:37 ` Christian Brauner 2021-12-13 16:40 ` Christian Brauner 2021-12-10 20:08 ` Stefan Berger 2021-12-11 8:46 ` Christian Brauner 2021-12-08 22:18 ` [PATCH v5 14/16] ima: Use mac_admin_ns_capable() to check corresponding capability Stefan Berger 2021-12-09 7:22 ` Denis Semakin 2021-12-09 13:23 ` James Bottomley 2021-12-09 8:09 ` Denis Semakin 2021-12-11 15:02 ` Serge E. Hallyn 2021-12-11 15:38 ` Stefan Berger 2021-12-11 16:00 ` James Bottomley 2021-12-08 22:18 ` [PATCH v5 15/16] ima: Move dentries into ima_namespace Stefan Berger 2021-12-09 14:34 ` Christian Brauner 2021-12-09 14:37 ` Christian Brauner 2021-12-09 14:41 ` Christian Brauner 2021-12-09 15:00 ` Stefan Berger 2021-12-09 15:47 ` Christian Brauner 2021-12-09 15:30 ` James Bottomley 2021-12-09 19:38 ` James Bottomley 2021-12-09 20:13 ` Stefan Berger 2021-12-10 11:49 ` Christian Brauner 2021-12-10 12:09 ` Mimi Zohar 2021-12-10 12:40 ` Stefan Berger 2021-12-10 13:02 ` Mimi Zohar 2021-12-10 14:17 ` Stefan Berger 2021-12-10 14:26 ` James Bottomley 2021-12-10 15:26 ` Mimi Zohar 2021-12-10 15:32 ` Stefan Berger 2021-12-10 15:48 ` Mimi Zohar 2021-12-10 16:40 ` Stefan Berger 2021-12-10 12:40 ` James Bottomley 2021-12-10 12:54 ` Mimi Zohar 2021-12-12 14:13 ` James Bottomley 2021-12-13 11:25 ` Christian Brauner 2021-12-08 22:18 ` [PATCH v5 16/16] ima: Setup securityfs for IMA namespace Stefan Berger
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=202112102358.AmVci5Ag-lkp@intel.com \ --to=lkp@intel.com \ --cc=christian.brauner@ubuntu.com \ --cc=containers@lists.linux.dev \ --cc=dmitry.kasatkin@gmail.com \ --cc=ebiederm@xmission.com \ --cc=kbuild-all@lists.01.org \ --cc=krzysztof.struczynski@huawei.com \ --cc=linux-integrity@vger.kernel.org \ --cc=mpeters@redhat.com \ --cc=roberto.sassu@huawei.com \ --cc=serge@hallyn.com \ --cc=stefanb@linux.ibm.com \ --cc=zohar@linux.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: linkBe 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.