From: kernel test robot <lkp@intel.com>
To: Trond Myklebust <trond.myklebust@hammerspace.com>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
linux-nfs@vger.kernel.org
Subject: [nfs:testing 2/2] fs/nfs/nfs4proc.c:9598:51: error: incompatible pointer types passing 'struct nfs4_exception *' to parameter of type 'long *'
Date: Wed, 2 Jun 2021 03:02:47 +0800 [thread overview]
Message-ID: <202106020345.szswjRdW-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3349 bytes --]
tree: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git testing
head: df584fa3fe729c964d40a96383e2e91d6ca65c2b
commit: df584fa3fe729c964d40a96383e2e91d6ca65c2b [2/2] NFSv4: Fix second deadlock in nfs4_evict_inode()
config: mips-randconfig-r014-20210601 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project db26cd30b6dd65e88d786e97a1e453af5cd48966)
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 mips cross compiling tool for clang build
# apt-get install binutils-mips-linux-gnu
git remote add nfs git://git.linux-nfs.org/projects/trondmy/linux-nfs.git
git fetch --no-tags nfs testing
git checkout df584fa3fe729c964d40a96383e2e91d6ca65c2b
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=mips
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> fs/nfs/nfs4proc.c:9598:51: error: incompatible pointer types passing 'struct nfs4_exception *' to parameter of type 'long *' [-Werror,-Wincompatible-pointer-types]
if (nfs4_async_handle_error(task, server, NULL, &exception) !=
^~~~~~~~~~
fs/nfs/nfs4proc.c:644:36: note: passing argument to parameter 'timeout' here
struct nfs4_state *state, long *timeout)
^
1 error generated.
vim +9598 fs/nfs/nfs4proc.c
9561
9562 static void nfs4_layoutreturn_done(struct rpc_task *task, void *calldata)
9563 {
9564 struct nfs4_layoutreturn *lrp = calldata;
9565 struct nfs_server *server;
9566 struct nfs4_exception exception = {
9567 .task_is_privileged = lrp->args.seq_args.sa_privileged,
9568 };
9569
9570 dprintk("--> %s\n", __func__);
9571
9572 if (!nfs41_sequence_process(task, &lrp->res.seq_res))
9573 return;
9574
9575 /*
9576 * Was there an RPC level error? Assume the call succeeded,
9577 * and that we need to release the layout
9578 */
9579 if (task->tk_rpc_status != 0 && RPC_WAS_SENT(task)) {
9580 lrp->res.lrs_present = 0;
9581 return;
9582 }
9583
9584 server = NFS_SERVER(lrp->args.inode);
9585 switch (task->tk_status) {
9586 case -NFS4ERR_OLD_STATEID:
9587 if (nfs4_layout_refresh_old_stateid(&lrp->args.stateid,
9588 &lrp->args.range,
9589 lrp->args.inode))
9590 goto out_restart;
9591 fallthrough;
9592 default:
9593 task->tk_status = 0;
9594 fallthrough;
9595 case 0:
9596 break;
9597 case -NFS4ERR_DELAY:
> 9598 if (nfs4_async_handle_error(task, server, NULL, &exception) !=
9599 -EAGAIN)
9600 break;
9601 goto out_restart;
9602 }
9603 dprintk("<-- %s\n", __func__);
9604 return;
9605 out_restart:
9606 task->tk_status = 0;
9607 nfs4_sequence_free_slot(&lrp->res.seq_res);
9608 rpc_restart_call_prepare(task);
9609 }
9610
---
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: 25951 bytes --]
reply other threads:[~2021-06-01 19:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202106020345.szswjRdW-lkp@intel.com \
--to=lkp@intel.com \
--cc=clang-built-linux@googlegroups.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