From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [next:akpm 147/308] net/sunrpc/clnt.c:720:36: sparse: dereference of noderef expression
Date: Fri, 27 Jul 2012 13:02:25 +0000 [thread overview]
Message-ID: <20120727130225.GA29912@localhost> (raw)
Hi Mel,
There are new sparse warnings show up in
tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git akpm
head: 247109fa112ac912f31efc28e130ed2a0cc1764c
commit: 5bb176c86a868289d5d93d89919c3b5a339d6d20 [147/308] nfs: enable swap on NFS
All sparse warnings:
net/sunrpc/clnt.c:1362:39: sparse: incorrect type in initializer (different address spaces)
net/sunrpc/clnt.c:1362:39: expected struct rpc_xprt *xprt
net/sunrpc/clnt.c:1362:39: got struct rpc_xprt [noderef] <asn:4>*cl_xprt
net/sunrpc/clnt.c:1954:59: sparse: incorrect type in argument 1 (different address spaces)
net/sunrpc/clnt.c:1954:59: expected struct rpc_xprt *xprt
net/sunrpc/clnt.c:1954:59: got struct rpc_xprt [noderef] <asn:4>*cl_xprt
net/sunrpc/clnt.c:1470:39: sparse: incorrect type in initializer (different address spaces)
net/sunrpc/clnt.c:1470:39: expected struct rpc_xprt *xprt
net/sunrpc/clnt.c:1470:39: got struct rpc_xprt [noderef] <asn:4>*cl_xprt
net/sunrpc/clnt.c:1648:40: sparse: incorrect type in argument 1 (different address spaces)
net/sunrpc/clnt.c:1648:40: expected struct rpc_wait_queue *<noident>
net/sunrpc/clnt.c:1648:40: got struct rpc_wait_queue [noderef] <asn:4>*<noident>
net/sunrpc/clnt.c:1748:51: sparse: incorrect type in argument 1 (different address spaces)
net/sunrpc/clnt.c:1748:51: expected struct rpc_xprt *xprt
net/sunrpc/clnt.c:1748:51: got struct rpc_xprt [noderef] <asn:4>*cl_xprt
net/sunrpc/clnt.c:1800:59: sparse: incorrect type in argument 1 (different address spaces)
net/sunrpc/clnt.c:1800:59: expected struct rpc_xprt *xprt
net/sunrpc/clnt.c:1800:59: got struct rpc_xprt [noderef] <asn:4>*cl_xprt
net/sunrpc/clnt.c:1564:39: sparse: incorrect type in initializer (different address spaces)
net/sunrpc/clnt.c:1564:39: expected struct rpc_xprt *xprt
net/sunrpc/clnt.c:1564:39: got struct rpc_xprt [noderef] <asn:4>*cl_xprt
net/sunrpc/clnt.c:1968:46: sparse: incorrect type in argument 1 (different address spaces)
net/sunrpc/clnt.c:1968:46: expected struct rpc_xprt *xprt
net/sunrpc/clnt.c:1968:46: got struct rpc_xprt [noderef] <asn:4>*cl_xprt
+ net/sunrpc/clnt.c:720:36: sparse: dereference of noderef expression
net/sunrpc/clnt.c:1851:25: sparse: context imbalance in 'call_timeout' - different lock contexts for basic block
vim +720 net/sunrpc/clnt.c
717 atomic_inc(&clnt->cl_count);
718 if (clnt->cl_softrtry)
719 task->tk_flags |= RPC_TASK_SOFT;
> 720 if (task->tk_client->cl_xprt->swapper)
721 task->tk_flags |= RPC_TASK_SWAPPER;
722 /* Add to the client's list of all tasks */
723 spin_lock(&clnt->cl_lock);
---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu <wfg@linux.intel.com> Intel Corporation
next reply other threads:[~2012-07-27 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 13:02 Fengguang Wu [this message]
2012-07-27 14:10 ` [next:akpm 147/308] net/sunrpc/clnt.c:720:36: sparse: dereference of noderef expression Mel Gorman
2012-07-27 14:27 ` Fengguang Wu
2012-07-27 14:53 ` Mel Gorman
2012-07-27 15:01 ` Fengguang Wu
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=20120727130225.GA29912@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@vger.kernel.org \
/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).