From: kernel test robot <lkp@intel.com>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [akpm-mm:mm-unstable 338/431] mm/nommu.c:579:9: error: implicit declaration of function 'vma_mas_store'; did you mean 'mas_store'?
Date: Tue, 10 May 2022 20:11:06 +0800 [thread overview]
Message-ID: <202205102017.SiSV7Y9l-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
head: 584a50635cc1deee2eeab5a17dfdcf9db7add21b
commit: a245f2ec995564195c1956813ff4fee7a894f099 [338/431] mm: remove rb tree.
config: m68k-randconfig-r006-20220509 (https://download.01.org/0day-ci/archive/20220510/202205102017.SiSV7Y9l-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 11.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git/commit/?id=a245f2ec995564195c1956813ff4fee7a894f099
git remote add akpm-mm https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git
git fetch --no-tags akpm-mm mm-unstable
git checkout a245f2ec995564195c1956813ff4fee7a894f099
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=m68k SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
mm/nommu.c: In function 'add_vma_to_mm':
>> mm/nommu.c:579:9: error: implicit declaration of function 'vma_mas_store'; did you mean 'mas_store'? [-Werror=implicit-function-declaration]
579 | vma_mas_store(vma, &mas);
| ^~~~~~~~~~~~~
| mas_store
mm/nommu.c: In function 'delete_vma_from_mm':
>> mm/nommu.c:615:9: error: implicit declaration of function 'vma_mas_remove' [-Werror=implicit-function-declaration]
615 | vma_mas_remove(vma, &mas);
| ^~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +579 mm/nommu.c
547
548 /*
549 * add a VMA into a process's mm_struct in the appropriate place in the list
550 * and tree and add to the address space's page tree also if not an anonymous
551 * page
552 * - should be called with mm->mmap_lock held writelocked
553 */
554 static void add_vma_to_mm(struct mm_struct *mm, struct vm_area_struct *vma)
555 {
556 struct address_space *mapping;
557 struct vm_area_struct *prev;
558 MA_STATE(mas, &mm->mm_mt, vma->vm_start, vma->vm_end);
559
560 BUG_ON(!vma->vm_region);
561
562 mm->map_count++;
563 vma->vm_mm = mm;
564
565 /* add the VMA to the mapping */
566 if (vma->vm_file) {
567 mapping = vma->vm_file->f_mapping;
568
569 i_mmap_lock_write(mapping);
570 flush_dcache_mmap_lock(mapping);
571 vma_interval_tree_insert(vma, &mapping->i_mmap);
572 flush_dcache_mmap_unlock(mapping);
573 i_mmap_unlock_write(mapping);
574 }
575
576 prev = mas_prev(&mas, 0);
577 mas_reset(&mas);
578 /* add the VMA to the tree */
> 579 vma_mas_store(vma, &mas);
580 __vma_link_list(mm, vma, prev);
581 }
582
583 /*
584 * delete a VMA from its owning mm_struct and address space
585 */
586 static void delete_vma_from_mm(struct vm_area_struct *vma)
587 {
588 int i;
589 struct address_space *mapping;
590 struct mm_struct *mm = vma->vm_mm;
591 struct task_struct *curr = current;
592 MA_STATE(mas, &vma->vm_mm->mm_mt, 0, 0);
593
594 mm->map_count--;
595 for (i = 0; i < VMACACHE_SIZE; i++) {
596 /* if the vma is cached, invalidate the entire cache */
597 if (curr->vmacache.vmas[i] == vma) {
598 vmacache_invalidate(mm);
599 break;
600 }
601 }
602
603 /* remove the VMA from the mapping */
604 if (vma->vm_file) {
605 mapping = vma->vm_file->f_mapping;
606
607 i_mmap_lock_write(mapping);
608 flush_dcache_mmap_lock(mapping);
609 vma_interval_tree_remove(vma, &mapping->i_mmap);
610 flush_dcache_mmap_unlock(mapping);
611 i_mmap_unlock_write(mapping);
612 }
613
614 /* remove from the MM's tree and list */
> 615 vma_mas_remove(vma, &mas);
616 __vma_unlink_list(mm, vma);
617 }
618
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-05-10 12:11 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=202205102017.SiSV7Y9l-lkp@intel.com \
--to=lkp@intel.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.