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 1/5] NFSv4: Don't check file access when reclaiming state
Date: Fri, 11 Nov 2016 06:18:55 +0800 [thread overview]
Message-ID: <201611110658.6UcoC9ax%fengguang.wu@intel.com> (raw)
In-Reply-To: <1478814070-17140-2-git-send-email-trond.myklebust@primarydata.com>
[-- Attachment #1: Type: text/plain, Size: 2528 bytes --]
Hi Trond,
[auto build test WARNING on nfs/linux-next]
[also build test WARNING on v4.9-rc4 next-20161110]
[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/Trond-Myklebust/Optimisations-for-state-management/20161111-054856
base: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
config: x86_64-eywa-module (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
fs/nfs/nfs4proc.c: In function 'nfs4_opendata_alloc':
>> fs/nfs/nfs4proc.c:1232:3: warning: enumeration value 'NFS4_OPEN_CLAIM_PREVIOUS' not handled in switch [-Wswitch]
switch (p->o_arg.claim) {
^~~~~~
>> fs/nfs/nfs4proc.c:1232:3: warning: enumeration value 'NFS4_OPEN_CLAIM_DELEGATE_CUR' not handled in switch [-Wswitch]
>> fs/nfs/nfs4proc.c:1232:3: warning: enumeration value 'NFS4_OPEN_CLAIM_DELEGATE_PREV' not handled in switch [-Wswitch]
>> fs/nfs/nfs4proc.c:1232:3: warning: enumeration value 'NFS4_OPEN_CLAIM_DELEG_CUR_FH' not handled in switch [-Wswitch]
>> fs/nfs/nfs4proc.c:1232:3: warning: enumeration value 'NFS4_OPEN_CLAIM_DELEG_PREV_FH' not handled in switch [-Wswitch]
vim +/NFS4_OPEN_CLAIM_PREVIOUS +1232 fs/nfs/nfs4proc.c
1216 goto err_free_label;
1217 nfs_sb_active(dentry->d_sb);
1218 p->dentry = dget(dentry);
1219 p->dir = parent;
1220 p->owner = sp;
1221 atomic_inc(&sp->so_count);
1222 p->o_arg.open_flags = flags;
1223 p->o_arg.fmode = fmode & (FMODE_READ|FMODE_WRITE);
1224 p->o_arg.claim = nfs4_map_atomic_open_claim(server, claim);
1225 p->o_arg.share_access = nfs4_map_atomic_open_share(server,
1226 fmode, flags);
1227 /* don't put an ACCESS op in OPEN compound if O_EXCL, because ACCESS
1228 * will return permission denied for all bits until close */
1229 if (!(flags & O_EXCL)) {
1230 /* ask server to check for all possible rights as results
1231 * are cached */
> 1232 switch (p->o_arg.claim) {
1233 case NFS4_OPEN_CLAIM_NULL:
1234 case NFS4_OPEN_CLAIM_FH:
1235 p->o_arg.access = NFS4_ACCESS_READ |
1236 NFS4_ACCESS_MODIFY |
1237 NFS4_ACCESS_EXTEND |
1238 NFS4_ACCESS_EXECUTE;
1239 }
1240 }
---
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: 25516 bytes --]
next prev parent reply other threads:[~2016-11-10 22:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 21:41 [PATCH 0/5] Optimisations for state management Trond Myklebust
2016-11-10 21:41 ` [PATCH 1/5] NFSv4: Don't check file access when reclaiming state Trond Myklebust
2016-11-10 21:41 ` [PATCH 2/5] NFSv4: Don't ask for the change attribute " Trond Myklebust
2016-11-10 21:41 ` [PATCH 3/5] NFSv4: Don't request a GETATTR on open_downgrade Trond Myklebust
2016-11-10 21:41 ` [PATCH 4/5] NFSv4: Don't request close-to-open attribute when holding a delegation Trond Myklebust
2016-11-10 21:41 ` [PATCH 5/5] NFSv4: Optimise away forced revalidation when we know the attributes are OK Trond Myklebust
2016-11-10 22:18 ` kbuild test robot [this message]
2016-11-14 20:44 ` [PATCH 1/5] NFSv4: Don't check file access when reclaiming state Anna Schumaker
-- strict thread matches above, loose matches on Subject: below --
2016-12-01 22:06 [PATCH 0/5] Performance optimsations for 4.10 Trond Myklebust
2016-12-01 22:06 ` [PATCH 1/5] NFSv4: Don't check file access when reclaiming state 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=201611110658.6UcoC9ax%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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.