From: kbuild test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kbuild-all@lists.01.org,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 12169/12191] mm/mmu_gather.c:130:2: error: implicit declaration of function '__tlb_remove_table'; did you mean 'tlb_remove_table'?
Date: Wed, 5 Feb 2020 00:55:44 +0800 [thread overview]
Message-ID: <202002050040.LmmLcs2J%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2656 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: cee5a42837d4a6c4189f06f7bf355b97a24c3c93
commit: f86406aec90334bf576b9f9034ccff083d5ed44a [12169/12191] asm-generic/tlb: rename HAVE_RCU_TABLE_FREE
config: sparc64-randconfig-a001-20200204 (attached as .config)
compiler: sparc64-linux-gcc (GCC) 7.5.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout f86406aec90334bf576b9f9034ccff083d5ed44a
# save the attached .config to linux build tree
GCC_VERSION=7.5.0 make.cross ARCH=sparc64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
mm/mmu_gather.c: In function 'tlb_remove_table_one':
>> mm/mmu_gather.c:130:2: error: implicit declaration of function '__tlb_remove_table'; did you mean 'tlb_remove_table'? [-Werror=implicit-function-declaration]
__tlb_remove_table(table);
^~~~~~~~~~~~~~~~~~
tlb_remove_table
cc1: some warnings being treated as errors
vim +130 mm/mmu_gather.c
196d9d8bb71dea Peter Zijlstra 2018-09-03 119
196d9d8bb71dea Peter Zijlstra 2018-09-03 120 static void tlb_remove_table_one(void *table)
196d9d8bb71dea Peter Zijlstra 2018-09-03 121 {
196d9d8bb71dea Peter Zijlstra 2018-09-03 122 /*
196d9d8bb71dea Peter Zijlstra 2018-09-03 123 * This isn't an RCU grace period and hence the page-tables cannot be
196d9d8bb71dea Peter Zijlstra 2018-09-03 124 * assumed to be actually RCU-freed.
196d9d8bb71dea Peter Zijlstra 2018-09-03 125 *
196d9d8bb71dea Peter Zijlstra 2018-09-03 126 * It is however sufficient for software page-table walkers that rely on
196d9d8bb71dea Peter Zijlstra 2018-09-03 127 * IRQ disabling. See the comment near struct mmu_table_batch.
196d9d8bb71dea Peter Zijlstra 2018-09-03 128 */
196d9d8bb71dea Peter Zijlstra 2018-09-03 129 smp_call_function(tlb_remove_table_smp_sync, NULL, 1);
196d9d8bb71dea Peter Zijlstra 2018-09-03 @130 __tlb_remove_table(table);
196d9d8bb71dea Peter Zijlstra 2018-09-03 131 }
196d9d8bb71dea Peter Zijlstra 2018-09-03 132
:::::: The code at line 130 was first introduced by commit
:::::: 196d9d8bb71deaa2d1c7170c88a2f1a318363047 mm/memory: Move mmu_gather and TLB invalidation code into its own file
:::::: TO: Peter Zijlstra <peterz@infradead.org>
:::::: CC: Will Deacon <will.deacon@arm.com>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 28870 bytes --]
reply other threads:[~2020-02-04 16:56 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=202002050040.LmmLcs2J%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.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 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).