Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Ackerley Tng <ackerleytng@google.com>
Subject: [sean-jc:x86/gmem_inplace 35/59] arch/x86/kvm/../../../virt/kvm/guest_memfd.c:1204:10: error: call to undeclared function 'kvm_range_has_vm_memory_attributes'; ISO C99 and later do not support implicit function declarations
Date: Thu, 11 Jun 2026 21:32:16 +0200	[thread overview]
Message-ID: <202606112109.SWdbql08-lkp@intel.com> (raw)

tree:   https://github.com/sean-jc/linux x86/gmem_inplace
head:   4a99b51978dc7e7b3e5f61c14790e9f49c33fdbb
commit: 3b494d9b05174562830962ea9e49aff75fde974f [35/59] KVM: Let userspace disable per-VM mem attributes, enable per-gmem attributes
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260611/202606112109.SWdbql08-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project f43d6834093b19baf79beda8c0337ab020ac5f17)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260611/202606112109.SWdbql08-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/202606112109.SWdbql08-lkp@intel.com/

All errors (new ones prefixed by >>):

>> arch/x86/kvm/../../../virt/kvm/guest_memfd.c:1204:10: error: call to undeclared function 'kvm_range_has_vm_memory_attributes'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
    1204 |                 return kvm_range_has_vm_memory_attributes(kvm, gfn, gfn + nr_pages,
         |                        ^
   1 error generated.


vim +/kvm_range_has_vm_memory_attributes +1204 arch/x86/kvm/../../../virt/kvm/guest_memfd.c

1f6c06b177513e8 Paolo Bonzini       2024-02-14  1196  
36cf63bb5df6883 Fuad Tabba          2025-07-29  1197  #ifdef CONFIG_HAVE_KVM_ARCH_GMEM_POPULATE
3338335299abe86 Sean Christopherson 2026-06-10  1198  static bool kvm_gmem_range_is_private(struct file *file, pgoff_t index,
3338335299abe86 Sean Christopherson 2026-06-10  1199  				      size_t nr_pages, struct kvm *kvm, gfn_t gfn)
3338335299abe86 Sean Christopherson 2026-06-10  1200  {
3338335299abe86 Sean Christopherson 2026-06-10  1201  	struct maple_tree *mt = &GMEM_I(file_inode(file))->attributes;
3338335299abe86 Sean Christopherson 2026-06-10  1202  
3338335299abe86 Sean Christopherson 2026-06-10  1203  	if (!gmem_in_place_conversion)
3338335299abe86 Sean Christopherson 2026-06-10 @1204  		return kvm_range_has_vm_memory_attributes(kvm, gfn, gfn + nr_pages,
3338335299abe86 Sean Christopherson 2026-06-10  1205  							  KVM_MEMORY_ATTRIBUTE_PRIVATE,
3338335299abe86 Sean Christopherson 2026-06-10  1206  							  KVM_MEMORY_ATTRIBUTE_PRIVATE);
3338335299abe86 Sean Christopherson 2026-06-10  1207  
e4f7252dca71e1a Ackerley Tng        2026-04-23  1208  	return kvm_gmem_range_has_attributes(mt, index, nr_pages,
e4f7252dca71e1a Ackerley Tng        2026-04-23  1209  					     KVM_MEMORY_ATTRIBUTE_PRIVATE);
3338335299abe86 Sean Christopherson 2026-06-10  1210  }
2a62345b30529e4 Michael Roth        2026-01-08  1211  

:::::: The code at line 1204 was first introduced by commit
:::::: 3338335299abe867f2a5d5b207df57edba03b5f1 KVM: guest_memfd: Wire up kvm_get_memory_attributes() to per-gmem attributes

:::::: TO: Sean Christopherson <seanjc@google.com>
:::::: CC: Sean Christopherson <seanjc@google.com>

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-06-11 19:33 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=202606112109.SWdbql08-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ackerleytng@google.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=seanjc@google.com \
    /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