[android-common:android-5.4 16/36] include/vdso/clocksource.h:9:10: fatal error: 'asm/vdso/clocksource.h' file not found

[kbuild test robot]

tree: https://android.googlesource.com/kernel/common android-5.4
head: 7f84f8f1841844015ce11c0606d4e57b75533604
commit: 2b3f7bf08d3db5471d541868f201e2209cb26079 [16/36] BACKPORT: linux/clocksource.h: Extract common header for vDSO
config: mips-randconfig-a001-20200428 (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project f30416fdde922eaa655934e050026930fefbd260)
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install mips cross compiling tool for clang build
# apt-get install binutils-mips-linux-gnu
git checkout 2b3f7bf08d3db5471d541868f201e2209cb26079
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=mips

If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <l...@intel.com>

All errors (new ones prefixed by >>):

In file included from fs/proc/stat.c:15:
In file included from include/linux/tick.h:8:
In file included from include/linux/clockchips.h:14:
In file included from include/linux/clocksource.h:30:
>> include/vdso/clocksource.h:9:10: fatal error: 'asm/vdso/clocksource.h' file not found
#include <asm/vdso/clocksource.h>
^~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.

vim +9 include/vdso/clocksource.h

6
7 #if defined(CONFIG_ARCH_CLOCKSOURCE_DATA) || \
8 defined(CONFIG_GENERIC_GETTIMEOFDAY)
> 9 #include <asm/vdso/clocksource.h>
10 #endif /* CONFIG_ARCH_CLOCKSOURCE_DATA || CONFIG_GENERIC_GETTIMEOFDAY */
11

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuil...@lists.01.org

[Nick Desaulniers]

What's cros-kernel-buildreports? Is Android's kernel team on that
mailing list? (This looks like a MIPS build of an Android tree,
emailed to a list that mentions CrOS).

> --
> You received this message because you are subscribed to the Google Groups "Clang Built Linux" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to clang-built-li...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/clang-built-linux/202004281818.1ptgznrP%25lkp%40intel.com.



--
Thanks,
~Nick Desaulniers

[Todd Kjos]

Nick- I'm on that list and watch for 0-day reports for relevant to
arm, arm64, x86, x86_64 builds of android kernels. I ignore all other
kernels and architectures.

On Tue, Apr 28, 2020 at 9:31 AM 'Nick Desaulniers' via
cros-kernel-buildreports <cros-kernel-...@googlegroups.com>
wrote:

> You received this message because you are subscribed to the Google Groups "cros-kernel-buildreports" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to cros-kernel-buildr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/cros-kernel-buildreports/CAKwvOd%3D-XNzdoe_GhC6guj63Y_nfKG1FFUZ%3DizNGCk%3DqX6iTVQ%40mail.gmail.com.

[Nick Desaulniers]

so MIPS randconfig is not interesting? ;) haha
Anyways the patch in question is the compat vdso stuff. Mark might
want to keep a look out for this report on other
architectures/configs. Randconfig may have found a config that's
actually broken.

Though it may be the case that patch 16/32 does have a bug that's
fixed later in the series, and bisection converged/stopped early on
that patch. If that's the case, something else may actually be broken
for that config in that tree.

--
Thanks,
~Nick Desaulniers

[Vincenzo Frascino]

Hi Nick,

On 4/28/20 5:46 PM, Nick Desaulniers wrote:
> so MIPS randconfig is not interesting? ;) haha
> Anyways the patch in question is the compat vdso stuff. Mark might
> want to keep a look out for this report on other
> architectures/configs. Randconfig may have found a config that's
> actually broken.
>
> Though it may be the case that patch 16/32 does have a bug that's
> fixed later in the series, and bisection converged/stopped early on
> that patch. If that's the case, something else may actually be broken
> for that config in that tree.
>

The issue you are reporting was fixed by [1] and the patch is part of 5.7-rc<x>.
Could you please verify that it is present in that tree?
If so, your suspect is correct, the issue was fixed by a later patch hence the
problem is somewhere else.

[1] https://www.spinics.net/lists/linux-tip-commits/msg52752.html

--
Regards,
Vincenzo