All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Chuck Lever <chuck.lever@oracle.com>,
	Jeff Layton <jlayton@kernel.org>
Subject: fs/nfs/nfs4super.c:232:17: sparse: sparse: incompatible types in conditional expression (different base types):
Date: Thu, 14 May 2026 13:03:29 +0800	[thread overview]
Message-ID: <202605141218.uA0wk544-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   e1914add2799225a87502051415fc5c32aeb02ae
commit: 6f57293abb8d087de830dd3f02e66d94b3e59973 sunrpc: Fix compilation error (`make W=1`) when dprintk() is no-op
date:   6 weeks ago
config: x86_64-randconfig-121-20260514 (https://download.01.org/0day-ci/archive/20260514/202605141218.uA0wk544-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260514/202605141218.uA0wk544-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Fixes: 6f57293abb8d ("sunrpc: Fix compilation error (`make W=1`) when dprintk() is no-op")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202605141218.uA0wk544-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> fs/nfs/nfs4super.c:232:17: sparse: sparse: incompatible types in conditional expression (different base types):
   fs/nfs/nfs4super.c:232:17: sparse:    void
   fs/nfs/nfs4super.c:232:17: sparse:    int
   fs/nfs/nfs4super.c:255:17: sparse: sparse: incompatible types in conditional expression (different base types):
   fs/nfs/nfs4super.c:255:17: sparse:    void
   fs/nfs/nfs4super.c:255:17: sparse:    int
--
>> fs/nfs/getroot.c:90:17: sparse: sparse: incompatible types in conditional expression (different base types):
   fs/nfs/getroot.c:90:17: sparse:    void
   fs/nfs/getroot.c:90:17: sparse:    int
   fs/nfs/getroot.c:98:17: sparse: sparse: incompatible types in conditional expression (different base types):
   fs/nfs/getroot.c:98:17: sparse:    void
   fs/nfs/getroot.c:98:17: sparse:    int
   fs/nfs/getroot.c:114:17: sparse: sparse: incompatible types in conditional expression (different base types):
   fs/nfs/getroot.c:114:17: sparse:    void
   fs/nfs/getroot.c:114:17: sparse:    int
--
>> fs/nfs/namespace.c:304:17: sparse: sparse: incompatible types in conditional expression (different base types):
   fs/nfs/namespace.c:304:17: sparse:    void
   fs/nfs/namespace.c:304:17: sparse:    int
--
>> fs/nfs/fs_context.c:1120:9: sparse: sparse: incompatible types in conditional expression (different base types):
   fs/nfs/fs_context.c:1120:9: sparse:    void
   fs/nfs/fs_context.c:1120:9: sparse:    int
   fs/nfs/fs_context.c:1123:9: sparse: sparse: incompatible types in conditional expression (different base types):
   fs/nfs/fs_context.c:1123:9: sparse:    void
   fs/nfs/fs_context.c:1123:9: sparse:    int
   fs/nfs/fs_context.c:1126:9: sparse: sparse: incompatible types in conditional expression (different base types):
   fs/nfs/fs_context.c:1126:9: sparse:    void
   fs/nfs/fs_context.c:1126:9: sparse:    int
   fs/nfs/fs_context.c:1591:9: sparse: sparse: incompatible types in conditional expression (different base types):
   fs/nfs/fs_context.c:1591:9: sparse:    void
   fs/nfs/fs_context.c:1591:9: sparse:    int
   fs/nfs/fs_context.c:1605:9: sparse: sparse: incompatible types in conditional expression (different base types):
   fs/nfs/fs_context.c:1605:9: sparse:    void
   fs/nfs/fs_context.c:1605:9: sparse:    int
--
   fs/nfs/super.c:1170:49: sparse: sparse: incorrect type in initializer (different address spaces) @@     expected struct rpc_xprt *xprt1 @@     got struct rpc_xprt [noderef] __rcu *cl_xprt @@
   fs/nfs/super.c:1170:49: sparse:     expected struct rpc_xprt *xprt1
   fs/nfs/super.c:1170:49: sparse:     got struct rpc_xprt [noderef] __rcu *cl_xprt
   fs/nfs/super.c:1171:49: sparse: sparse: incorrect type in initializer (different address spaces) @@     expected struct rpc_xprt *xprt2 @@     got struct rpc_xprt [noderef] __rcu *cl_xprt @@
   fs/nfs/super.c:1171:49: sparse:     expected struct rpc_xprt *xprt2
   fs/nfs/super.c:1171:49: sparse:     got struct rpc_xprt [noderef] __rcu *cl_xprt
>> fs/nfs/super.c:1307:17: sparse: sparse: incompatible types in conditional expression (different base types):
   fs/nfs/super.c:1307:17: sparse:    void
   fs/nfs/super.c:1307:17: sparse:    int
   fs/nfs/super.c:1333:17: sparse: sparse: incompatible types in conditional expression (different base types):
   fs/nfs/super.c:1333:17: sparse:    void
   fs/nfs/super.c:1333:17: sparse:    int

vim +232 fs/nfs/nfs4super.c

fbdefd64428113 Bryan Schumaker 2012-07-16  217  
f2aedb713c2844 David Howells   2019-12-10  218  int nfs4_try_get_tree(struct fs_context *fc)
fbdefd64428113 Bryan Schumaker 2012-07-16  219  {
f2aedb713c2844 David Howells   2019-12-10  220  	struct nfs_fs_context *ctx = nfs_fc2context(fc);
f2aedb713c2844 David Howells   2019-12-10  221  	int err;
fbdefd64428113 Bryan Schumaker 2012-07-16  222  
f2aedb713c2844 David Howells   2019-12-10  223  	dfprintk(MOUNT, "--> nfs4_try_get_tree()\n");
fbdefd64428113 Bryan Schumaker 2012-07-16  224  
f2aedb713c2844 David Howells   2019-12-10  225  	/* We create a mount for the server's root, walk to the requested
f2aedb713c2844 David Howells   2019-12-10  226  	 * location and then create another mount for that.
f2aedb713c2844 David Howells   2019-12-10  227  	 */
62a55d088cd87d Scott Mayhew    2019-12-10  228  	err= do_nfs4_mount(nfs4_create_server(fc),
f2aedb713c2844 David Howells   2019-12-10  229  			   fc, ctx->nfs_server.hostname,
5eb005caf5383d David Howells   2019-12-10  230  			   ctx->nfs_server.export_path);
f2aedb713c2844 David Howells   2019-12-10  231  	if (err) {
c98e9daa59a611 Scott Mayhew    2021-01-05 @232  		nfs_ferrorf(fc, MOUNT, "NFS4: Couldn't follow remote path");
f2aedb713c2844 David Howells   2019-12-10  233  		dfprintk(MOUNT, "<-- nfs4_try_get_tree() = %d [error]\n", err);
f2aedb713c2844 David Howells   2019-12-10  234  	} else {
f2aedb713c2844 David Howells   2019-12-10  235  		dfprintk(MOUNT, "<-- nfs4_try_get_tree() = 0\n");
f2aedb713c2844 David Howells   2019-12-10  236  	}
f2aedb713c2844 David Howells   2019-12-10  237  	return err;
fbdefd64428113 Bryan Schumaker 2012-07-16  238  }
fbdefd64428113 Bryan Schumaker 2012-07-16  239  

:::::: The code at line 232 was first introduced by commit
:::::: c98e9daa59a611ff4e163689815f40380c912415 NFS: Adjust fs_context error logging

:::::: TO: Scott Mayhew <smayhew@redhat.com>
:::::: CC: Trond Myklebust <trond.myklebust@hammerspace.com>

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2026-05-14  5:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-14  5:03 kernel test robot [this message]
2026-05-14 17:37 ` fs/nfs/nfs4super.c:232:17: sparse: sparse: incompatible types in conditional expression (different base types): Chuck Lever

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=202605141218.uA0wk544-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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.