From: kbuild test robot <lkp@intel.com>
To: Benjamin Coddington <bcodding@redhat.com>
Cc: kbuild-all@01.org,
Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
Jeff Layton <jlayton@poochiereds.net>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH 2/3] NFS: add OFD lock owners to nfs_lock_context
Date: Sat, 2 Apr 2016 00:55:40 +0800 [thread overview]
Message-ID: <201604020001.YWWjB51w%fengguang.wu@intel.com> (raw)
In-Reply-To: <14db791eb1cde17ca9260cd09221b64f1f56a13f.1459512820.git.bcodding@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 4156 bytes --]
Hi Benjamin,
[auto build test ERROR on v4.6-rc1]
[also build test ERROR on next-20160401]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Benjamin-Coddington/Include-OFD-lock-owners-when-looking-up-state/20160401-233801
config: i386-randconfig-s0-201613 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
In file included from fs/nfs/inode.c:49:0:
fs/nfs/fscache.h: In function 'nfs_readpage_from_fscache':
>> fs/nfs/fscache.h:122:38: error: passing argument 1 of '__nfs_readpage_from_fscache' from incompatible pointer type [-Werror=incompatible-pointer-types]
return __nfs_readpage_from_fscache(l_ctx, inode, page);
^
fs/nfs/fscache.h:86:12: note: expected 'struct nfs_open_context *' but argument is of type 'struct nfs_lock_context *'
extern int __nfs_readpage_from_fscache(struct nfs_open_context *,
^
fs/nfs/fscache.h: In function 'nfs_readpages_from_fscache':
>> fs/nfs/fscache.h:136:39: error: passing argument 1 of '__nfs_readpages_from_fscache' from incompatible pointer type [-Werror=incompatible-pointer-types]
return __nfs_readpages_from_fscache(l_ctx, inode, mapping, pages,
^
fs/nfs/fscache.h:88:12: note: expected 'struct nfs_open_context *' but argument is of type 'struct nfs_lock_context *'
extern int __nfs_readpages_from_fscache(struct nfs_open_context *,
^
cc1: some warnings being treated as errors
--
In file included from fs/nfs/fscache-index.c:21:0:
fs/nfs/fscache.h: In function 'nfs_readpage_from_fscache':
>> fs/nfs/fscache.h:122:38: error: passing argument 1 of '__nfs_readpage_from_fscache' from incompatible pointer type [-Werror=incompatible-pointer-types]
return __nfs_readpage_from_fscache(l_ctx, inode, page);
^
fs/nfs/fscache.h:86:12: note: expected 'struct nfs_open_context *' but argument is of type 'struct nfs_lock_context *'
extern int __nfs_readpage_from_fscache(struct nfs_open_context *,
^
fs/nfs/fscache.h: In function 'nfs_readpages_from_fscache':
>> fs/nfs/fscache.h:136:39: error: passing argument 1 of '__nfs_readpages_from_fscache' from incompatible pointer type [-Werror=incompatible-pointer-types]
return __nfs_readpages_from_fscache(l_ctx, inode, mapping, pages,
^
fs/nfs/fscache.h:88:12: note: expected 'struct nfs_open_context *' but argument is of type 'struct nfs_lock_context *'
extern int __nfs_readpages_from_fscache(struct nfs_open_context *,
^
fs/nfs/fscache-index.c: In function 'nfs_fh_put_context':
fs/nfs/fscache-index.c:314:3: error: implicit declaration of function 'put_nfs_lock_context' [-Werror=implicit-function-declaration]
put_nfs_lock_context(context);
^
cc1: some warnings being treated as errors
vim +/__nfs_readpage_from_fscache +122 fs/nfs/fscache.h
116 */
117 static inline int nfs_readpage_from_fscache(struct nfs_lock_context *l_ctx,
118 struct inode *inode,
119 struct page *page)
120 {
121 if (NFS_I(inode)->fscache)
> 122 return __nfs_readpage_from_fscache(l_ctx, inode, page);
123 return -ENOBUFS;
124 }
125
126 /*
127 * Retrieve a set of pages from an inode data storage object.
128 */
129 static inline int nfs_readpages_from_fscache(struct nfs_lock_context *l_ctx,
130 struct inode *inode,
131 struct address_space *mapping,
132 struct list_head *pages,
133 unsigned *nr_pages)
134 {
135 if (NFS_I(inode)->fscache)
> 136 return __nfs_readpages_from_fscache(l_ctx, inode, mapping, pages,
137 nr_pages);
138 return -ENOBUFS;
139 }
---
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: 29360 bytes --]
next prev parent reply other threads:[~2016-04-01 16:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 15:34 [PATCH 0/3] Include OFD lock owners when looking up state Benjamin Coddington
2016-04-01 15:34 ` [PATCH 1/3] NFS: add get_nfs_lock_context, find_nfs_lock_context Benjamin Coddington
2016-04-01 16:45 ` kbuild test robot
2016-04-01 17:03 ` kbuild test robot
2016-04-01 15:34 ` [PATCH 2/3] NFS: add OFD lock owners to nfs_lock_context Benjamin Coddington
2016-04-01 16:17 ` kbuild test robot
2016-04-01 16:55 ` kbuild test robot [this message]
2016-04-01 15:34 ` [PATCH 3/3] NFSv4: use OFD lock owners in lock state lookup Benjamin Coddington
2016-04-01 15:47 ` [PATCH 0/3] Include OFD lock owners when looking up state Trond Myklebust
2016-04-01 15:48 ` Benjamin Coddington
2016-04-01 16:09 ` Trond Myklebust
2016-04-01 16:19 ` Jeff Layton
2016-04-01 20:24 ` Frank Filz
2016-04-01 16:35 ` Benjamin Coddington
2016-04-01 16:09 ` Jeff Layton
2016-04-01 17:17 ` Benjamin Coddington
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=201604020001.YWWjB51w%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=anna.schumaker@netapp.com \
--cc=bcodding@redhat.com \
--cc=jlayton@poochiereds.net \
--cc=kbuild-all@01.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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