mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Pascal van Leeuwen <pascalvanl@gmail.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	Herbert Xu <herbert@gondor.apana.org.au>
Subject: drivers/crypto/inside-secure/safexcel_cipher.c:2001:1-3: WARNING: PTR_ERR_OR_ZERO can be used
Date: Thu, 10 Oct 2019 22:29:38 +0800	[thread overview]
Message-ID: <201910102236.4K1XBa2F%lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   8a8c600de5dc1d9a7f4b83269fddc80ebd3dd045
commit: 3e450886ec573cb9d7cb1758317b5e4e0f308b52 crypto: inside-secure - Added support for basic AES-GCM
date:   5 weeks ago

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>


coccinelle warnings: (new ones prefixed by >>)

>> drivers/crypto/inside-secure/safexcel_cipher.c:2001:1-3: WARNING: PTR_ERR_OR_ZERO can be used

vim +2001 drivers/crypto/inside-secure/safexcel_cipher.c

  1989	
  1990	static int safexcel_aead_gcm_cra_init(struct crypto_tfm *tfm)
  1991	{
  1992		struct safexcel_cipher_ctx *ctx = crypto_tfm_ctx(tfm);
  1993	
  1994		safexcel_aead_cra_init(tfm);
  1995		ctx->hash_alg = CONTEXT_CONTROL_CRYPTO_ALG_GHASH;
  1996		ctx->state_sz = GHASH_BLOCK_SIZE;
  1997		ctx->xcm = 1; /* GCM */
  1998		ctx->mode = CONTEXT_CONTROL_CRYPTO_MODE_XCM; /* override default */
  1999	
  2000		ctx->hkaes = crypto_alloc_cipher("aes", 0, 0);
> 2001		if (IS_ERR(ctx->hkaes))
  2002			return PTR_ERR(ctx->hkaes);
  2003	
  2004		return 0;
  2005	}
  2006	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

                 reply	other threads:[~2019-10-10 14:30 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=201910102236.4K1XBa2F%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pascalvanl@gmail.com \
    /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

all inboxes | Powered by JetHome®