From: kernel test robot <lkp@intel.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [djwong-xfs:djwong-wtf 111/117] fs/xfs/xfs_healthmon.c:72:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
Date: Sun, 15 Feb 2026 11:25:06 +0800 [thread overview]
Message-ID: <202602151111.adtkFni9-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git djwong-wtf
head: b26d191b36748da1afef6227d8de4bd258015b48
commit: 50ea06949a53186ea95fb6f84cd1712b2eca258e [111/117] xfs: fix potential pointer access race in xfs_healthmon_get
config: mips-randconfig-r121-20260215 (https://download.01.org/0day-ci/archive/20260215/202602151111.adtkFni9-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 9b8addffa70cee5b2acc5454712d9cf78ce45710)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260215/202602151111.adtkFni9-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
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202602151111.adtkFni9-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/xfs/xfs_healthmon.c:72:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
fs/xfs/xfs_healthmon.c:72:14: sparse: struct xfs_healthmon [noderef] __rcu *
fs/xfs/xfs_healthmon.c:72:14: sparse: struct xfs_healthmon *
fs/xfs/xfs_healthmon.c:113:13: sparse: sparse: incompatible types in comparison expression (different address spaces):
fs/xfs/xfs_healthmon.c:113:13: sparse: struct xfs_healthmon [noderef] __rcu *
fs/xfs/xfs_healthmon.c:113:13: sparse: struct xfs_healthmon *
fs/xfs/xfs_healthmon.c:119:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
fs/xfs/xfs_healthmon.c:119:9: sparse: struct xfs_healthmon [noderef] __rcu *
fs/xfs/xfs_healthmon.c:119:9: sparse: struct xfs_healthmon *
fs/xfs/xfs_healthmon.c:137:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
fs/xfs/xfs_healthmon.c:137:9: sparse: struct xfs_healthmon [noderef] __rcu *
fs/xfs/xfs_healthmon.c:137:9: sparse: struct xfs_healthmon *
vim +72 fs/xfs/xfs_healthmon.c
63
64 /* Grab a reference to the healthmon object for a given mount, if any. */
65 static struct xfs_healthmon *
66 xfs_healthmon_get(
67 struct xfs_mount *mp)
68 {
69 struct xfs_healthmon *hm;
70
71 rcu_read_lock();
> 72 hm = rcu_dereference(mp->m_healthmon);
73 if (hm && !refcount_inc_not_zero(&hm->ref))
74 hm = NULL;
75 rcu_read_unlock();
76
77 return hm;
78 }
79
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-02-15 3:26 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=202602151111.adtkFni9-lkp@intel.com \
--to=lkp@intel.com \
--cc=darrick.wong@oracle.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 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.