All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: gary.hook@amd.com
Cc: linux-crypto@vger.kernel.org
Subject: [bug report] crypto: ccp - Let a v5 CCP provide the same function as v3
Date: Wed, 12 Oct 2016 11:19:43 +0300	[thread overview]
Message-ID: <20161012081942.GA4766@mwanda> (raw)

Hello Gary R Hook,

The patch 4b394a232df7: "crypto: ccp - Let a v5 CCP provide the same
function as v3" from Jul 26, 2016, leads to the following static
checker warning:

	drivers/crypto/ccp/ccp-dev-v5.c:30 ccp_lsb_alloc()
	warn: always true condition '(cmd_q->lsb >= 0) => (0-u32max >= 0)'

drivers/crypto/ccp/ccp-dev-v5.c
    24  static u32 ccp_lsb_alloc(struct ccp_cmd_queue *cmd_q, unsigned int count)
    25  {
    26          struct ccp_device *ccp;
    27          int start;
    28  
    29          /* First look at the map for the queue */
    30          if (cmd_q->lsb >= 0) {
                    ^^^^^^^^^^^^^^^

->lsb is a u32 so this is always true.

    31                  start = (u32)bitmap_find_next_zero_area(cmd_q->lsbmap,
    32                                                          LSB_SIZE,
    33                                                          0, count, 0);
    34                  if (start < LSB_SIZE) {
    35                          bitmap_set(cmd_q->lsbmap, start, count);
    36                          return start + cmd_q->lsb * LSB_SIZE;
    37                  }
    38          }
    39  
    40          /* No joy; try to get an entry from the shared blocks */
    41          ccp = cmd_q->ccp;
    42          for (;;) {
    43                  mutex_lock(&ccp->sb_mutex);
    44  
    45                  start = (u32)bitmap_find_next_zero_area(ccp->lsbmap,
    46                                                          MAX_LSB_CNT * LSB_SIZE,
    47                                                          0,
    48                                                          count, 0);
    49                  if (start <= MAX_LSB_CNT * LSB_SIZE) {
    50                          bitmap_set(ccp->lsbmap, start, count);
    51  
    52                          mutex_unlock(&ccp->sb_mutex);
    53                          return start * LSB_ITEM_SIZE;
    54                  }
    55  
    56                  ccp->sb_avail = 0;
    57  
    58                  mutex_unlock(&ccp->sb_mutex);
    59  
    60                  /* Wait for KSB entries to become available */
    61                  if (wait_event_interruptible(ccp->sb_queue, ccp->sb_avail))
    62                          return 0;
    63          }
    64  }


regards,
dan carpenter

                 reply	other threads:[~2016-10-12  8:20 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=20161012081942.GA4766@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=gary.hook@amd.com \
    --cc=linux-crypto@vger.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.