From: kernel test robot <lkp@intel.com>
To: "Jason A. Donenfeld" <zx2c4@kernel.org>
Cc: kbuild-all@lists.01.org, zx2c4@kernel.org, linux-kernel@vger.kernel.org
Subject: [crng-random:jd/not-zero-entropy 7/12] arch/arm/include/asm/timex.h:14:63: error: implicit declaration of function 'sched_clock'
Date: Mon, 11 Apr 2022 01:06:20 +0800 [thread overview]
Message-ID: <202204110106.XXNJ3BEs-lkp@intel.com> (raw)
tree: git://git.kernel.org/pub/scm/linux/kernel/git/crng/random.git jd/not-zero-entropy
head: efec3e2057963ad20223fa50a657b3ca9314ed45
commit: 904df0ccc3b52e7dffc4b968b8839d63ecba08ce [7/12] arm: use sched_clock() for random_get_entropy() instead of zero
config: arm-buildonly-randconfig-r001-20220410 (https://download.01.org/0day-ci/archive/20220411/202204110106.XXNJ3BEs-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 11.2.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
# https://git.kernel.org/pub/scm/linux/kernel/git/crng/random.git/commit/?id=904df0ccc3b52e7dffc4b968b8839d63ecba08ce
git remote add crng-random git://git.kernel.org/pub/scm/linux/kernel/git/crng/random.git
git fetch --no-tags crng-random jd/not-zero-entropy
git checkout 904df0ccc3b52e7dffc4b968b8839d63ecba08ce
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arm SHELL=/bin/bash
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 include/linux/timex.h:65,
from include/linux/time32.h:13,
from include/linux/time.h:60,
from include/linux/jiffies.h:10,
from lib/random32.c:38:
lib/random32.c: In function 'prandom_init_early':
>> arch/arm/include/asm/timex.h:14:63: error: implicit declaration of function 'sched_clock' [-Werror=implicit-function-declaration]
14 | #define random_get_entropy() ((unsigned long)(get_cycles() ?: sched_clock()))
| ^~~~~~~~~~~
lib/random32.c:469:22: note: in expansion of macro 'random_get_entropy'
469 | v1 = random_get_entropy();
| ^~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
--
In file included from include/linux/timex.h:65,
from include/linux/time32.h:13,
from include/linux/time.h:60,
from include/linux/stat.h:19,
from include/linux/module.h:13,
from crypto/jitterentropy-kcapi.c:41:
crypto/jitterentropy-kcapi.c: In function 'jent_get_nstime':
>> arch/arm/include/asm/timex.h:14:63: error: implicit declaration of function 'sched_clock' [-Werror=implicit-function-declaration]
14 | #define random_get_entropy() ((unsigned long)(get_cycles() ?: sched_clock()))
| ^~~~~~~~~~~
crypto/jitterentropy-kcapi.c:85:15: note: in expansion of macro 'random_get_entropy'
85 | tmp = random_get_entropy();
| ^~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/sched_clock +14 arch/arm/include/asm/timex.h
11
12 typedef unsigned long cycles_t;
13 #define get_cycles() ({ cycles_t c; read_current_timer(&c) ? 0 : c; })
> 14 #define random_get_entropy() ((unsigned long)(get_cycles() ?: sched_clock()))
15
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-04-10 17:07 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=202204110106.XXNJ3BEs-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zx2c4@kernel.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