From: kbuild test robot <lkp@intel.com>
To: Mark Salyzyn <salyzyn@android.com>
Cc: Latchesar Ionkov <lucho@ionkov.net>,
Dave Kleikamp <shaggy@kernel.org>,
jfs-discussion@lists.sourceforge.net,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Martin Brandenburg <martin@omnibond.com>,
samba-technical@lists.samba.org,
Dominique Martinet <asmadeus@codewreck.org>,
Chao Yu <yuchao0@huawei.com>, Mimi Zohar <zohar@linux.ibm.com>,
linux-unionfs@vger.kernel.org,
David Howells <dhowells@redhat.com>, Chris Mason <clm@fb.com>,
"David S. Miller" <davem@davemloft.net>,
Andreas Dilger <adilger.kernel@dilger.ca>,
ocfs2-devel@oss.oracle.com, Eric Paris <eparis@parisplace.org>,
netdev@vger.kernel.org, Tyler Hicks <tyhicks@canonical.com>,
linux-afs@lists.infradead.org,
Mike Marshall <hubcap@omnibond.com>,
linux-xfs@vger.kernel.org, Sage Weil <sage@redhat.com>,
Miklos Szeredi <miklos@szeredi.hu>,
Richard Weinberger <richard@nod.at>,
Mark Fasheh <mark@fasheh.com>,
Hugh
Subject: Re: [PATCH] Add flags option to get xattr method paired to __vfs_getxattr
Date: Tue, 13 Aug 2019 16:28:45 +0800 [thread overview]
Message-ID: <201908131644.yb5jmvKK%lkp@intel.com> (raw)
In-Reply-To: <20190812193320.200472-1-salyzyn@android.com>
[-- Attachment #1: Type: text/plain, Size: 4149 bytes --]
Hi Mark,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[cannot apply to v5.3-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/Mark-Salyzyn/Add-flags-option-to-get-xattr-method-paired-to-__vfs_getxattr/20190813-124612
config: c6x-allyesconfig (attached as .config)
compiler: c6x-elf-gcc (GCC) 7.4.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=c6x
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> fs/ubifs/xattr.c:699:9: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
.get = xattr_get,
^~~~~~~~~
fs/ubifs/xattr.c:699:9: note: (near initialization for 'ubifs_user_xattr_handler.get')
fs/ubifs/xattr.c:705:9: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
.get = xattr_get,
^~~~~~~~~
fs/ubifs/xattr.c:705:9: note: (near initialization for 'ubifs_trusted_xattr_handler.get')
fs/ubifs/xattr.c:712:9: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
.get = xattr_get,
^~~~~~~~~
fs/ubifs/xattr.c:712:9: note: (near initialization for 'ubifs_security_xattr_handler.get')
cc1: some warnings being treated as errors
--
>> drivers/staging//erofs/xattr.c:492:9: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
.get = erofs_xattr_generic_get,
^~~~~~~~~~~~~~~~~~~~~~~
drivers/staging//erofs/xattr.c:492:9: note: (near initialization for 'erofs_xattr_user_handler.get')
drivers/staging//erofs/xattr.c:499:9: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
.get = erofs_xattr_generic_get,
^~~~~~~~~~~~~~~~~~~~~~~
drivers/staging//erofs/xattr.c:499:9: note: (near initialization for 'erofs_xattr_trusted_handler.get')
drivers/staging//erofs/xattr.c:506:9: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
.get = erofs_xattr_generic_get,
^~~~~~~~~~~~~~~~~~~~~~~
drivers/staging//erofs/xattr.c:506:9: note: (near initialization for 'erofs_xattr_security_handler.get')
cc1: some warnings being treated as errors
--
>> fs//afs/xattr.c:156:12: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
.get = afs_xattr_get_acl,
^~~~~~~~~~~~~~~~~
fs//afs/xattr.c:156:12: note: (near initialization for 'afs_xattr_afs_acl_handler.get')
fs//afs/xattr.c:327:9: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
.get = afs_xattr_get_yfs,
^~~~~~~~~~~~~~~~~
fs//afs/xattr.c:327:9: note: (near initialization for 'afs_xattr_yfs_handler.get')
cc1: some warnings being treated as errors
vim +699 fs/ubifs/xattr.c
2b88fc21cae91e Andreas Gruenbacher 2016-04-22 696
dfaf8d2aeca482 Ben Dooks 2016-06-21 697 static const struct xattr_handler ubifs_user_xattr_handler = {
2b88fc21cae91e Andreas Gruenbacher 2016-04-22 698 .prefix = XATTR_USER_PREFIX,
ade46c3a6029de Richard Weinberger 2016-09-19 @699 .get = xattr_get,
ade46c3a6029de Richard Weinberger 2016-09-19 700 .set = xattr_set,
2b88fc21cae91e Andreas Gruenbacher 2016-04-22 701 };
2b88fc21cae91e Andreas Gruenbacher 2016-04-22 702
:::::: The code at line 699 was first introduced by commit
:::::: ade46c3a6029dea49dbc6c7734b0f6a78d3f104c ubifs: Export xattr get and set functions
:::::: TO: Richard Weinberger <richard@nod.at>
:::::: CC: Richard Weinberger <richard@nod.at>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 49672 bytes --]
next prev parent reply other threads:[~2019-08-13 8:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 19:32 [PATCH] Add flags option to get xattr method paired to __vfs_getxattr Mark Salyzyn via Linux-f2fs-devel
2019-08-13 8:28 ` kbuild test robot [this message]
2019-08-13 8:48 ` Greg Kroah-Hartman
2019-08-13 14:37 ` Mark Salyzyn via Linux-f2fs-devel
2019-08-15 19:20 ` James Morris
2019-08-15 20:43 ` Greg Kroah-Hartman
2019-08-15 21:26 ` Mark Salyzyn
2019-08-15 22:27 ` James Morris
2019-08-16 15:30 ` Mark Salyzyn
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=201908131644.yb5jmvKK%lkp@intel.com \
--to=lkp@intel.com \
--cc=adilger.kernel@dilger.ca \
--cc=asmadeus@codewreck.org \
--cc=clm@fb.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=eparis@parisplace.org \
--cc=gregkh@linuxfoundation.org \
--cc=hubcap@omnibond.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-afs@lists.infradead.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=mark@fasheh.com \
--cc=martin@omnibond.com \
--cc=miklos@szeredi.hu \
--cc=netdev@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=richard@nod.at \
--cc=sage@redhat.com \
--cc=salyzyn@android.com \
--cc=samba-technical@lists.samba.org \
--cc=shaggy@kernel.org \
--cc=tyhicks@canonical.com \
--cc=yuchao0@huawei.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: 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