From: kernel test robot <lkp@intel.com>
To: Olga Kornievskaia <olga.kornievskaia@gmail.com>,
trond.myklebust@hammerspace.com, anna.schumaker@netapp.com
Cc: kbuild-all@lists.01.org, linux-nfs@vger.kernel.org,
linux-security-module@vger.kernel.org, selinux@vger.kernel.org
Subject: Re: [PATCH 2/2] NFSv4 account for selinux security context when deciding to share superblock
Date: Sat, 13 Feb 2021 08:16:11 +0800 [thread overview]
Message-ID: <202102130833.ebOyrcK5-lkp@intel.com> (raw)
In-Reply-To: <20210212211955.11239-2-olga.kornievskaia@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2819 bytes --]
Hi Olga,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on nfs/linux-next]
[also build test ERROR on pcmoore-selinux/next linus/master security/next-testing v5.11-rc7 next-20210211]
[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/Olga-Kornievskaia/Add-new-hook-to-compare-new-mount-to-an-existing-mount/20210213-052321
base: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
config: arm-defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 9.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/0day-ci/linux/commit/ff69e0bcc99716695e11ed2741b2e01d6014f960
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Olga-Kornievskaia/Add-new-hook-to-compare-new-mount-to-an-existing-mount/20210213-052321
git checkout ff69e0bcc99716695e11ed2741b2e01d6014f960
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm
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 >>):
fs/nfs/super.c: In function 'nfs_compare_super':
>> fs/nfs/super.c:1179:5: error: implicit declaration of function 'security_sb_do_mnt_opts_match'; did you mean 'security_sb_set_mnt_opts'? [-Werror=implicit-function-declaration]
1179 | !security_sb_do_mnt_opts_match(sb, fc->security))
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| security_sb_set_mnt_opts
cc1: some warnings being treated as errors
vim +1179 fs/nfs/super.c
1164
1165 static int nfs_compare_super(struct super_block *sb, struct fs_context *fc)
1166 {
1167 struct nfs_server *server = fc->s_fs_info, *old = NFS_SB(sb);
1168
1169 if (!nfs_compare_super_address(old, server))
1170 return 0;
1171 /* Note: NFS_MOUNT_UNSHARED == NFS4_MOUNT_UNSHARED */
1172 if (old->flags & NFS_MOUNT_UNSHARED)
1173 return 0;
1174 if (memcmp(&old->fsid, &server->fsid, sizeof(old->fsid)) != 0)
1175 return 0;
1176 if (!nfs_compare_userns(old, server))
1177 return 0;
1178 if ((old->has_sec_mnt_opts || fc->security) &&
> 1179 !security_sb_do_mnt_opts_match(sb, fc->security))
1180 return 0;
1181 return nfs_compare_mount_options(sb, server, fc);
1182 }
1183
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 54163 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 2/2] NFSv4 account for selinux security context when deciding to share superblock
Date: Sat, 13 Feb 2021 08:16:11 +0800 [thread overview]
Message-ID: <202102130833.ebOyrcK5-lkp@intel.com> (raw)
In-Reply-To: <20210212211955.11239-2-olga.kornievskaia@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2884 bytes --]
Hi Olga,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on nfs/linux-next]
[also build test ERROR on pcmoore-selinux/next linus/master security/next-testing v5.11-rc7 next-20210211]
[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/Olga-Kornievskaia/Add-new-hook-to-compare-new-mount-to-an-existing-mount/20210213-052321
base: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
config: arm-defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 9.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/0day-ci/linux/commit/ff69e0bcc99716695e11ed2741b2e01d6014f960
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Olga-Kornievskaia/Add-new-hook-to-compare-new-mount-to-an-existing-mount/20210213-052321
git checkout ff69e0bcc99716695e11ed2741b2e01d6014f960
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm
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 >>):
fs/nfs/super.c: In function 'nfs_compare_super':
>> fs/nfs/super.c:1179:5: error: implicit declaration of function 'security_sb_do_mnt_opts_match'; did you mean 'security_sb_set_mnt_opts'? [-Werror=implicit-function-declaration]
1179 | !security_sb_do_mnt_opts_match(sb, fc->security))
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| security_sb_set_mnt_opts
cc1: some warnings being treated as errors
vim +1179 fs/nfs/super.c
1164
1165 static int nfs_compare_super(struct super_block *sb, struct fs_context *fc)
1166 {
1167 struct nfs_server *server = fc->s_fs_info, *old = NFS_SB(sb);
1168
1169 if (!nfs_compare_super_address(old, server))
1170 return 0;
1171 /* Note: NFS_MOUNT_UNSHARED == NFS4_MOUNT_UNSHARED */
1172 if (old->flags & NFS_MOUNT_UNSHARED)
1173 return 0;
1174 if (memcmp(&old->fsid, &server->fsid, sizeof(old->fsid)) != 0)
1175 return 0;
1176 if (!nfs_compare_userns(old, server))
1177 return 0;
1178 if ((old->has_sec_mnt_opts || fc->security) &&
> 1179 !security_sb_do_mnt_opts_match(sb, fc->security))
1180 return 0;
1181 return nfs_compare_mount_options(sb, server, fc);
1182 }
1183
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 54163 bytes --]
next prev parent reply other threads:[~2021-02-13 0:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 21:19 [PATCH 1/2] [security] Add new hook to compare new mount to an existing mount Olga Kornievskaia
2021-02-12 21:19 ` [PATCH 2/2] NFSv4 account for selinux security context when deciding to share superblock Olga Kornievskaia
2021-02-13 0:10 ` kernel test robot
2021-02-13 0:10 ` kernel test robot
2021-02-13 0:16 ` kernel test robot [this message]
2021-02-13 0:16 ` kernel test robot
2021-02-12 22:36 ` [PATCH 1/2] [security] Add new hook to compare new mount to an existing mount Casey Schaufler
2021-02-12 22:50 ` Olga Kornievskaia
2021-02-13 0:32 ` Casey Schaufler
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=202102130833.ebOyrcK5-lkp@intel.com \
--to=lkp@intel.com \
--cc=anna.schumaker@netapp.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=olga.kornievskaia@gmail.com \
--cc=selinux@vger.kernel.org \
--cc=trond.myklebust@hammerspace.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.