Re: [linux-next:master 4466/4894] kernel/bpf/syscall.c:305:58: error: 'VMALLOC_END' undeclared; did you mean 'VM_LOCKED'?

[Christoph Hellwig <hch@lst.de>]

On Sat, Apr 25, 2020 at 05:09:09PM -0700, Andrew Morton wrote:
> On Sun, 26 Apr 2020 04:25:54 +0800 kbuild test robot <lkp@intel.com> wrote:
> 
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head:   8bdabd09ec86a993419c8c98a4f34c12bc902c6c
> > commit: d4493a599f1aa34153b047da482cf6419f3c79dc [4466/4894] mm: remove vmalloc_user_node_flags
> > config: riscv-randconfig-a001-20200426 (attached as .config)
> > compiler: riscv64-linux-gcc (GCC) 9.3.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 d4493a599f1aa34153b047da482cf6419f3c79dc
> >         # save the attached .config to linux build tree
> >         COMPILER_INSTALL_PATH=$HOME/0day GCC_VERSION=9.3.0 make.cross ARCH=riscv 
> > 
> >    kernel/bpf/syscall.c: In function '__bpf_map_area_alloc':
> > >> kernel/bpf/syscall.c:305:58: error: 'VMALLOC_END' undeclared (first use in this function); did you mean 'VM_LOCKED'?
> >      305 |  return __vmalloc_node_range(size, align, VMALLOC_START, VMALLOC_END,
> 
> CONFIG_MMU=n.
> 
> I guess this will suffice?

It should.  But I wonder if BPF actually even has a chance of working
on nommu configs..

> 
> --- a/arch/riscv/include/asm/pgtable.h~mm-switch-the-test_vmalloc-module-to-use-__vmalloc_node-fix-fix
> +++ a/arch/riscv/include/asm/pgtable.h
> @@ -472,9 +472,9 @@ static inline int ptep_clear_flush_young
>  
>  #define PAGE_KERNEL		__pgprot(0)
>  #define swapper_pg_dir		NULL
> +#define TASK_SIZE		0xffffffffUL
>  #define VMALLOC_START		0
> -
> -#define TASK_SIZE 0xffffffffUL
> +#define VMALLOC_END		TASK_SIZE
>  
>  #endif /* !CONFIG_MMU */
>  
> 
> It could be any value, really - we just need VMALLOC_END there to make
> the compiler happy.
---end quoted text---