All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [dhowells-fs:keys-pqc 2/8] crypto/ml_dsa/dilithium_polyvec_c.h:41:33: sparse: sparse: incorrect type in argument 3 (different base types)
Date: Tue, 11 Nov 2025 01:15:13 +0800	[thread overview]
Message-ID: <202511110107.cresrLdf-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git keys-pqc
head:   445b842b50b449ceb18cbbfc72dc28bc25fa8b08
commit: 7ae730f92709e7f54f560e4ca88b10ef1aeb6c22 [2/8] crypto: Add ML-DSA/Dilithium verify support
config: mips-randconfig-r134-20251110 (https://download.01.org/0day-ci/archive/20251111/202511110107.cresrLdf-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 93d445cba39f4dd3dcda4fa1433eca825cf8fc09)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251111/202511110107.cresrLdf-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202511110107.cresrLdf-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
   crypto/ml_dsa/dilithium_44.c: note: in included file (through crypto/ml_dsa/dilithium_signature_c.c):
>> crypto/ml_dsa/dilithium_polyvec_c.h:41:33: sparse: sparse: incorrect type in argument 3 (different base types) @@     expected unsigned short [addressable] [usertype] nonce @@     got restricted __le16 [usertype] @@
   crypto/ml_dsa/dilithium_polyvec_c.h:41:33: sparse:     expected unsigned short [addressable] [usertype] nonce
   crypto/ml_dsa/dilithium_polyvec_c.h:41:33: sparse:     got restricted __le16 [usertype]
>> crypto/ml_dsa/dilithium_polyvec_c.h:41:33: sparse: sparse: incorrect type in argument 3 (different base types) @@     expected unsigned short [addressable] [usertype] nonce @@     got restricted __le16 [usertype] @@
   crypto/ml_dsa/dilithium_polyvec_c.h:41:33: sparse:     expected unsigned short [addressable] [usertype] nonce
   crypto/ml_dsa/dilithium_polyvec_c.h:41:33: sparse:     got restricted __le16 [usertype]

vim +41 crypto/ml_dsa/dilithium_polyvec_c.h

    21	
    22	/*
    23	 * @brief expand_mat - Implementation of ExpandA. Generates matrix A with
    24	 *		       uniformly random coefficients a_{i,j} by performing
    25	 *		       rejection sampling on the output stream of
    26	 *		       SHAKE128(rho|j|i).
    27	 *
    28	 * @param [out] mat output matrix
    29	 * @param [in] rho byte array containing seed rho
    30	 */
    31	static inline void
    32	polyvec_matrix_expand(polyvecl mat[DILITHIUM_K],
    33			      const uint8_t rho[DILITHIUM_SEEDBYTES], void *ws_buf)
    34	{
    35		unsigned int i, j;
    36	
    37		for (i = 0; i < DILITHIUM_K; ++i)
    38			for (j = 0; j < DILITHIUM_L; ++j)
    39				poly_uniform(
    40					&mat[i].vec[j], rho,
  > 41					cpu_to_le16((uint16_t)(i << 8) + (uint16_t)j),
    42					ws_buf);
    43	}
    44	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2025-11-10 17:16 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=202511110107.cresrLdf-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dhowells@redhat.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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 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.