From: Randy Dunlap <rdunlap@infradead.org>
To: kernel test robot <lkp@intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [hnaz-linux-mm:master 1/421] arch/powerpc/include/asm/mmu.h:139:22: error: unknown type name 'next_tlbcam_idx'
Date: Wed, 26 Aug 2020 23:03:55 -0700 [thread overview]
Message-ID: <f51b2b14-495a-b7fa-34d8-e6de2b108b37@infradead.org> (raw)
In-Reply-To: <202008251009.zFrMbVzh%lkp@intel.com>
Hi,
I can't reproduce this with mmotm of 2020-08-25...
More below.
On 8/24/20 7:11 PM, kernel test robot wrote:
> tree: https://github.com/hnaz/linux-mm master
> head: 2932a9e66c580f3c8d95ec27716d437198fb4c94
> commit: 4c4ef2c53a5e517248011bd1908235df1257e66d [1/421] origin
> config: powerpc-ppc64e_defconfig (attached as .config)
> compiler: powerpc64-linux-gcc (GCC) 9.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
> git checkout 4c4ef2c53a5e517248011bd1908235df1257e66d
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=powerpc
>
> 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 >>):
>
> In file included from arch/powerpc/include/asm/paca.h:18,
> from arch/powerpc/include/asm/percpu.h:13,
> from include/linux/random.h:14,
> from include/linux/net.h:18,
> from fs/cifs/netmisc.c:12:
>>> arch/powerpc/include/asm/mmu.h:139:22: error: unknown type name 'next_tlbcam_idx'
That's not a type name. It's a variable name. The type is 'int'.
> 139 | DECLARE_PER_CPU(int, next_tlbcam_idx);
> | ^~~~~~~~~~~~~~~
> --
> In file included from arch/powerpc/include/asm/paca.h:18,
> from arch/powerpc/include/asm/percpu.h:13,
> from include/linux/random.h:14,
> from include/linux/net.h:18,
> from fs/cifs/netmisc.c:12:
>>> arch/powerpc/include/asm/mmu.h:139:22: error: unknown type name 'next_tlbcam_idx'
> 139 | DECLARE_PER_CPU(int, next_tlbcam_idx);
> | ^~~~~~~~~~~~~~~
> In file included from fs/cifs/cifsglob.h:32,
> from fs/cifs/netmisc.c:22:
> fs/cifs/smb2pdu.h:28:10: fatal error: cifsacl.h: No such file or directory
> 28 | #include <cifsacl.h>
> | ^~~~~~~~~~~
#include <cifsacl.h>
That probably could be changed to "cifsacl.h".
> compilation terminated.
>
> # https://github.com/hnaz/linux-mm/commit/4c4ef2c53a5e517248011bd1908235df1257e66d
> git remote add hnaz-linux-mm https://github.com/hnaz/linux-mm
> git fetch --no-tags hnaz-linux-mm master
> git checkout 4c4ef2c53a5e517248011bd1908235df1257e66d
> vim +/next_tlbcam_idx +139 arch/powerpc/include/asm/mmu.h
>
> 7c03d653cd2577 Benjamin Herrenschmidt 2008-12-18 136
> 3160b09796129a Becky Bruce 2011-06-28 137 #ifdef CONFIG_PPC_FSL_BOOK3E
> 3160b09796129a Becky Bruce 2011-06-28 138 #include <asm/percpu.h>
> 3160b09796129a Becky Bruce 2011-06-28 @139 DECLARE_PER_CPU(int, next_tlbcam_idx);
> 3160b09796129a Becky Bruce 2011-06-28 140 #endif
> 3160b09796129a Becky Bruce 2011-06-28 141
>
> :::::: The code at line 139 was first introduced by commit
> :::::: 3160b09796129abc9523ea3cd1633b0faba64a02 powerpc: Create next_tlbcam_idx percpu variable for FSL_BOOKE
It's surprising that a patch from 2011 would start showing problems now.
> :::::: TO: Becky Bruce <beckyb@kernel.crashing.org>
> :::::: CC: Kumar Gala <galak@kernel.crashing.org>
--
~Randy
next prev parent reply other threads:[~2020-08-27 6:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 2:11 kernel test robot
2020-08-27 6:03 ` Randy Dunlap [this message]
2020-08-28 6:46 ` [kbuild-all] " Rong Chen
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=f51b2b14-495a-b7fa-34d8-e6de2b108b37@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
/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