From: kernel test robot <lkp@intel.com>
To: Olga Kornievskaia <olga.kornievskaia@gmail.com>,
trond.myklebust@hammerspace.com, anna.schumaker@netapp.com
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/1] NFSv4.1+ add trunking when server trunking detected
Date: Wed, 9 Jun 2021 07:36:16 +0800 [thread overview]
Message-ID: <202106090753.tm6XYp8y-lkp@intel.com> (raw)
In-Reply-To: <20210608184527.87018-1-olga.kornievskaia@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3354 bytes --]
Hi Olga,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on nfs/linux-next]
[also build test WARNING on v5.13-rc5 next-20210608]
[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]
url: https://github.com/0day-ci/linux/commits/Olga-Kornievskaia/NFSv4-1-add-trunking-when-server-trunking-detected/20210609-025208
base: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
config: x86_64-randconfig-a015-20210608 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project d32cc150feb72f315a5bbd34f92e7beca21a50da)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# https://github.com/0day-ci/linux/commit/52d86dfa29146024beeca51af401aabbb329a942
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Olga-Kornievskaia/NFSv4-1-add-trunking-when-server-trunking-detected/20210609-025208
git checkout 52d86dfa29146024beeca51af401aabbb329a942
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> fs/nfs/nfs4client.c:369:20: warning: variable 'old_salen' set but not used [-Wunused-but-set-variable]
size_t clp_salen, old_salen;
^
1 warning generated.
vim +/old_salen +369 fs/nfs/nfs4client.c
363
364 static void nfs4_add_trunk(struct nfs_client *clp, struct nfs_client *old)
365 {
366 struct sockaddr_storage clp_addr, old_addr;
367 struct sockaddr *clp_sap = (struct sockaddr *)&clp_addr;
368 struct sockaddr *old_sap = (struct sockaddr *)&old_addr;
> 369 size_t clp_salen, old_salen;
370 struct xprt_create xprt_args = {
371 .ident = old->cl_proto,
372 .net = old->cl_net,
373 .servername = old->cl_hostname,
374 };
375 struct nfs4_add_xprt_data xprtdata = {
376 .clp = old,
377 };
378 struct rpc_add_xprt_test rpcdata = {
379 .add_xprt_test = old->cl_mvops->session_trunk,
380 .data = &xprtdata,
381 };
382
383 if (clp->cl_proto != old->cl_proto)
384 return;
385 clp_salen = rpc_peeraddr(clp->cl_rpcclient, clp_sap, sizeof(clp_addr));
386 old_salen = rpc_peeraddr(old->cl_rpcclient, old_sap, sizeof(old_addr));
387
388 if (clp_addr.ss_family != old_addr.ss_family)
389 return;
390
391 xprt_args.dstaddr = clp_sap;
392 xprt_args.addrlen = clp_salen;
393
394 xprtdata.cred = nfs4_get_clid_cred(old);
395 rpc_clnt_add_xprt(old->cl_rpcclient, &xprt_args,
396 rpc_clnt_setup_test_and_add_xprt, &rpcdata);
397
398 if (xprtdata.cred)
399 put_cred(xprtdata.cred);
400 }
401
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 34438 bytes --]
prev parent reply other threads:[~2021-06-08 23:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 18:45 [PATCH 1/1] NFSv4.1+ add trunking when server trunking detected Olga Kornievskaia
2021-06-08 20:41 ` Chuck Lever III
2021-06-08 20:56 ` Olga Kornievskaia
2021-06-08 21:06 ` Chuck Lever III
2021-06-08 21:19 ` Trond Myklebust
2021-06-08 21:26 ` Trond Myklebust
2021-06-08 21:30 ` Olga Kornievskaia
2021-06-08 21:41 ` Trond Myklebust
2021-06-08 22:21 ` Olga Kornievskaia
2021-06-08 22:31 ` Trond Myklebust
2021-06-08 22:38 ` Olga Kornievskaia
2021-06-08 23:02 ` Trond Myklebust
2021-06-08 23:12 ` Trond Myklebust
2021-06-08 21:40 ` Olga Kornievskaia
2021-06-08 22:13 ` Trond Myklebust
2021-06-08 22:18 ` Olga Kornievskaia
2021-06-08 22:27 ` Trond Myklebust
2021-06-08 22:38 ` Olga Kornievskaia
2021-06-08 22:58 ` Trond Myklebust
2021-06-09 20:47 ` Olga Kornievskaia
2021-06-08 22:39 ` kernel test robot
2021-06-08 23:36 ` 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=202106090753.tm6XYp8y-lkp@intel.com \
--to=lkp@intel.com \
--cc=anna.schumaker@netapp.com \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-nfs@vger.kernel.org \
--cc=olga.kornievskaia@gmail.com \
--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