The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Jeff Layton <jlayton@kernel.org>,
	kernel test robot <lkp@intel.com>
Subject: Re: fs/nfs/nfs4super.c:232:17: sparse: sparse: incompatible types in conditional expression (different base types):
Date: Thu, 14 May 2026 13:37:24 -0400	[thread overview]
Message-ID: <c295b65f-bbf8-442e-8cdd-b1c5159eefd9@oracle.com> (raw)
In-Reply-To: <202605141218.uA0wk544-lkp@intel.com>

On 5/14/26 1:03 AM, kernel test robot wrote:
> 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
Andy, do you plan to have a look at this sparse splat?


-- 
Chuck Lever

      reply	other threads:[~2026-05-14 17:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-14  5:03 fs/nfs/nfs4super.c:232:17: sparse: sparse: incompatible types in conditional expression (different base types): kernel test robot
2026-05-14 17:37 ` Chuck Lever [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=c295b65f-bbf8-442e-8cdd-b1c5159eefd9@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=jlayton@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox