linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: kbuild-all@01.org, miklos@szeredi.hu, sds@tycho.nsa.gov,
	pmoore@redhat.com, casey@schaufler-ca.com,
	linux-kernel@vger.kernel.org, linux-unionfs@vger.kernel.org,
	linux-security-module@vger.kernel.org, dwalsh@redhat.com,
	dhowells@redhat.com, viro@ZenIV.linux.org.uk, vgoyal@redhat.com,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 3/7] security,overlayfs: Provide security hook for copy up of xattrs for overlay file
Date: Sat, 9 Jul 2016 01:41:38 +0800	[thread overview]
Message-ID: <201607090113.z0EuiSaT%fengguang.wu@intel.com> (raw)
In-Reply-To: <1467994782-26474-4-git-send-email-vgoyal@redhat.com>

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

Hi,

[auto build test ERROR on next-20160708]
[also build test ERROR on v4.7-rc6]
[cannot apply to pcmoore-selinux/next security/next v4.7-rc6 v4.7-rc5 v4.7-rc4]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Vivek-Goyal/Overlayfs-SELinux-Support/20160709-002635
config: mips-gpr_defconfig (attached as .config)
compiler: mips-linux-gnu-gcc (Debian 5.3.1-8) 5.3.1 20160205
reproduce:
        wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=mips 

All errors (new ones prefixed by >>):

   In file included from arch/mips/kernel/ptrace.c:27:0:
   include/linux/security.h: In function 'security_inode_copy_up_xattr':
>> include/linux/security.h:770:2: error: statement with no effect [-Werror=unused-value]
     -EOPNOTSUPP;
     ^
   include/linux/security.h:771:1: error: no return statement in function returning non-void [-Werror=return-type]
    }
    ^
   cc1: all warnings being treated as errors

vim +770 include/linux/security.h

   764	{
   765		return 0;
   766	}
   767	
   768	static inline int security_inode_copy_up_xattr(const char *name)
   769	{
 > 770		-EOPNOTSUPP;
   771	}
   772	
   773	static inline int security_file_permission(struct file *file, int mask)

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 7223 bytes --]

  reply	other threads:[~2016-07-08 17:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08 16:19 [RFC PATCH 0/7][V2] Overlayfs SELinux Support Vivek Goyal
2016-07-08 16:19 ` [PATCH 1/7] security, overlayfs: provide copy up security hook for unioned files Vivek Goyal
2016-07-11 15:24   ` Stephen Smalley
2016-07-11 16:54     ` Vivek Goyal
2016-07-08 16:19 ` [PATCH 2/7] selinux: Implementation for inode_copy_up() hook Vivek Goyal
2016-07-08 16:19 ` [PATCH 3/7] security,overlayfs: Provide security hook for copy up of xattrs for overlay file Vivek Goyal
2016-07-08 17:41   ` kbuild test robot [this message]
2016-07-11 13:40     ` Vivek Goyal
2016-07-11 13:50       ` [kbuild-all] [PATCH 3/7] security, overlayfs: " Fengguang Wu
2016-07-12  0:02       ` [PATCH 3/7] security,overlayfs: " Stephen Rothwell
2016-07-11 15:31   ` Stephen Smalley
2016-07-11 16:56     ` Vivek Goyal
2016-07-11 17:02     ` Vivek Goyal
2016-07-08 16:19 ` [PATCH 4/7] selinux: Implementation for inode_copy_up_xattr() hook Vivek Goyal
2016-07-08 16:19 ` [PATCH 5/7] selinux: Pass security pointer to determine_inode_label() Vivek Goyal
2016-07-08 16:19 ` [PATCH 6/7] security, overlayfs: Provide hook to correctly label newly created files Vivek Goyal
2016-07-08 16:19 ` [PATCH 7/7] selinux: Implement dentry_create_files_as() hook Vivek Goyal

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=201607090113.z0EuiSaT%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=casey@schaufler-ca.com \
    --cc=dhowells@redhat.com \
    --cc=dwalsh@redhat.com \
    --cc=kbuild-all@01.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=pmoore@redhat.com \
    --cc=sds@tycho.nsa.gov \
    --cc=vgoyal@redhat.com \
    --cc=viro@ZenIV.linux.org.uk \
    /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).