From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [paulmck-rcu:dev.2025.04.09a 32/52] security/integrity/ima/ima_crypto.c:319:17: sparse: sparse: Initializer entry defined twice
Date: Sat, 12 Apr 2025 12:31:13 +0800 [thread overview]
Message-ID: <202504121256.tiCMP2yi-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2025.04.09a
head: 45d581d282cfd358f599a7a53768519772444871
commit: 7388d97bfc3c63bc8bd9aa32ef8cbd78c7fdf135 [32/52] ratelimit: Reduce ratelimit's false-positive misses
config: arc-randconfig-r121-20250412 (https://download.01.org/0day-ci/archive/20250412/202504121256.tiCMP2yi-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 14.2.0
reproduce: (https://download.01.org/0day-ci/archive/20250412/202504121256.tiCMP2yi-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/202504121256.tiCMP2yi-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> security/integrity/ima/ima_crypto.c:319:17: sparse: sparse: Initializer entry defined twice
security/integrity/ima/ima_crypto.c:319:17: sparse: also defined here
>> security/integrity/ima/ima_crypto.c:319:17: sparse: sparse: Initializer entry defined twice
security/integrity/ima/ima_crypto.c:319:17: sparse: also defined here
>> security/integrity/ima/ima_crypto.c:319:17: sparse: sparse: Initializer entry defined twice
security/integrity/ima/ima_crypto.c:319:17: sparse: also defined here
>> security/integrity/ima/ima_crypto.c:319:17: sparse: sparse: Initializer entry defined twice
security/integrity/ima/ima_crypto.c:319:17: sparse: also defined here
>> security/integrity/ima/ima_crypto.c:319:17: sparse: sparse: Initializer entry defined twice
security/integrity/ima/ima_crypto.c:319:17: sparse: also defined here
>> security/integrity/ima/ima_crypto.c:319:17: sparse: sparse: Initializer entry defined twice
security/integrity/ima/ima_crypto.c:319:17: sparse: also defined here
>> security/integrity/ima/ima_crypto.c:319:17: sparse: sparse: Initializer entry defined twice
security/integrity/ima/ima_crypto.c:319:17: sparse: also defined here
>> security/integrity/ima/ima_crypto.c:319:17: sparse: sparse: Initializer entry defined twice
security/integrity/ima/ima_crypto.c:319:17: sparse: also defined here
vim +319 security/integrity/ima/ima_crypto.c
3bcced39ea7d1b0 Dmitry Kasatkin 2014-02-26 315
46f1414c8a92d85 Gilad Ben-Yossef 2017-10-18 316 err = crypto_wait_req(err, wait);
3bcced39ea7d1b0 Dmitry Kasatkin 2014-02-26 317
46f1414c8a92d85 Gilad Ben-Yossef 2017-10-18 318 if (err)
3bcced39ea7d1b0 Dmitry Kasatkin 2014-02-26 @319 pr_crit_ratelimited("ahash calculation failed: err: %d\n", err);
3bcced39ea7d1b0 Dmitry Kasatkin 2014-02-26 320
3bcced39ea7d1b0 Dmitry Kasatkin 2014-02-26 321 return err;
3bcced39ea7d1b0 Dmitry Kasatkin 2014-02-26 322 }
3bcced39ea7d1b0 Dmitry Kasatkin 2014-02-26 323
:::::: The code at line 319 was first introduced by commit
:::::: 3bcced39ea7d1b0da0a991e221f53de480c6b60b ima: use ahash API for file hash calculation
:::::: TO: Dmitry Kasatkin <d.kasatkin@samsung.com>
:::::: CC: Mimi Zohar <zohar@linux.vnet.ibm.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-04-12 4:32 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=202504121256.tiCMP2yi-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paulmck@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 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.