linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: kbuild-all@01.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] NFSv4.1: nfs4_opendata_check_deleg needs to handle NFS4_OPEN_CLAIM_DELEG_CUR_FH
Date: Fri, 2 Oct 2015 23:57:00 +0800	[thread overview]
Message-ID: <201510022302.68uvmDNW%fengguang.wu@intel.com> (raw)
In-Reply-To: <1443800844-7249-1-git-send-email-trond.myklebust@primarydata.com>

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

Hi Trond,

[auto build test results on v4.3-rc3 -- if it's inappropriate base, please ignore]

config: m68k-sun3_defconfig (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=m68k 

All warnings (new ones prefixed by >>):

   fs/nfs/nfs4proc.c: In function 'nfs4_opendata_check_deleg':
>> fs/nfs/nfs4proc.c:1461:2: warning: enumeration value 'NFS4_OPEN_CLAIM_NULL' not handled in switch [-Wswitch]
     switch (data->o_arg.claim) {
     ^
>> fs/nfs/nfs4proc.c:1461:2: warning: enumeration value 'NFS4_OPEN_CLAIM_PREVIOUS' not handled in switch [-Wswitch]
>> fs/nfs/nfs4proc.c:1461:2: warning: enumeration value 'NFS4_OPEN_CLAIM_DELEGATE_PREV' not handled in switch [-Wswitch]
>> fs/nfs/nfs4proc.c:1461:2: warning: enumeration value 'NFS4_OPEN_CLAIM_FH' not handled in switch [-Wswitch]
>> fs/nfs/nfs4proc.c:1461:2: warning: enumeration value 'NFS4_OPEN_CLAIM_DELEG_PREV_FH' not handled in switch [-Wswitch]

vim +/NFS4_OPEN_CLAIM_NULL +1461 fs/nfs/nfs4proc.c

  1445		atomic_inc(&state->count);
  1446		return state;
  1447	}
  1448	
  1449	static void
  1450	nfs4_opendata_check_deleg(struct nfs4_opendata *data, struct nfs4_state *state)
  1451	{
  1452		struct nfs_client *clp = NFS_SERVER(state->inode)->nfs_client;
  1453		struct nfs_delegation *delegation;
  1454		int delegation_flags = 0;
  1455	
  1456		rcu_read_lock();
  1457		delegation = rcu_dereference(NFS_I(state->inode)->delegation);
  1458		if (delegation)
  1459			delegation_flags = delegation->flags;
  1460		rcu_read_unlock();
> 1461		switch (data->o_arg.claim) {
  1462		case NFS4_OPEN_CLAIM_DELEGATE_CUR:
  1463		case NFS4_OPEN_CLAIM_DELEG_CUR_FH:
  1464			pr_err_ratelimited("NFS: Broken NFSv4 server %s is "
  1465					   "returning a delegation for "
  1466					   "OPEN(CLAIM_DELEGATE_CUR)\n",
  1467					   clp->cl_hostname);
  1468			return;
  1469		}

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

  reply	other threads:[~2015-10-02 15:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 15:47 [PATCH] NFSv4.1: nfs4_opendata_check_deleg needs to handle NFS4_OPEN_CLAIM_DELEG_CUR_FH Trond Myklebust
2015-10-02 15:57 ` kbuild test robot [this message]
2015-10-02 16:39   ` [PATCH v2] " Trond Myklebust

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=201510022302.68uvmDNW%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).