From: kernel test robot <lkp@intel.com>
To: Sasha Levin <sashal@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [sashal-linus-next:linus-next 24/43] arch/x86/kvm/../../../virt/kvm/guest_memfd.c:111:22: warning: 'kvm_gmem_get_folio_noalloc' defined but not used
Date: Wed, 18 Mar 2026 04:30:25 +0800 [thread overview]
Message-ID: <202603180446.dkWedwkx-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linus-next.git linus-next
head: e9cdadb8e756233fae78095f72ff1f40f138def1
commit: 2268a4ea672795a572dbbd7187117546ff262562 [24/43] Merge branch 'mm-next' into all-next
config: x86_64-randconfig-014-20260317 (https://download.01.org/0day-ci/archive/20260318/202603180446.dkWedwkx-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260318/202603180446.dkWedwkx-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/202603180446.dkWedwkx-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/x86/kvm/../../../virt/kvm/guest_memfd.c:111:22: warning: 'kvm_gmem_get_folio_noalloc' defined but not used [-Wunused-function]
111 | static struct folio *kvm_gmem_get_folio_noalloc(struct inode *inode, pgoff_t pgoff)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/kvm_gmem_get_folio_noalloc +111 arch/x86/kvm/../../../virt/kvm/guest_memfd.c
3bb2531e20bff9 Paolo Bonzini 2024-05-07 110
0ad31a420d0638 Nikita Kalyazin 2026-03-06 @111 static struct folio *kvm_gmem_get_folio_noalloc(struct inode *inode, pgoff_t pgoff)
0ad31a420d0638 Nikita Kalyazin 2026-03-06 112 {
0ad31a420d0638 Nikita Kalyazin 2026-03-06 113 return __filemap_get_folio(inode->i_mapping, pgoff,
0ad31a420d0638 Nikita Kalyazin 2026-03-06 114 FGP_LOCK | FGP_ACCESSED, 0);
0ad31a420d0638 Nikita Kalyazin 2026-03-06 115 }
0ad31a420d0638 Nikita Kalyazin 2026-03-06 116
:::::: The code at line 111 was first introduced by commit
:::::: 0ad31a420d063897026ee2e71e1461069951ac72 KVM: guest_memfd: implement userfaultfd operations
:::::: TO: Nikita Kalyazin <kalyazin@amazon.com>
:::::: CC: Andrew Morton <akpm@linux-foundation.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-17 20:30 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=202603180446.dkWedwkx-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sashal@kernel.org \
/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.