Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: lionel.debieve@st.com
Cc: linux-crypto@vger.kernel.org
Subject: [bug report] crypto: stm32 - Support for STM32 HASH module
Date: Thu, 10 Aug 2017 00:27:18 +0300	[thread overview]
Message-ID: <20170809212718.7xcib3rhexiy52cb@mwanda> (raw)

Hello lionel.debieve@st.com,

The patch 8a1012d3f2ab: "crypto: stm32 - Support for STM32 HASH
module" from Jul 13, 2017, leads to the following static checker
warning:

	drivers/crypto/stm32/stm32-hash.c:1088 stm32_hash_irq_thread()
	error: uninitialized symbol 'err'.

drivers/crypto/stm32/stm32-hash.c
  1067  static irqreturn_t stm32_hash_irq_thread(int irq, void *dev_id)
  1068  {
  1069          struct stm32_hash_dev *hdev = dev_id;
  1070          int err;
                ^^^^^^^^
  1071  
  1072          if (HASH_FLAGS_CPU & hdev->flags) {
  1073                  if (HASH_FLAGS_OUTPUT_READY & hdev->flags) {
  1074                          hdev->flags &= ~HASH_FLAGS_OUTPUT_READY;
  1075                          goto finish;
  1076                  }
  1077          } else if (HASH_FLAGS_DMA_READY & hdev->flags) {
  1078                  if (HASH_FLAGS_DMA_ACTIVE & hdev->flags) {
  1079                          hdev->flags &= ~HASH_FLAGS_DMA_ACTIVE;
  1080                                  goto finish;
  1081                  }
  1082          }
  1083  
  1084          return IRQ_HANDLED;
  1085  
  1086  finish:
  1087          /*Finish current request */
  1088          stm32_hash_finish_req(hdev->req, err);
                                                 ^^^
Never initialized.

  1089  
  1090          return IRQ_HANDLED;
  1091  }


regards,
dan carpenter

                 reply	other threads:[~2017-08-09 21:27 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=20170809212718.7xcib3rhexiy52cb@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=lionel.debieve@st.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