From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android16-6.12-desktop 11/11] mm/hmm.c:595:21: error: implicit declaration of function 'mmu_interval_check_retry'
Date: Sun, 13 Jul 2025 07:48:08 +0800 [thread overview]
Message-ID: <202507130727.deZ6Vccv-lkp@intel.com> (raw)
Hi Ryan,
First bad commit (maybe != root cause):
tree: https://android.googlesource.com/kernel/common android16-6.12-desktop
head: dc1cbab31745422f559829a3be0cc2bcfd2967ae
commit: e481300819c9576070aa3b7b8edc2da716d0e3c4 [11/11] ANDROID: GKI: x86: add HMM_MIRROR as DRM hidden dep
config: x86_64-randconfig-104-20250712 (https://download.01.org/0day-ci/archive/20250713/202507130727.deZ6Vccv-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14+deb12u1) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250713/202507130727.deZ6Vccv-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/202507130727.deZ6Vccv-lkp@intel.com/
All errors (new ones prefixed by >>):
mm/hmm.c: In function 'hmm_range_fault':
>> mm/hmm.c:595:21: error: implicit declaration of function 'mmu_interval_check_retry' [-Werror=implicit-function-declaration]
595 | if (mmu_interval_check_retry(range->notifier,
| ^~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for CAN_RX_OFFLOAD
Depends on [n]: NETDEVICES [=y] && CAN_DEV [=n] && CAN_NETLINK [=n]
Selected by [y]:
- GKI_HIDDEN_MCP251XFD_CONFIGS [=y] && 64BIT [=y]
vim +/mmu_interval_check_retry +595 mm/hmm.c
7b86ac3371b70c Christoph Hellwig 2019-08-28 562
9a4903e49e495b Christoph Hellwig 2019-07-25 563 /**
9a4903e49e495b Christoph Hellwig 2019-07-25 564 * hmm_range_fault - try to fault some address in a virtual address range
f970b977e068aa Jason Gunthorpe 2020-03-27 565 * @range: argument structure
9a4903e49e495b Christoph Hellwig 2019-07-25 566 *
be957c886d92aa Jason Gunthorpe 2020-05-01 567 * Returns 0 on success or one of the following error codes:
73231612dc7c90 Jérôme Glisse 2019-05-13 568 *
9a4903e49e495b Christoph Hellwig 2019-07-25 569 * -EINVAL: Invalid arguments or mm or virtual address is in an invalid vma
9a4903e49e495b Christoph Hellwig 2019-07-25 570 * (e.g., device file vma).
73231612dc7c90 Jérôme Glisse 2019-05-13 571 * -ENOMEM: Out of memory.
9a4903e49e495b Christoph Hellwig 2019-07-25 572 * -EPERM: Invalid permission (e.g., asking for write and range is read
9a4903e49e495b Christoph Hellwig 2019-07-25 573 * only).
9a4903e49e495b Christoph Hellwig 2019-07-25 574 * -EBUSY: The range has been invalidated and the caller needs to wait for
9a4903e49e495b Christoph Hellwig 2019-07-25 575 * the invalidation to finish.
f970b977e068aa Jason Gunthorpe 2020-03-27 576 * -EFAULT: A page was requested to be valid and could not be made valid
f970b977e068aa Jason Gunthorpe 2020-03-27 577 * ie it has no backing VMA or it is illegal to access
74eee180b935fc Jérôme Glisse 2017-09-08 578 *
f970b977e068aa Jason Gunthorpe 2020-03-27 579 * This is similar to get_user_pages(), except that it can read the page tables
f970b977e068aa Jason Gunthorpe 2020-03-27 580 * without mutating them (ie causing faults).
74eee180b935fc Jérôme Glisse 2017-09-08 581 */
be957c886d92aa Jason Gunthorpe 2020-05-01 582 int hmm_range_fault(struct hmm_range *range)
74eee180b935fc Jérôme Glisse 2017-09-08 583 {
d28c2c9a487708 Ralph Campbell 2019-11-04 584 struct hmm_vma_walk hmm_vma_walk = {
d28c2c9a487708 Ralph Campbell 2019-11-04 585 .range = range,
d28c2c9a487708 Ralph Campbell 2019-11-04 586 .last = range->start,
d28c2c9a487708 Ralph Campbell 2019-11-04 587 };
a22dd506400d0f Jason Gunthorpe 2019-11-12 588 struct mm_struct *mm = range->notifier->mm;
74eee180b935fc Jérôme Glisse 2017-09-08 589 int ret;
74eee180b935fc Jérôme Glisse 2017-09-08 590
42fc541404f249 Michel Lespinasse 2020-06-08 591 mmap_assert_locked(mm);
74eee180b935fc Jérôme Glisse 2017-09-08 592
a3e0d41c2b1f86 Jérôme Glisse 2019-05-13 593 do {
a3e0d41c2b1f86 Jérôme Glisse 2019-05-13 594 /* If range is no longer valid force retry. */
a22dd506400d0f Jason Gunthorpe 2019-11-12 @595 if (mmu_interval_check_retry(range->notifier,
:::::: The code at line 595 was first introduced by commit
:::::: a22dd506400d0f4784ad596f073b9eb5ed7c6a2a mm/hmm: remove hmm_mirror and related
:::::: TO: Jason Gunthorpe <jgg@mellanox.com>
:::::: CC: Jason Gunthorpe <jgg@mellanox.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-07-12 23:48 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=202507130727.deZ6Vccv-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.