linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: kernel test robot <lkp@intel.com>
Cc: "kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: gup_test.c:1:10: fatal error: fcntl.h: No such file or directory
Date: Tue, 27 Jul 2021 22:24:36 -0700	[thread overview]
Message-ID: <6af32770-1825-ff9a-ccf2-46600ed6fc7e@nvidia.com> (raw)
In-Reply-To: <202107281223.L61SLDL2-lkp@intel.com>

On 7/27/21 9:59 PM, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   7d549995d4e0d99b68e8a7793a0d23da6fc40fe8
> commit: 9c84f229268fa229e250b7225611d0eb7094fea0 mm/gup_benchmark: rename to mm/gup_test
> date:   7 months ago
> config: openrisc-randconfig-s031-20210726 (attached as .config)
> compiler: or1k-linux-gcc (GCC) 10.3.0
> reproduce:
>          wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>          chmod +x ~/bin/make.cross
>          # apt-get install sparse
>          # sparse version: v0.6.3-341-g8af24329-dirty
>          # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9c84f229268fa229e250b7225611d0eb7094fea0
>          git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>          git fetch --no-tags linus master
>          git checkout 9c84f229268fa229e250b7225611d0eb7094fea0
>          # save the attached .config to linux build tree
>          COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=openrisc SHELL=/bin/bash -C tools/testing/selftests/vm install
> 
> 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 >>):
> 
>>> gup_test.c:1:10: fatal error: fcntl.h: No such file or directory
>         1 | #include <fcntl.h>
>           |          ^~~~~~~~~
>     compilation terminated.
> 

I reproduced this via the above steps, and noticed that there are missing
header files for most (all?) of the vm tests, not just gup_test.c. And
not just fcntl.h, either. The error list continue as follows (below).

This seems like a new toolchain issue, right?


gup_test.c:1:10: fatal error: fcntl.h: No such file or directory
1 | #include <fcntl.h>
|          ^~~~~~~~~
compilation terminated.
compaction_test.c:10:10: fatal error: stdio.h: No such file or directory
10 | #include <stdio.h>
|          ^~~~~~~~~
In file included from hmm-tests.c:13:
../kselftest_harness.h:56:10: fatal error: asm/types.h: No such file or directory
56 | #include <asm/types.h>
|          ^~~~~~~~~~~~~
hugepage-shm.c:31:10: fatal error: stdlib.h: No such file or directory
31 | #include <stdlib.h>
|          ^~~~~~~~~~
make: *** [../lib.mk:139: /kernel_work/linux-github/tools/testing/selftests/vm/gup_test] Error 1
compilation terminated.
compilation terminated.
compilation terminated.
hugepage-mmap.c:20:10: fatal error: stdlib.h: No such file or directory
20 | #include <stdlib.h>
|          ^~~~~~~~~~
map_hugetlb.c:13:10: fatal error: stdlib.h: No such file or directory
13 | #include <stdlib.h>
|          ^~~~~~~~~~
compilation terminated.
compilation terminated.
on-fault-limit.c:2:10: fatal error: sys/mman.h: No such file or directory
2 | #include <sys/mman.h>
|          ^~~~~~~~~~~~
transhuge-stress.c:9:10: fatal error: stdlib.h: No such file or directory
9 | #include <stdlib.h>
|          ^~~~~~~~~~
map_fixed_noreplace.c:10:10: fatal error: sys/mman.h: No such file or directory
10 | #include <sys/mman.h>
|          ^~~~~~~~~~~~
mlock2-tests.c:3:10: fatal error: sys/mman.h: No such file or directory
3 | #include <sys/mman.h>
|          ^~~~~~~~~~~~
compilation terminated.
compilation terminated.
compilation terminated.
compilation terminated.
mremap_dontunmap.c:9:10: fatal error: sys/mman.h: No such file or directory
9 | #include <sys/mman.h>
|          ^~~~~~~~~~~~
compilation terminated.
va_128TBswitch.c:8:10: fatal error: stdio.h: No such file or directory
8 | #include <stdio.h>
|          ^~~~~~~~~
compilation terminated.
make: *** [../lib.mk:139: /kernel_work/linux-github/tools/testing/selftests/vm/hmm-tests] Error 1
make: *** [../lib.mk:139: /kernel_work/linux-github/tools/testing/selftests/vm/hugepage-shm] Error 1
map_populate.c:9:10: fatal error: errno.h: No such file or directory
9 | #include <errno.h>
|          ^~~~~~~~~
compilation terminated.
make: *** [../lib.mk:139: /kernel_work/linux-github/tools/testing/selftests/vm/compaction_test] Error 1
make: *** [../lib.mk:139: /kernel_work/linux-github/tools/testing/selftests/vm/hugepage-mmap] Error 1
mlock-random-test.c:6:10: fatal error: unistd.h: No such file or directory
6 | #include <unistd.h>
|          ^~~~~~~~~~
compilation terminated.
make: *** [../lib.mk:139: /kernel_work/linux-github/tools/testing/selftests/vm/map_hugetlb] Error 1
khugepaged.c:2:10: fatal error: fcntl.h: No such file or directory
2 | #include <fcntl.h>
|          ^~~~~~~~~
compilation terminated.
make: *** [../lib.mk:139: /kernel_work/linux-github/tools/testing/selftests/vm/on-fault-limit] Error 1
make: *** [../lib.mk:139: /kernel_work/linux-github/tools/testing/selftests/vm/mlock2-tests] Error 1
make: *** [../lib.mk:139: /kernel_work/linux-github/tools/testing/selftests/vm/transhuge-stress] Error 1
make: *** [../lib.mk:139: /kernel_work/linux-github/tools/testing/selftests/vm/map_fixed_noreplace] 
Error 1
make: *** [../lib.mk:139: /kernel_work/linux-github/tools/testing/selftests/vm/mremap_dontunmap] Error 1
make: *** [../lib.mk:139: /kernel_work/linux-github/tools/testing/selftests/vm/va_128TBswitch] Error 1
make: *** [../lib.mk:139: /kernel_work/linux-github/tools/testing/selftests/vm/map_populate] Error 1
thuge-gen.c:16:10: fatal error: sys/mman.h: No such file or directory
16 | #include <sys/mman.h>
|          ^~~~~~~~~~~~
compilation terminated.
make: *** [../lib.mk:139: /kernel_work/linux-github/tools/testing/selftests/vm/khugepaged] Error 1
make: *** [../lib.mk:139: /kernel_work/linux-github/tools/testing/selftests/vm/mlock-random-test] 
Error 1
userfaultfd.c:38:10: fatal error: stdio.h: No such file or directory
38 | #include <stdio.h>
|          ^~~~~~~~~
compilation terminated.
write_to_hugetlbfs.c:7:10: fatal error: err.h: No such file or directory
7 | #include <err.h>
|          ^~~~~~~
compilation terminated.
virtual_address_range.c:8:10: fatal error: stdio.h: No such file or directory
8 | #include <stdio.h>
|          ^~~~~~~~~
compilation terminated.


thanks,
-- 
John Hubbard
NVIDIA


  reply	other threads:[~2021-07-28  5:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28  4:59 kernel test robot
2021-07-28  5:24 ` John Hubbard [this message]
2021-07-28  6:09   ` [kbuild-all] " Chen, Rong A

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=6af32770-1825-ff9a-ccf2-46600ed6fc7e@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --subject='Re: gup_test.c:1:10: fatal error: fcntl.h: No such file or directory' \
    /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

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).