All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Stefan Berger <stefanb@linux.ibm.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [RFC v2 19/19] ima: Setup securityfs for IMA namespace
Date: Fri, 3 Dec 2021 19:04:59 +0800	[thread overview]
Message-ID: <202112031932.qCorYl4u-lkp@intel.com> (raw)
In-Reply-To: <20211203023118.1447229-20-stefanb@linux.ibm.com>

Hi Stefan,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on zohar-integrity/next-integrity]
[also build test ERROR on linus/master v5.16-rc3]
[cannot apply to pcmoore-selinux/next next-20211203]
[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/20211203-103412
base:   https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git next-integrity
config: mips-buildonly-randconfig-r002-20211203 (https://download.01.org/0day-ci/archive/20211203/202112031932.qCorYl4u-lkp@intel.com/config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 1e328b06c15273edf4a40a27ca24931b5efb3a87)
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
        # install mips cross compiling tool for clang build
        # apt-get install binutils-mips-linux-gnu
        # https://github.com/0day-ci/linux/commit/8766e0181c2639c814f7391feaa411d8c767e37b
        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/20211203-103412
        git checkout 8766e0181c2639c814f7391feaa411d8c767e37b
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=mips SHELL=/bin/bash

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/inode.c:69:19: error: no member named 'ima_ns' in 'struct user_namespace'
           if (fc->user_ns->ima_ns->late_fs_init) {
               ~~~~~~~~~~~  ^
   security/inode.c:70:21: error: no member named 'ima_ns' in 'struct user_namespace'
                   rc = fc->user_ns->ima_ns->late_fs_init(fc->user_ns);
                        ~~~~~~~~~~~  ^
   2 errors generated.


vim +69 security/inode.c

    64	
    65	static int securityfs_init_fs_context(struct fs_context *fc)
    66	{
    67		int rc;
    68	
  > 69		if (fc->user_ns->ima_ns->late_fs_init) {
    70			rc = fc->user_ns->ima_ns->late_fs_init(fc->user_ns);
    71			if (rc)
    72				return rc;
    73		}
    74		fc->ops = &securityfs_context_ops;
    75		return 0;
    76	}
    77	

---
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: [RFC v2 19/19] ima: Setup securityfs for IMA namespace
Date: Fri, 03 Dec 2021 19:04:59 +0800	[thread overview]
Message-ID: <202112031932.qCorYl4u-lkp@intel.com> (raw)
In-Reply-To: <20211203023118.1447229-20-stefanb@linux.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 2786 bytes --]

Hi Stefan,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on zohar-integrity/next-integrity]
[also build test ERROR on linus/master v5.16-rc3]
[cannot apply to pcmoore-selinux/next next-20211203]
[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/20211203-103412
base:   https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git next-integrity
config: mips-buildonly-randconfig-r002-20211203 (https://download.01.org/0day-ci/archive/20211203/202112031932.qCorYl4u-lkp(a)intel.com/config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 1e328b06c15273edf4a40a27ca24931b5efb3a87)
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
        # install mips cross compiling tool for clang build
        # apt-get install binutils-mips-linux-gnu
        # https://github.com/0day-ci/linux/commit/8766e0181c2639c814f7391feaa411d8c767e37b
        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/20211203-103412
        git checkout 8766e0181c2639c814f7391feaa411d8c767e37b
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=mips SHELL=/bin/bash

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/inode.c:69:19: error: no member named 'ima_ns' in 'struct user_namespace'
           if (fc->user_ns->ima_ns->late_fs_init) {
               ~~~~~~~~~~~  ^
   security/inode.c:70:21: error: no member named 'ima_ns' in 'struct user_namespace'
                   rc = fc->user_ns->ima_ns->late_fs_init(fc->user_ns);
                        ~~~~~~~~~~~  ^
   2 errors generated.


vim +69 security/inode.c

    64	
    65	static int securityfs_init_fs_context(struct fs_context *fc)
    66	{
    67		int rc;
    68	
  > 69		if (fc->user_ns->ima_ns->late_fs_init) {
    70			rc = fc->user_ns->ima_ns->late_fs_init(fc->user_ns);
    71			if (rc)
    72				return rc;
    73		}
    74		fc->ops = &securityfs_context_ops;
    75		return 0;
    76	}
    77	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

  reply	other threads:[~2021-12-03 11:05 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-03  2:30 [RFC v2 00/19] ima: Namespace IMA with audit support in IMA-ns Stefan Berger
2021-12-03  2:31 ` [RFC v2 01/19] ima: Add IMA namespace support Stefan Berger
2021-12-03  2:31 ` [RFC v2 02/19] ima: Define ns_status for storing namespaced iint data Stefan Berger
2021-12-03  2:31 ` [RFC v2 03/19] ima: Namespace audit status flags Stefan Berger
2021-12-03  2:31 ` [RFC v2 04/19] ima: Move delayed work queue and variables into ima_namespace Stefan Berger
2021-12-03  2:31 ` [RFC v2 05/19] ima: Move IMA's keys queue related " Stefan Berger
2021-12-03  2:31 ` [RFC v2 06/19] ima: Move policy " Stefan Berger
2021-12-03 16:50   ` kernel test robot
2021-12-03  2:31 ` [RFC v2 07/19] ima: Move ima_htable " Stefan Berger
2021-12-03  2:31 ` [RFC v2 08/19] ima: Move measurement list related variables " Stefan Berger
2021-12-03  2:31 ` [RFC v2 09/19] ima: Only accept AUDIT rules for IMA non-init_ima_ns namespaces for now Stefan Berger
2021-12-03  2:31 ` [RFC v2 10/19] ima: Implement hierarchical processing of file accesses Stefan Berger
2021-12-03  2:31 ` [RFC v2 11/19] securityfs: Prefix global variables with securityfs_ Stefan Berger
2021-12-03  2:31 ` [RFC v2 12/19] securityfs: Pass static variables as parameters from top level functions Stefan Berger
2021-12-03  2:31 ` [RFC v2 13/19] securityfs: Extend securityfs with namespacing support Stefan Berger
2021-12-03  2:31 ` [RFC v2 14/19] ima: Move some IMA policy and filesystem related variables into ima_namespace Stefan Berger
2021-12-03  2:31 ` [RFC v2 15/19] capabilities: Introduce CAP_INTEGRITY_ADMIN Stefan Berger
2021-12-03 16:40   ` Casey Schaufler
2021-12-03 17:39     ` Stefan Berger
2021-12-03  2:31 ` [RFC v2 16/19] ima: Use integrity_admin_ns_capable() to check corresponding capability Stefan Berger
2021-12-03  2:31 ` [RFC v2 17/19] userns: Introduce a refcount variable for calling early teardown function Stefan Berger
2021-12-03  2:31 ` [RFC v2 18/19] ima/userns: Define early teardown function for IMA namespace Stefan Berger
2021-12-03  2:31 ` [RFC v2 19/19] ima: Setup securityfs " Stefan Berger
2021-12-03 11:04   ` kernel test robot [this message]
2021-12-03 11:04     ` kernel test robot
2021-12-03 12:36   ` kernel test robot
2021-12-03 15:07   ` Stefan Berger
2021-12-03 17:03   ` James Bottomley
2021-12-03 18:06     ` Stefan Berger
2021-12-03 18:50       ` James Bottomley
2021-12-03 19:11         ` Stefan Berger
2021-12-04  0:33           ` Stefan Berger
2021-12-06 11:52             ` Christian Brauner
2021-12-06  4:27           ` James Bottomley
2021-12-06 14:03             ` Stefan Berger
2021-12-06 14:11               ` James Bottomley
2021-12-06 17:22                 ` Stefan Berger
2021-12-03 19:37         ` Casey Schaufler
2021-12-06 12:08           ` Christian Brauner
2021-12-06 13:38             ` James Bottomley
2021-12-06 14:13               ` Christian Brauner
2021-12-06 15:44               ` Christian Brauner
2021-12-06 16:25                 ` James Bottomley
2021-12-06 14:11       ` Christian Brauner
2021-12-06 14:21         ` James Bottomley
2021-12-06 14:42           ` Christian Brauner
2021-12-06 14:51             ` James Bottomley

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=202112031932.qCorYl4u-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=llvm@lists.linux.dev \
    --cc=stefanb@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: 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.