linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: mpenttil@redhat.com, linux-mm@kvack.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	"Mika Penttilä" <mpenttil@redhat.com>,
	"David Hildenbrand" <david@redhat.com>,
	"Jason Gunthorpe" <jgg@nvidia.com>,
	"Leon Romanovsky" <leonro@nvidia.com>,
	"Alistair Popple" <apopple@nvidia.com>,
	"Balbir Singh" <balbirs@nvidia.com>, "Zi Yan" <ziy@nvidia.com>,
	"Matthew Brost" <matthew.brost@intel.com>
Subject: Re: [PATCH v3 1/3] mm: unified hmm fault and migrate device pagewalk paths
Date: Tue, 27 Jan 2026 02:48:43 +0800	[thread overview]
Message-ID: <202601270202.cL2IcE86-lkp@intel.com> (raw)
In-Reply-To: <20260126111939.1332983-2-mpenttil@redhat.com>

Hi,

kernel test robot noticed the following build errors:

[auto build test ERROR on 63804fed149a6750ffd28610c5c1c98cce6bd377]

url:    https://github.com/intel-lab-lkp/linux/commits/mpenttil-redhat-com/mm-unified-hmm-fault-and-migrate-device-pagewalk-paths/20260126-192236
base:   63804fed149a6750ffd28610c5c1c98cce6bd377
patch link:    https://lore.kernel.org/r/20260126111939.1332983-2-mpenttil%40redhat.com
patch subject: [PATCH v3 1/3] mm: unified hmm fault and migrate device pagewalk paths
config: x86_64-randconfig-013-20260126 (https://download.01.org/0day-ci/archive/20260127/202601270202.cL2IcE86-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260127/202601270202.cL2IcE86-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/202601270202.cL2IcE86-lkp@intel.com/

All errors (new ones prefixed by >>):

>> mm/hmm.c:927:31: error: no member named 'owner' in 'struct mmu_notifier_range'
     927 |         if (!hmm_vma_walk->mmu_range.owner) {
         |              ~~~~~~~~~~~~~~~~~~~~~~~ ^
   mm/hmm.c:1343:24: error: call to undeclared function 'mmu_interval_check_retry'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
    1343 |                 if (is_fault_path && mmu_interval_check_retry(range->notifier,
         |                                      ^
   mm/hmm.c:1361:29: error: no member named 'owner' in 'struct mmu_notifier_range'
    1361 |             hmm_vma_walk.mmu_range.owner) {
         |             ~~~~~~~~~~~~~~~~~~~~~~ ^
   3 errors generated.


vim +927 mm/hmm.c

   906	
   907	static int hmm_vma_capture_migrate_range(unsigned long start,
   908						 unsigned long end,
   909						 struct mm_walk *walk)
   910	{
   911		struct hmm_vma_walk *hmm_vma_walk = walk->private;
   912		struct hmm_range *range = hmm_vma_walk->range;
   913	
   914		if (!hmm_select_migrate(range))
   915			return 0;
   916	
   917		if (hmm_vma_walk->vma && (hmm_vma_walk->vma != walk->vma))
   918			return -ERANGE;
   919	
   920		hmm_vma_walk->vma = walk->vma;
   921		hmm_vma_walk->start = start;
   922		hmm_vma_walk->end = end;
   923	
   924		if (end - start > range->end - range->start)
   925			return -ERANGE;
   926	
 > 927		if (!hmm_vma_walk->mmu_range.owner) {
   928			mmu_notifier_range_init_owner(&hmm_vma_walk->mmu_range, MMU_NOTIFY_MIGRATE, 0,
   929						      walk->vma->vm_mm, start, end,
   930						      range->dev_private_owner);
   931			mmu_notifier_invalidate_range_start(&hmm_vma_walk->mmu_range);
   932		}
   933	
   934		return 0;
   935	}
   936	

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


  reply	other threads:[~2026-01-26 18:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-26 11:19 [PATCH v3 0/3] Migrate on fault for device pages mpenttil
2026-01-26 11:19 ` [PATCH v3 1/3] mm: unified hmm fault and migrate device pagewalk paths mpenttil
2026-01-26 18:48   ` kernel test robot [this message]
2026-01-26 18:48   ` kernel test robot
2026-01-26 11:19 ` [PATCH v3 2/3] mm: add new testcase for the migrate on fault case mpenttil
2026-01-26 11:19 ` [PATCH v3 3/3] mm:/migrate_device.c: remove migrate_vma_collect_*() functions mpenttil

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=202601270202.cL2IcE86-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=apopple@nvidia.com \
    --cc=balbirs@nvidia.com \
    --cc=david@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=leonro@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=llvm@lists.linux.dev \
    --cc=matthew.brost@intel.com \
    --cc=mpenttil@redhat.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ziy@nvidia.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