From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android15-6.6 2/2] drivers/virt/gunyah/vm_mgr.c:887:5: sparse: sparse: symbol 'gunyah_gup_reclaim_parcel' was not declared. Should it be static?
Date: Tue, 31 Mar 2026 02:14:40 +0800 [thread overview]
Message-ID: <202603310204.jPov6ka9-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android15-6.6
head: 5fdbbd61a3cbdca7ac1034dc16723bdbc7ece8cc
commit: 296cceed084451decfd348415b1db9c833443713 [2/2] ANDROID: virt: gunyah: Add gup based demand paging support
config: arm64-randconfig-r122-20260330 (https://download.01.org/0day-ci/archive/20260331/202603310204.jPov6ka9-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 12.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260331/202603310204.jPov6ka9-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/202603310204.jPov6ka9-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/virt/gunyah/vm_mgr.c:887:5: sparse: sparse: symbol 'gunyah_gup_reclaim_parcel' was not declared. Should it be static?
vim +/gunyah_gup_reclaim_parcel +887 drivers/virt/gunyah/vm_mgr.c
886
> 887 int gunyah_gup_reclaim_parcel(struct gunyah_vm *ghvm,
888 struct gunyah_rm_mem_parcel *parcel, u64 gfn,
889 u64 nr)
890 {
891 struct gunyah_rm_mem_entry *entry;
892 struct folio *folio;
893 pgoff_t i;
894 int ret;
895
896 if (parcel->mem_handle != GUNYAH_MEM_HANDLE_INVAL) {
897 ret = gunyah_rm_mem_reclaim(ghvm->rm, parcel);
898 if (ret) {
899 dev_err(ghvm->parent, "Failed to reclaim parcel: %d\n",
900 ret);
901 /* We can't reclaim the pages -- hold onto the pages
902 * forever because we don't know what state the memory
903 * is in
904 */
905 return ret;
906 }
907 parcel->mem_handle = GUNYAH_MEM_HANDLE_INVAL;
908
909 for (i = 0; i < parcel->n_mem_entries; i++) {
910 entry = &parcel->mem_entries[i];
911
912 folio = pfn_folio(PHYS_PFN(le64_to_cpu(entry->phys_addr)));
913
914 if (folio_test_private(folio))
915 gunyah_folio_host_reclaim(folio);
916
917 folio_put(folio);
918 }
919
920 kfree(parcel->mem_entries);
921 kfree(parcel->acl_entries);
922 }
923
924 return 0;
925 }
926
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-30 18:15 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=202603310204.jPov6ka9-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.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.