From: kernel test robot <lkp@intel.com>
To: Alistair Popple <apopple@nvidia.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [linux-next:master 3179/3438] arch/arm64/include/asm/tlbflush.h:268:53: error: 'vma' undeclared
Date: Wed, 19 Jul 2023 18:11:30 +0800 [thread overview]
Message-ID: <202307191848.Bd4gXW0j-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 352ce39a8bbaec0405793682be59fae120fc6b05
commit: 8c2be11e06f44391db3fc426528d8f17aa570992 [3179/3438] mmu_notifiers: call arch_invalidate_secondary_tlbs() when invalidating TLBs
config: arm64-randconfig-r002-20230718 (https://download.01.org/0day-ci/archive/20230719/202307191848.Bd4gXW0j-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230719/202307191848.Bd4gXW0j-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/202307191848.Bd4gXW0j-lkp@intel.com/
Note: the linux-next/master HEAD 352ce39a8bbaec0405793682be59fae120fc6b05 builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
In file included from arch/arm64/include/asm/pgtable.h:15,
from include/linux/pgtable.h:6,
from arch/arm64/include/asm/io.h:12,
from include/linux/io.h:13,
from include/linux/irq.h:20,
from include/asm-generic/hardirq.h:17,
from arch/arm64/include/asm/hardirq.h:17,
from include/linux/hardirq.h:11,
from include/linux/interrupt.h:11,
from include/linux/trace_recursion.h:5,
from include/linux/ftrace.h:10,
from arch/arm64/kernel/asm-offsets.c:12:
arch/arm64/include/asm/tlbflush.h: In function '__flush_tlb_page_nosync':
>> arch/arm64/include/asm/tlbflush.h:268:53: error: 'vma' undeclared (first use in this function)
268 | mmu_notifier_arch_invalidate_secondary_tlbs(vma->vm_mm, uaddr & PAGE_MASK,
| ^~~
arch/arm64/include/asm/tlbflush.h:268:53: note: each undeclared identifier is reported only once for each function it appears in
make[3]: *** [scripts/Makefile.build:116: arch/arm64/kernel/asm-offsets.s] Error 1 shuffle=251802209
make[3]: Target 'prepare' not remade because of errors.
make[2]: *** [Makefile:1275: prepare0] Error 2 shuffle=251802209
make[2]: Target 'prepare' not remade because of errors.
make[1]: *** [Makefile:234: __sub-make] Error 2 shuffle=251802209
make[1]: Target 'prepare' not remade because of errors.
make: *** [Makefile:234: __sub-make] Error 2 shuffle=251802209
make: Target 'prepare' not remade because of errors.
vim +/vma +268 arch/arm64/include/asm/tlbflush.h
258
259 static inline void __flush_tlb_page_nosync(struct mm_struct *mm,
260 unsigned long uaddr)
261 {
262 unsigned long addr;
263
264 dsb(ishst);
265 addr = __TLBI_VADDR(uaddr, ASID(mm));
266 __tlbi(vale1is, addr);
267 __tlbi_user(vale1is, addr);
> 268 mmu_notifier_arch_invalidate_secondary_tlbs(vma->vm_mm, uaddr & PAGE_MASK,
269 (uaddr & PAGE_MASK) + PAGE_SIZE);
270 }
271
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-07-19 10:12 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=202307191848.Bd4gXW0j-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox