From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: fs/seq_file.c:960:12: sparse: sparse: incorrect type in assignment (different address spaces)
Date: Wed, 27 Dec 2023 12:18:58 +0800 [thread overview]
Message-ID: <202312271242.6AVwbkKf-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: fbafc3e621c3f4ded43720fdb1d6ce1728ec664e
commit: ad25f5cb39872ca14bcbe00816ae65c22fe04b89 rxrpc: Fix locking issue
date: 1 year, 7 months ago
config: x86_64-alldefconfig (https://download.01.org/0day-ci/archive/20231227/202312271242.6AVwbkKf-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231227/202312271242.6AVwbkKf-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/202312271242.6AVwbkKf-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
fs/seq_file.c:938:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
fs/seq_file.c:938:9: sparse: struct list_head [noderef] __rcu *
fs/seq_file.c:938:9: sparse: struct list_head *
fs/seq_file.c:938:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
fs/seq_file.c:938:9: sparse: struct list_head [noderef] __rcu *
fs/seq_file.c:938:9: sparse: struct list_head *
>> fs/seq_file.c:960:12: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct list_head *lh @@ got struct list_head [noderef] __rcu * @@
fs/seq_file.c:960:12: sparse: expected struct list_head *lh
fs/seq_file.c:960:12: sparse: got struct list_head [noderef] __rcu *
fs/seq_file.c:1087:24: sparse: sparse: incompatible types in comparison expression (different address spaces):
fs/seq_file.c:1087:24: sparse: struct hlist_node [noderef] __rcu *
fs/seq_file.c:1087:24: sparse: struct hlist_node *
fs/seq_file.c:1089:24: sparse: sparse: incompatible types in comparison expression (different address spaces):
fs/seq_file.c:1089:24: sparse: struct hlist_node [noderef] __rcu *
fs/seq_file.c:1089:24: sparse: struct hlist_node *
vim +960 fs/seq_file.c
933
934 struct list_head *seq_list_start_rcu(struct list_head *head, loff_t pos)
935 {
936 struct list_head *lh;
937
> 938 list_for_each_rcu(lh, head)
939 if (pos-- == 0)
940 return lh;
941
942 return NULL;
943 }
944 EXPORT_SYMBOL(seq_list_start_rcu);
945
946 struct list_head *seq_list_start_head_rcu(struct list_head *head, loff_t pos)
947 {
948 if (!pos)
949 return head;
950
951 return seq_list_start_rcu(head, pos - 1);
952 }
953 EXPORT_SYMBOL(seq_list_start_head_rcu);
954
955 struct list_head *seq_list_next_rcu(void *v, struct list_head *head,
956 loff_t *ppos)
957 {
958 struct list_head *lh;
959
> 960 lh = list_next_rcu((struct list_head *)v);
961 ++*ppos;
962 return lh == head ? NULL : lh;
963 }
964 EXPORT_SYMBOL(seq_list_next_rcu);
965
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-27 4:19 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=202312271242.6AVwbkKf-lkp@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®