Linux NFS development
 help / color / mirror / Atom feed
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 1/3] NFS: add get_nfs_lock_context, find_nfs_lock_context
Date: Sat, 2 Apr 2016 00:45:39 +0800	[thread overview]
Message-ID: <201604020002.3WywISq5%fengguang.wu@intel.com> (raw)
In-Reply-To: <55019f777691bf13781699d70cdaea6504311c89.1459512820.git.bcodding@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 3802 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: mips-jz4740 (attached as .config)
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 

Note: the linux-review/Benjamin-Coddington/Include-OFD-lock-owners-when-looking-up-state/20160401-233801 HEAD e6973cc5e04cb6af43dbba362969dbf6ddcf7740 builds fine.
      It only hurts bisectibility.

All errors (new ones prefixed by >>):

   fs/nfs/file.c: In function 'do_unlk':
>> fs/nfs/file.c:759:32: error: passing argument 1 of 'nfs_find_lock_context' from incompatible pointer type [-Werror=incompatible-pointer-types]
     l_ctx = nfs_find_lock_context(nfs_file_open_context(filp));
                                   ^
   In file included from fs/nfs/file.c:25:0:
   include/linux/nfs_fs.h:368:33: note: expected 'struct file *' but argument is of type 'struct nfs_open_context *'
    extern struct nfs_lock_context *nfs_find_lock_context(struct file *file);
                                    ^
   cc1: some warnings being treated as errors
--
   fs/nfs/direct.c: In function 'nfs_file_direct_read':
>> fs/nfs/direct.c:599:32: error: passing argument 1 of 'nfs_find_lock_context' from incompatible pointer type [-Werror=incompatible-pointer-types]
     l_ctx = nfs_find_lock_context(dreq->ctx);
                                   ^
   In file included from fs/nfs/direct.c:51:0:
   include/linux/nfs_fs.h:368:33: note: expected 'struct file *' but argument is of type 'struct nfs_open_context *'
    extern struct nfs_lock_context *nfs_find_lock_context(struct file *file);
                                    ^
   fs/nfs/direct.c: In function 'nfs_file_direct_write':
   fs/nfs/direct.c:1032:32: error: passing argument 1 of 'nfs_find_lock_context' from incompatible pointer type [-Werror=incompatible-pointer-types]
     l_ctx = nfs_find_lock_context(dreq->ctx);
                                   ^
   In file included from fs/nfs/direct.c:51:0:
   include/linux/nfs_fs.h:368:33: note: expected 'struct file *' but argument is of type 'struct nfs_open_context *'
    extern struct nfs_lock_context *nfs_find_lock_context(struct file *file);
                                    ^
   cc1: some warnings being treated as errors
--
   fs/nfs/pagelist.c: In function 'nfs_create_request':
>> fs/nfs/pagelist.c:332:32: error: passing argument 1 of 'nfs_find_lock_context' from incompatible pointer type [-Werror=incompatible-pointer-types]
     l_ctx = nfs_find_lock_context(ctx);
                                   ^
   In file included from fs/nfs/pagelist.c:20:0:
   include/linux/nfs_fs.h:368:33: note: expected 'struct file *' but argument is of type 'struct nfs_open_context *'
    extern struct nfs_lock_context *nfs_find_lock_context(struct file *file);
                                    ^
   cc1: some warnings being treated as errors

vim +/nfs_find_lock_context +759 fs/nfs/file.c

   753		/*
   754		 * Flush all pending writes before doing anything
   755		 * with locks..
   756		 */
   757		vfs_fsync(filp, 0);
   758	
 > 759		l_ctx = nfs_find_lock_context(nfs_file_open_context(filp));
   760		if (!IS_ERR(l_ctx)) {
   761			status = nfs_iocounter_wait(l_ctx);
   762			nfs_put_lock_context(l_ctx);

---
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: 18246 bytes --]

  reply	other threads:[~2016-04-01 16:45 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 [this message]
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
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=201604020002.3WywISq5%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