From: kernel test robot <lkp@intel.com> To: "Stephan Müller" <smueller@chronox.de>, "Tso Ted" <tytso@mit.edu>, linux-crypto@vger.kernel.org Cc: kbuild-all@lists.01.org, Willy Tarreau <w@1wt.eu>, Nicolai Stange <nstange@suse.de>, LKML <linux-kernel@vger.kernel.org>, Arnd Bergmann <arnd@arndb.de>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, "Eric W. Biederman" <ebiederm@xmission.com>, "Alexander E. Patrakov" <patrakov@gmail.com>, "Ahmed S. Darwish" <darwish.07@gmail.com> Subject: Re: [PATCH v42 01/13] Linux Random Number Generator Date: Fri, 17 Sep 2021 23:02:29 +0800 [thread overview] Message-ID: <202109172238.fNcqoasE-lkp@intel.com> (raw) In-Reply-To: <2645866.lzt4QeR4KX@positron.chronox.de> [-- Attachment #1: Type: text/plain, Size: 4521 bytes --] Hi "Stephan, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on herbert-crypto-2.6/master] [cannot apply to char-misc/char-misc-testing herbert-cryptodev-2.6/master v5.15-rc1 next-20210917] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch] url: https://github.com/0day-ci/linux/commits/Stephan-M-ller/dev-random-a-new-approach/20210917-174624 base: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git master config: nds32-allyesconfig (attached as .config) compiler: nds32le-linux-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://github.com/0day-ci/linux/commit/335ce64ab466685e61b363a33a405c9c49c7a099 git remote add linux-review https://github.com/0day-ci/linux git fetch --no-tags linux-review Stephan-M-ller/dev-random-a-new-approach/20210917-174624 git checkout 335ce64ab466685e61b363a33a405c9c49c7a099 # save the attached .config to linux build tree COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=nds32 If you fix the issue, kindly add following tag as appropriate Reported-by: kernel test robot <lkp@intel.com> All warnings (new ones prefixed by >>): >> drivers/char/lrng/lrng_chacha20.c:35: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst * Update of the ChaCha20 state by either using an unused buffer part or by -- >> drivers/char/lrng/lrng_es_aux.c:185: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst * Get auxiliary entropy pool and its entropy content for seed buffer. -- drivers/char/lrng/lrng_es_irq.c:316: warning: Function parameter or member 'node' not described in 'lrng_pcpu_switch_hash' drivers/char/lrng/lrng_es_irq.c:316: warning: Function parameter or member 'new_cb' not described in 'lrng_pcpu_switch_hash' drivers/char/lrng/lrng_es_irq.c:316: warning: Function parameter or member 'new_hash' not described in 'lrng_pcpu_switch_hash' drivers/char/lrng/lrng_es_irq.c:316: warning: Function parameter or member 'old_cb' not described in 'lrng_pcpu_switch_hash' >> drivers/char/lrng/lrng_es_irq.c:316: warning: expecting prototype for Trigger a switch of the hash implementation for the per(). Prototype was for lrng_pcpu_switch_hash() instead >> drivers/char/lrng/lrng_es_irq.c:444: warning: expecting prototype for Hash all per(). Prototype was for lrng_pcpu_pool_hash() instead vim +35 drivers/char/lrng/lrng_chacha20.c 33 34 /** > 35 * Update of the ChaCha20 state by either using an unused buffer part or by 36 * generating one ChaCha20 block which is half of the state of the ChaCha20. 37 * The block is XORed into the key part of the state. This shall ensure 38 * backtracking resistance as well as a proper mix of the ChaCha20 state once 39 * the key is injected. 40 */ 41 static void lrng_chacha20_update(struct chacha20_state *chacha20_state, 42 __le32 *buf, u32 used_words) 43 { 44 struct chacha20_block *chacha20 = &chacha20_state->block; 45 u32 i; 46 __le32 tmp[CHACHA_BLOCK_WORDS]; 47 48 BUILD_BUG_ON(sizeof(struct chacha20_block) != CHACHA_BLOCK_SIZE); 49 BUILD_BUG_ON(CHACHA_BLOCK_SIZE != 2 * CHACHA_KEY_SIZE); 50 51 if (used_words > CHACHA_KEY_SIZE_WORDS) { 52 chacha20_block(&chacha20->constants[0], (u8 *)tmp); 53 for (i = 0; i < CHACHA_KEY_SIZE_WORDS; i++) 54 chacha20->key.u[i] ^= le32_to_cpu(tmp[i]); 55 memzero_explicit(tmp, sizeof(tmp)); 56 } else { 57 for (i = 0; i < CHACHA_KEY_SIZE_WORDS; i++) 58 chacha20->key.u[i] ^= le32_to_cpu(buf[i + used_words]); 59 } 60 61 /* Deterministic increment of nonce as required in RFC 7539 chapter 4 */ 62 chacha20->nonce[0]++; 63 if (chacha20->nonce[0] == 0) { 64 chacha20->nonce[1]++; 65 if (chacha20->nonce[1] == 0) 66 chacha20->nonce[2]++; 67 } 68 69 /* Leave counter untouched as it is start value is undefined in RFC */ 70 } 71 --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org [-- Attachment #2: .config.gz --] [-- Type: application/gzip, Size: 61228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com> To: kbuild-all@lists.01.org Subject: Re: [PATCH v42 01/13] Linux Random Number Generator Date: Fri, 17 Sep 2021 23:02:29 +0800 [thread overview] Message-ID: <202109172238.fNcqoasE-lkp@intel.com> (raw) In-Reply-To: <2645866.lzt4QeR4KX@positron.chronox.de> [-- Attachment #1: Type: text/plain, Size: 4611 bytes --] Hi "Stephan, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on herbert-crypto-2.6/master] [cannot apply to char-misc/char-misc-testing herbert-cryptodev-2.6/master v5.15-rc1 next-20210917] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch] url: https://github.com/0day-ci/linux/commits/Stephan-M-ller/dev-random-a-new-approach/20210917-174624 base: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git master config: nds32-allyesconfig (attached as .config) compiler: nds32le-linux-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://github.com/0day-ci/linux/commit/335ce64ab466685e61b363a33a405c9c49c7a099 git remote add linux-review https://github.com/0day-ci/linux git fetch --no-tags linux-review Stephan-M-ller/dev-random-a-new-approach/20210917-174624 git checkout 335ce64ab466685e61b363a33a405c9c49c7a099 # save the attached .config to linux build tree COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=nds32 If you fix the issue, kindly add following tag as appropriate Reported-by: kernel test robot <lkp@intel.com> All warnings (new ones prefixed by >>): >> drivers/char/lrng/lrng_chacha20.c:35: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst * Update of the ChaCha20 state by either using an unused buffer part or by -- >> drivers/char/lrng/lrng_es_aux.c:185: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst * Get auxiliary entropy pool and its entropy content for seed buffer. -- drivers/char/lrng/lrng_es_irq.c:316: warning: Function parameter or member 'node' not described in 'lrng_pcpu_switch_hash' drivers/char/lrng/lrng_es_irq.c:316: warning: Function parameter or member 'new_cb' not described in 'lrng_pcpu_switch_hash' drivers/char/lrng/lrng_es_irq.c:316: warning: Function parameter or member 'new_hash' not described in 'lrng_pcpu_switch_hash' drivers/char/lrng/lrng_es_irq.c:316: warning: Function parameter or member 'old_cb' not described in 'lrng_pcpu_switch_hash' >> drivers/char/lrng/lrng_es_irq.c:316: warning: expecting prototype for Trigger a switch of the hash implementation for the per(). Prototype was for lrng_pcpu_switch_hash() instead >> drivers/char/lrng/lrng_es_irq.c:444: warning: expecting prototype for Hash all per(). Prototype was for lrng_pcpu_pool_hash() instead vim +35 drivers/char/lrng/lrng_chacha20.c 33 34 /** > 35 * Update of the ChaCha20 state by either using an unused buffer part or by 36 * generating one ChaCha20 block which is half of the state of the ChaCha20. 37 * The block is XORed into the key part of the state. This shall ensure 38 * backtracking resistance as well as a proper mix of the ChaCha20 state once 39 * the key is injected. 40 */ 41 static void lrng_chacha20_update(struct chacha20_state *chacha20_state, 42 __le32 *buf, u32 used_words) 43 { 44 struct chacha20_block *chacha20 = &chacha20_state->block; 45 u32 i; 46 __le32 tmp[CHACHA_BLOCK_WORDS]; 47 48 BUILD_BUG_ON(sizeof(struct chacha20_block) != CHACHA_BLOCK_SIZE); 49 BUILD_BUG_ON(CHACHA_BLOCK_SIZE != 2 * CHACHA_KEY_SIZE); 50 51 if (used_words > CHACHA_KEY_SIZE_WORDS) { 52 chacha20_block(&chacha20->constants[0], (u8 *)tmp); 53 for (i = 0; i < CHACHA_KEY_SIZE_WORDS; i++) 54 chacha20->key.u[i] ^= le32_to_cpu(tmp[i]); 55 memzero_explicit(tmp, sizeof(tmp)); 56 } else { 57 for (i = 0; i < CHACHA_KEY_SIZE_WORDS; i++) 58 chacha20->key.u[i] ^= le32_to_cpu(buf[i + used_words]); 59 } 60 61 /* Deterministic increment of nonce as required in RFC 7539 chapter 4 */ 62 chacha20->nonce[0]++; 63 if (chacha20->nonce[0] == 0) { 64 chacha20->nonce[1]++; 65 if (chacha20->nonce[1] == 0) 66 chacha20->nonce[2]++; 67 } 68 69 /* Leave counter untouched as it is start value is undefined in RFC */ 70 } 71 --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org [-- Attachment #2: config.gz --] [-- Type: application/gzip, Size: 61228 bytes --]
next prev parent reply other threads:[~2021-09-17 15:03 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-16 10:09 [PATCH v42 00/13] /dev/random - a new approach Stephan Müller 2021-09-16 10:11 ` [PATCH v42 01/13] Linux Random Number Generator Stephan Müller 2021-09-17 15:02 ` kernel test robot [this message] 2021-09-17 15:02 ` kernel test robot 2021-09-17 15:14 ` Stephan Mueller 2021-09-17 15:14 ` Stephan Mueller 2021-10-26 21:03 ` Jirka Hladky 2021-10-26 21:03 ` Jirka Hladky 2021-09-16 10:12 ` [PATCH v42 02/13] LRNG - allocate one DRNG instance per NUMA node Stephan Müller 2021-09-16 10:12 ` [PATCH v42 03/13] LRNG - sysctls and /proc interface Stephan Müller 2021-09-16 10:12 ` [PATCH v42 04/13] LRNG - add switchable DRNG support Stephan Müller 2021-09-16 10:13 ` [PATCH v42 05/13] LRNG - add common generic hash support Stephan Müller 2021-09-16 10:13 ` [PATCH v42 06/13] crypto: DRBG - externalize DRBG functions for LRNG Stephan Müller 2021-09-16 10:14 ` [PATCH v42 07/13] LRNG - add SP800-90A DRBG extension Stephan Müller 2021-09-16 10:14 ` [PATCH v42 08/13] LRNG - add kernel crypto API PRNG extension Stephan Müller 2021-09-16 10:15 ` [PATCH v42 09/13] crypto: move Jitter RNG header include dir Stephan Müller 2021-09-16 10:15 ` [PATCH v42 10/13] LRNG - add Jitter RNG fast noise source Stephan Müller 2021-09-16 10:16 ` [PATCH v42 11/13] LRNG - add SP800-90B compliant health tests Stephan Müller 2021-09-16 10:16 ` [PATCH v42 12/13] LRNG - add interface for gathering of raw entropy Stephan Müller 2021-09-16 10:16 ` [PATCH v42 13/13] LRNG - add power-on and runtime self-tests Stephan Müller
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=202109172238.fNcqoasE-lkp@intel.com \ --to=lkp@intel.com \ --cc=arnd@arndb.de \ --cc=darwish.07@gmail.com \ --cc=ebiederm@xmission.com \ --cc=gregkh@linuxfoundation.org \ --cc=kbuild-all@lists.01.org \ --cc=linux-crypto@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=nstange@suse.de \ --cc=patrakov@gmail.com \ --cc=smueller@chronox.de \ --cc=tytso@mit.edu \ --cc=w@1wt.eu \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.