From: kernel test robot <lkp@intel.com>
To: Anna Schumaker <anna@kernel.org>,
linux-nfs@vger.kernel.org, trond.myklebust@hammerspace.com
Cc: kbuild-all@lists.01.org, anna@kernel.org, cuiyue-fnst@fujitsu.com
Subject: Re: [PATCH v3] NFSv4.2: Update mode bits after ALLOCATE and DEALLOCATE
Date: Fri, 2 Sep 2022 10:39:56 +0800 [thread overview]
Message-ID: <202209021046.JT3dSTuK-lkp@intel.com> (raw)
In-Reply-To: <20220901191927.1582107-1-anna@kernel.org>
Hi Anna,
I love your patch! Perhaps something to improve:
[auto build test WARNING on trondmy-nfs/linux-next]
[also build test WARNING on linus/master v6.0-rc3 next-20220901]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Anna-Schumaker/NFSv4-2-Update-mode-bits-after-ALLOCATE-and-DEALLOCATE/20220902-032035
base: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20220902/202209021046.JT3dSTuK-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-5) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/intel-lab-lkp/linux/commit/8a722317bde651cf6fa29c7c618ddcce4e52b4e1
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Anna-Schumaker/NFSv4-2-Update-mode-bits-after-ALLOCATE-and-DEALLOCATE/20220902-032035
git checkout 8a722317bde651cf6fa29c7c618ddcce4e52b4e1
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash fs/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
fs/nfs/nfs42proc.c: In function '_nfs42_proc_fallocate':
>> fs/nfs/nfs42proc.c:59:22: warning: unused variable 'invalid' [-Wunused-variable]
59 | unsigned int invalid = 0;
| ^~~~~~~
vim +/invalid +59 fs/nfs/nfs42proc.c
43
44 static int _nfs42_proc_fallocate(struct rpc_message *msg, struct file *filep,
45 struct nfs_lock_context *lock, loff_t offset, loff_t len)
46 {
47 struct inode *inode = file_inode(filep);
48 struct nfs_server *server = NFS_SERVER(inode);
49 u32 bitmask[NFS_BITMASK_SZ];
50 struct nfs42_falloc_args args = {
51 .falloc_fh = NFS_FH(inode),
52 .falloc_offset = offset,
53 .falloc_length = len,
54 .falloc_bitmask = bitmask,
55 };
56 struct nfs42_falloc_res res = {
57 .falloc_server = server,
58 };
> 59 unsigned int invalid = 0;
60 int status;
61
62 msg->rpc_argp = &args;
63 msg->rpc_resp = &res;
64
65 status = nfs4_set_rw_stateid(&args.falloc_stateid, lock->open_context,
66 lock, FMODE_WRITE);
67 if (status) {
68 if (status == -EAGAIN)
69 status = -NFS4ERR_BAD_STATEID;
70 return status;
71 }
72
73 nfs4_bitmask_set(bitmask, server->cache_consistency_bitmask, inode,
74 NFS_INO_INVALID_BLOCKS);
75
76 res.falloc_fattr = nfs_alloc_fattr();
77 if (!res.falloc_fattr)
78 return -ENOMEM;
79
80 status = nfs4_call_sync(server->client, server, msg,
81 &args.seq_args, &res.seq_res, 0);
82 if (status == 0) {
83 if (nfs_should_remove_suid(inode)) {
84 spin_lock(&inode->i_lock);
85 nfs_set_cache_invalid(inode, NFS_INO_INVALID_MODE);
86 spin_unlock(&inode->i_lock);
87 }
88 status = nfs_post_op_update_inode_force_wcc(inode,
89 res.falloc_fattr);
90 }
91 if (msg->rpc_proc == &nfs4_procedures[NFSPROC4_CLNT_ALLOCATE])
92 trace_nfs4_fallocate(inode, &args, status);
93 else
94 trace_nfs4_deallocate(inode, &args, status);
95 kfree(res.falloc_fattr);
96 return status;
97 }
98
--
0-DAY CI Kernel Test Service
https://01.org/lkp
prev parent reply other threads:[~2022-09-02 2:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 19:19 [PATCH v3] NFSv4.2: Update mode bits after ALLOCATE and DEALLOCATE Anna Schumaker
2022-09-02 2:39 ` kernel test robot [this message]
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=202209021046.JT3dSTuK-lkp@intel.com \
--to=lkp@intel.com \
--cc=anna@kernel.org \
--cc=cuiyue-fnst@fujitsu.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.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