From: kernel test robot <lkp@intel.com>
To: Gregory Price <gourry@gourry.net>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [gourryinverse:scratch/gourry/cxl/compression/file_cleancache 85/98] mm/cram.c:165:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
Date: Sun, 12 Jul 2026 09:50:35 +0800 [thread overview]
Message-ID: <202607120911.twqPgjfB-lkp@intel.com> (raw)
tree: https://github.com/gourryinverse/linux scratch/gourry/cxl/compression/file_cleancache
head: 917ae95f0c6e29eaa695ff88d91f1ee1d8bc626d
commit: 9fb117618cd8a8687bae14185d28b33360452bd9 [85/98] mm/cram: core compressed-RAM tier API
config: x86_64-randconfig-r112-20260712 (https://download.01.org/0day-ci/archive/20260712/202607120911.twqPgjfB-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/20260712/202607120911.twqPgjfB-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/202607120911.twqPgjfB-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> mm/cram.c:165:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
mm/cram.c:165:14: sparse: struct cram_node [noderef] __rcu *
mm/cram.c:165:14: sparse: struct cram_node *
mm/cram.c:217:41: sparse: sparse: incompatible types in comparison expression (different address spaces):
mm/cram.c:217:41: sparse: struct cram_node [noderef] __rcu *
mm/cram.c:217:41: sparse: struct cram_node *
mm/cram.c:803:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
mm/cram.c:803:9: sparse: struct cram_node [noderef] __rcu *
mm/cram.c:803:9: sparse: struct cram_node *
mm/cram.c:893:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
mm/cram.c:893:9: sparse: struct cram_node [noderef] __rcu *
mm/cram.c:893:9: sparse: struct cram_node *
mm/cram.c:146:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
mm/cram.c:146:14: sparse: struct cram_node [noderef] __rcu *
mm/cram.c:146:14: sparse: struct cram_node *
mm/cram.c:146:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
mm/cram.c:146:14: sparse: struct cram_node [noderef] __rcu *
mm/cram.c:146:14: sparse: struct cram_node *
mm/cram.c:146:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
mm/cram.c:146:14: sparse: struct cram_node [noderef] __rcu *
mm/cram.c:146:14: sparse: struct cram_node *
mm/cram.c:146:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
mm/cram.c:146:14: sparse: struct cram_node [noderef] __rcu *
mm/cram.c:146:14: sparse: struct cram_node *
mm/cram.c:146:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
mm/cram.c:146:14: sparse: struct cram_node [noderef] __rcu *
mm/cram.c:146:14: sparse: struct cram_node *
mm/cram.c:146:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
mm/cram.c:146:14: sparse: struct cram_node [noderef] __rcu *
mm/cram.c:146:14: sparse: struct cram_node *
vim +165 mm/cram.c
159
160 static void cram_set_migration_blocked(int nid, bool blocked)
161 {
162 struct cram_node *cn;
163
164 rcu_read_lock();
> 165 cn = rcu_dereference(cram_nodes[nid]);
166 if (cn)
167 WRITE_ONCE(cn->migration_blocked, blocked);
168 rcu_read_unlock();
169 }
170
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-12 1:51 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=202607120911.twqPgjfB-lkp@intel.com \
--to=lkp@intel.com \
--cc=gourry@gourry.net \
--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.