All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Peter Xu <peterx@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev, Mike Rapoport <rppt@kernel.org>
Subject: [rppt:uffd+guestmemfd/v1 12/15] mm/memory.c:5340:28: error: 'const struct vm_operations_struct' has no member named 'uffd_ops'
Date: Tue, 24 Feb 2026 00:22:21 +0800	[thread overview]
Message-ID: <202602240004.Sop2OCIr-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/rppt/linux.git uffd+guestmemfd/v1
head:   ea5af993d28d129d273453041a5ad6b3a1a9e31a
commit: 40ced64186624690248a72f77202a245eb1717e3 [12/15] mm: generalize handling of userfaults in __do_fault()
config: nios2-allnoconfig (https://download.01.org/0day-ci/archive/20260224/202602240004.Sop2OCIr-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260224/202602240004.Sop2OCIr-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/202602240004.Sop2OCIr-lkp@intel.com/

All errors (new ones prefixed by >>):

   mm/memory.c: In function '__do_userfault':
>> mm/memory.c:5340:28: error: 'const struct vm_operations_struct' has no member named 'uffd_ops'
    5340 |         folio = vma->vm_ops->uffd_ops->get_folio_noalloc(inode, vmf->pgoff);
         |                            ^~


vim +5340 mm/memory.c

  5330	
  5331	static vm_fault_t __do_userfault(struct vm_fault *vmf)
  5332	{
  5333		struct vm_area_struct *vma = vmf->vma;
  5334		struct inode *inode = file_inode(vma->vm_file);
  5335		struct folio *folio;
  5336	
  5337		if (!(userfaultfd_missing(vma) || userfaultfd_minor(vma)))
  5338			return 0;
  5339	
> 5340		folio = vma->vm_ops->uffd_ops->get_folio_noalloc(inode, vmf->pgoff);
  5341		if (!IS_ERR_OR_NULL(folio)) {
  5342			/*
  5343			 * TODO: provide a flag for get_folio_noalloc() to avoid
  5344			 * locking (or even the extra reference?)
  5345			 */
  5346			folio_unlock(folio);
  5347			folio_put(folio);
  5348			if (userfaultfd_minor(vma))
  5349				return handle_userfault(vmf, VM_UFFD_MINOR);
  5350		} else {
  5351			if (userfaultfd_missing(vma))
  5352				return handle_userfault(vmf, VM_UFFD_MISSING);
  5353		}
  5354	
  5355		return 0;
  5356	}
  5357	

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

                 reply	other threads:[~2026-02-23 16:25 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=202602240004.Sop2OCIr-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=peterx@redhat.com \
    --cc=rppt@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.