From: kernel test robot <lkp@intel.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [l1k:spdm-future 16/34] include/crypto/internal/ecc.h:74:34: sparse: sparse: cast to restricted __be64
Date: Fri, 8 Mar 2024 05:47:30 +0800 [thread overview]
Message-ID: <202403080559.b0unHTFI-lkp@intel.com> (raw)
tree: https://github.com/l1k/linux spdm-future
head: fde830bd8ee973e5acff536fac518cf4bdb59714
commit: 27df155f5889562ed6dad1352b9c84b4006907e1 [16/34] crypto: ecdsa - Convert byte arrays with key coordinates to digits
config: x86_64-randconfig-121-20240305 (https://download.01.org/0day-ci/archive/20240308/202403080559.b0unHTFI-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240308/202403080559.b0unHTFI-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/202403080559.b0unHTFI-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
crypto/ecdsa.c: note: in included file:
>> include/crypto/internal/ecc.h:74:34: sparse: sparse: cast to restricted __be64
>> include/crypto/internal/ecc.h:74:34: sparse: sparse: cast to restricted __be64
vim +74 include/crypto/internal/ecc.h
58
59 /**
60 * ecc_digits_from_bytes() - Create ndigits-sized digits array from byte array
61 * @in: Input byte array
62 * @nbytes Size of input byte array
63 * @out Output digits array
64 * @ndigits: Number of digits to create from byte array
65 */
66 static inline void ecc_digits_from_bytes(const u8 *in, unsigned int nbytes,
67 u64 *out, unsigned int ndigits)
68 {
69 unsigned int o = nbytes & 7;
70 u64 msd = 0;
71
72 if (o) {
73 memcpy((u8 *)&msd + sizeof(msd) - o, in, o);
> 74 out[--ndigits] = be64_to_cpu(msd);
75 in += o;
76 }
77 ecc_swap_digits(in, out, ndigits);
78 }
79
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-03-07 21:48 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=202403080559.b0unHTFI-lkp@intel.com \
--to=lkp@intel.com \
--cc=lukas@wunner.de \
--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.