From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:openEuler-1.0-LTS 18192/21544] mm/memory.c:1546:24: error: implicit declaration of function 'hugetlb_insert_hugepage_pte_by_pa'; did you mean 'hugetlb_insert__hugepage_pte_by_pa'?
Date: Mon, 15 Jan 2024 05:02:20 +0800 [thread overview]
Message-ID: <202401150459.fFshvuVQ-lkp@intel.com> (raw)
tree: https://gitee.com/openeuler/kernel.git openEuler-1.0-LTS
head: 1f0983450549eeea71fb9333517330947a779262
commit: 18f49509eef01d1ee6ed81899298994f2f88dd2a [18192/21544] ascend: share_pool: Use remap_pfn_range to share kva to uva
config: x86_64-allnoconfig (https://download.01.org/0day-ci/archive/20240115/202401150459.fFshvuVQ-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240115/202401150459.fFshvuVQ-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/202401150459.fFshvuVQ-lkp@intel.com/
All errors (new ones prefixed by >>):
mm/memory.c: In function 'vm_insert_page':
>> mm/memory.c:1546:24: error: implicit declaration of function 'hugetlb_insert_hugepage_pte_by_pa'; did you mean 'hugetlb_insert__hugepage_pte_by_pa'? [-Werror=implicit-function-declaration]
1546 | return hugetlb_insert_hugepage_pte_by_pa(vma->vm_mm, addr,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| hugetlb_insert__hugepage_pte_by_pa
cc1: some warnings being treated as errors
vim +1546 mm/memory.c
1504
1505 /**
1506 * vm_insert_page - insert single page into user vma
1507 * @vma: user vma to map to
1508 * @addr: target user address of this page
1509 * @page: source kernel page
1510 *
1511 * This allows drivers to insert individual pages they've allocated
1512 * into a user vma.
1513 *
1514 * The page has to be a nice clean _individual_ kernel allocation.
1515 * If you allocate a compound page, you need to have marked it as
1516 * such (__GFP_COMP), or manually just split the page up yourself
1517 * (see split_page()).
1518 *
1519 * NOTE! Traditionally this was done with "remap_pfn_range()" which
1520 * took an arbitrary page protection parameter. This doesn't allow
1521 * that. Your vma protection will have to be set up correctly, which
1522 * means that if you want a shared writable mapping, you'd better
1523 * ask for a shared writable mapping!
1524 *
1525 * The page does not need to be reserved.
1526 *
1527 * Usually this function is called from f_op->mmap() handler
1528 * under mm->mmap_sem write-lock, so it can change vma->vm_flags.
1529 * Caller must set VM_MIXEDMAP on vma if it wants to call this
1530 * function from other places, for example from page-fault handler.
1531 */
1532 int vm_insert_page(struct vm_area_struct *vma, unsigned long addr,
1533 struct page *page)
1534 {
1535 if (addr < vma->vm_start || addr >= vma->vm_end)
1536 return -EFAULT;
1537 if (!page_count(page))
1538 return -EINVAL;
1539 if (!(vma->vm_flags & VM_MIXEDMAP)) {
1540 BUG_ON(down_read_trylock(&vma->vm_mm->mmap_sem));
1541 BUG_ON(vma->vm_flags & VM_PFNMAP);
1542 vma->vm_flags |= VM_MIXEDMAP;
1543 }
1544
1545 if (sp_check_hugepage(page))
> 1546 return hugetlb_insert_hugepage_pte_by_pa(vma->vm_mm, addr,
1547 vma->vm_page_prot, page_to_phys(page));
1548 else
1549 return insert_page(vma, addr, page, vma->vm_page_prot);
1550 }
1551 EXPORT_SYMBOL(vm_insert_page);
1552
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-14 21:04 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=202401150459.fFshvuVQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=kernel@openeuler.org \
--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.