public inbox for linux-hyperv@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>,
	kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
	decui@microsoft.com
Cc: oe-kbuild-all@lists.linux.dev, linux-hyperv@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 5/5] Drivers: hv: Add support for movable memory regions
Date: Thu, 16 Oct 2025 22:47:57 +0800	[thread overview]
Message-ID: <202510162231.7UOw1jQq-lkp@intel.com> (raw)
In-Reply-To: <176057443695.74314.10584965103467299030.stgit@skinsburskii-cloud-desktop.internal.cloudapp.net>

Hi Stanislav,

kernel test robot noticed the following build errors:

[auto build test ERROR on linus/master]
[also build test ERROR on v6.18-rc1 next-20251015]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Stanislav-Kinsburskii/Drivers-hv-Refactor-and-rename-memory-region-handling-functions/20251016-082944
base:   linus/master
patch link:    https://lore.kernel.org/r/176057443695.74314.10584965103467299030.stgit%40skinsburskii-cloud-desktop.internal.cloudapp.net
patch subject: [PATCH v5 5/5] Drivers: hv: Add support for movable memory regions
config: x86_64-buildonly-randconfig-002-20251016 (https://download.01.org/0day-ci/archive/20251016/202510162231.7UOw1jQq-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/20251016/202510162231.7UOw1jQq-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/202510162231.7UOw1jQq-lkp@intel.com/

All errors (new ones prefixed by >>):

   mm/hmm.c: In function 'hmm_range_fault':
>> mm/hmm.c:667:21: error: implicit declaration of function 'mmu_interval_check_retry' [-Wimplicit-function-declaration]
     667 |                 if (mmu_interval_check_retry(range->notifier,
         |                     ^~~~~~~~~~~~~~~~~~~~~~~~


vim +/mmu_interval_check_retry +667 mm/hmm.c

7b86ac3371b70c Christoph Hellwig 2019-08-28  634  
9a4903e49e495b Christoph Hellwig 2019-07-25  635  /**
9a4903e49e495b Christoph Hellwig 2019-07-25  636   * hmm_range_fault - try to fault some address in a virtual address range
f970b977e068aa Jason Gunthorpe   2020-03-27  637   * @range:	argument structure
9a4903e49e495b Christoph Hellwig 2019-07-25  638   *
be957c886d92aa Jason Gunthorpe   2020-05-01  639   * Returns 0 on success or one of the following error codes:
73231612dc7c90 Jérôme Glisse     2019-05-13  640   *
9a4903e49e495b Christoph Hellwig 2019-07-25  641   * -EINVAL:	Invalid arguments or mm or virtual address is in an invalid vma
9a4903e49e495b Christoph Hellwig 2019-07-25  642   *		(e.g., device file vma).
73231612dc7c90 Jérôme Glisse     2019-05-13  643   * -ENOMEM:	Out of memory.
9a4903e49e495b Christoph Hellwig 2019-07-25  644   * -EPERM:	Invalid permission (e.g., asking for write and range is read
9a4903e49e495b Christoph Hellwig 2019-07-25  645   *		only).
9a4903e49e495b Christoph Hellwig 2019-07-25  646   * -EBUSY:	The range has been invalidated and the caller needs to wait for
9a4903e49e495b Christoph Hellwig 2019-07-25  647   *		the invalidation to finish.
f970b977e068aa Jason Gunthorpe   2020-03-27  648   * -EFAULT:     A page was requested to be valid and could not be made valid
f970b977e068aa Jason Gunthorpe   2020-03-27  649   *              ie it has no backing VMA or it is illegal to access
74eee180b935fc Jérôme Glisse     2017-09-08  650   *
f970b977e068aa Jason Gunthorpe   2020-03-27  651   * This is similar to get_user_pages(), except that it can read the page tables
f970b977e068aa Jason Gunthorpe   2020-03-27  652   * without mutating them (ie causing faults).
74eee180b935fc Jérôme Glisse     2017-09-08  653   */
be957c886d92aa Jason Gunthorpe   2020-05-01  654  int hmm_range_fault(struct hmm_range *range)
74eee180b935fc Jérôme Glisse     2017-09-08  655  {
d28c2c9a487708 Ralph Campbell    2019-11-04  656  	struct hmm_vma_walk hmm_vma_walk = {
d28c2c9a487708 Ralph Campbell    2019-11-04  657  		.range = range,
d28c2c9a487708 Ralph Campbell    2019-11-04  658  		.last = range->start,
d28c2c9a487708 Ralph Campbell    2019-11-04  659  	};
a22dd506400d0f Jason Gunthorpe   2019-11-12  660  	struct mm_struct *mm = range->notifier->mm;
74eee180b935fc Jérôme Glisse     2017-09-08  661  	int ret;
74eee180b935fc Jérôme Glisse     2017-09-08  662  
42fc541404f249 Michel Lespinasse 2020-06-08  663  	mmap_assert_locked(mm);
74eee180b935fc Jérôme Glisse     2017-09-08  664  
a3e0d41c2b1f86 Jérôme Glisse     2019-05-13  665  	do {
a3e0d41c2b1f86 Jérôme Glisse     2019-05-13  666  		/* If range is no longer valid force retry. */
a22dd506400d0f Jason Gunthorpe   2019-11-12 @667  		if (mmu_interval_check_retry(range->notifier,
a22dd506400d0f Jason Gunthorpe   2019-11-12  668  					     range->notifier_seq))
2bcbeaefde2f03 Christoph Hellwig 2019-07-24  669  			return -EBUSY;
d28c2c9a487708 Ralph Campbell    2019-11-04  670  		ret = walk_page_range(mm, hmm_vma_walk.last, range->end,
7b86ac3371b70c Christoph Hellwig 2019-08-28  671  				      &hmm_walk_ops, &hmm_vma_walk);
be957c886d92aa Jason Gunthorpe   2020-05-01  672  		/*
be957c886d92aa Jason Gunthorpe   2020-05-01  673  		 * When -EBUSY is returned the loop restarts with
be957c886d92aa Jason Gunthorpe   2020-05-01  674  		 * hmm_vma_walk.last set to an address that has not been stored
be957c886d92aa Jason Gunthorpe   2020-05-01  675  		 * in pfns. All entries < last in the pfn array are set to their
be957c886d92aa Jason Gunthorpe   2020-05-01  676  		 * output, and all >= are still at their input values.
be957c886d92aa Jason Gunthorpe   2020-05-01  677  		 */
d28c2c9a487708 Ralph Campbell    2019-11-04  678  	} while (ret == -EBUSY);
73231612dc7c90 Jérôme Glisse     2019-05-13  679  	return ret;
74eee180b935fc Jérôme Glisse     2017-09-08  680  }
73231612dc7c90 Jérôme Glisse     2019-05-13  681  EXPORT_SYMBOL(hmm_range_fault);
8cad4713056612 Leon Romanovsky   2025-04-28  682  

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

  reply	other threads:[~2025-10-16 14:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-16  0:26 [PATCH v5 0/5] Introduce movable pages for Hyper-V guests Stanislav Kinsburskii
2025-10-16  0:26 ` [PATCH v5 1/5] Drivers: hv: Refactor and rename memory region handling functions Stanislav Kinsburskii
2025-10-16  0:27 ` [PATCH v5 2/5] Drivers: hv: Centralize guest memory region destruction Stanislav Kinsburskii
2025-10-16  0:27 ` [PATCH v5 3/5] Drivers: hv: Batch GPA unmap operations to improve large region performance Stanislav Kinsburskii
2025-10-16  0:27 ` [PATCH v5 4/5] Drivers: hv: Ensure large page GPA mapping is PMD-aligned Stanislav Kinsburskii
2025-10-16  0:27 ` [PATCH v5 5/5] Drivers: hv: Add support for movable memory regions Stanislav Kinsburskii
2025-10-16 14:47   ` kernel test robot [this message]
2025-10-17 23:55   ` Mukesh R
2025-10-20 17:35     ` Stanislav Kinsburskii

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=202510162231.7UOw1jQq-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=decui@microsoft.com \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=skinsburskii@linux.microsoft.com \
    --cc=wei.liu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox