From: kernel test robot <lkp@intel.com>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>
Cc: oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Subject: [akpm-mm:mm-unstable 357/379] mm/vma.h:113:28: error: 'FIRST_USER_ADDRESS' undeclared
Date: Sat, 24 Aug 2024 23:14:18 +0800 [thread overview]
Message-ID: <202408242304.1A1fXTgE-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
head: b659edec079c90012cf8d05624e312d1062b8b87
commit: ca39aca8db2d78ff82356defba75d14ce78a67b9 [357/379] mm/vma: track start and end for munmap in vma_munmap_struct
config: m68k-allnoconfig (https://download.01.org/0day-ci/archive/20240824/202408242304.1A1fXTgE-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240824/202408242304.1A1fXTgE-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/202408242304.1A1fXTgE-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from mm/internal.h:22,
from mm/filemap.c:52:
mm/vma.h: In function 'init_vma_munmap':
>> mm/vma.h:113:28: error: 'FIRST_USER_ADDRESS' undeclared (first use in this function)
113 | vms->unmap_start = FIRST_USER_ADDRESS;
| ^~~~~~~~~~~~~~~~~~
mm/vma.h:113:28: note: each undeclared identifier is reported only once for each function it appears in
>> mm/vma.h:114:26: error: 'USER_PGTABLES_CEILING' undeclared (first use in this function)
114 | vms->unmap_end = USER_PGTABLES_CEILING;
| ^~~~~~~~~~~~~~~~~~~~~
vim +/FIRST_USER_ADDRESS +113 mm/vma.h
67
68 /* Required for do_brk_flags(). */
69 void init_vma_prep(struct vma_prepare *vp,
70 struct vm_area_struct *vma);
71
72 /* Required for do_brk_flags(). */
73 void vma_complete(struct vma_prepare *vp,
74 struct vma_iterator *vmi, struct mm_struct *mm);
75
76 int vma_expand(struct vma_iterator *vmi, struct vm_area_struct *vma,
77 unsigned long start, unsigned long end, pgoff_t pgoff,
78 struct vm_area_struct *next);
79
80 int vma_shrink(struct vma_iterator *vmi, struct vm_area_struct *vma,
81 unsigned long start, unsigned long end, pgoff_t pgoff);
82
83 /*
84 * init_vma_munmap() - Initializer wrapper for vma_munmap_struct
85 * @vms: The vma munmap struct
86 * @vmi: The vma iterator
87 * @vma: The first vm_area_struct to munmap
88 * @start: The aligned start address to munmap
89 * @end: The aligned end address to munmap
90 * @uf: The userfaultfd list_head
91 * @unlock: Unlock after the operation. Only unlocked on success
92 */
93 static inline void init_vma_munmap(struct vma_munmap_struct *vms,
94 struct vma_iterator *vmi, struct vm_area_struct *vma,
95 unsigned long start, unsigned long end, struct list_head *uf,
96 bool unlock)
97 {
98 vms->vmi = vmi;
99 vms->vma = vma;
100 if (vma) {
101 vms->mm = vma->vm_mm;
102 vms->start = start;
103 vms->end = end;
104 } else {
105 vms->mm = NULL;
106 vms->start = vms->end = 0;
107 }
108 vms->unlock = unlock;
109 vms->uf = uf;
110 vms->vma_count = 0;
111 vms->nr_pages = vms->locked_vm = vms->nr_accounted = 0;
112 vms->exec_vm = vms->stack_vm = vms->data_vm = 0;
> 113 vms->unmap_start = FIRST_USER_ADDRESS;
> 114 vms->unmap_end = USER_PGTABLES_CEILING;
115 }
116
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-08-24 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-24 15:14 kernel test robot [this message]
2024-08-24 19:45 ` [akpm-mm:mm-unstable 357/379] mm/vma.h:113:28: error: 'FIRST_USER_ADDRESS' undeclared Lorenzo Stoakes
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=202408242304.1A1fXTgE-lkp@intel.com \
--to=lkp@intel.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).