public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>
To: Sagi Grimberg <sagi@grimberg.me>, Hannes Reinecke <hare@suse.de>,
	Christoph Hellwig <hch@lst.de>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: build failure of next-20220715 due to "comparison will always evaluate as 'true'"
Date: Sat, 16 Jul 2022 00:13:02 +0100	[thread overview]
Message-ID: <YtH0fux43jxgnCCC@debian> (raw)

Hi All,

Not sure if it has been reported, gcc-12 builds of csky, s390 and x86_64
have failed to build next-20220715 with the error:

drivers/nvme/common/auth.c: In function 'nvme_auth_dhgroup_name':
drivers/nvme/common/auth.c:59:13: error: the comparison will always evaluate as 'true' for the address of 'name' will never be NULL [-Werror=address]
   59 |             !dhgroup_map[dhgroup_id].name ||
      |             ^
drivers/nvme/common/auth.c:39:20: note: 'name' declared here
   39 |         const char name[16];
      |                    ^~~~
drivers/nvme/common/auth.c: In function 'nvme_auth_dhgroup_kpp':
drivers/nvme/common/auth.c:69:13: error: the comparison will always evaluate as 'true' for the address of 'kpp' will never be NULL [-Werror=address]
   69 |             !dhgroup_map[dhgroup_id].kpp ||
      |             ^
drivers/nvme/common/auth.c:40:20: note: 'kpp' declared here
   40 |         const char kpp[16];
      |                    ^~~
drivers/nvme/common/auth.c: In function 'nvme_auth_dhgroup_id':
drivers/nvme/common/auth.c:81:21: error: the comparison will always evaluate as 'true' for the address of 'name' will never be NULL [-Werror=address]
   81 |                 if (!dhgroup_map[i].name ||
      |                     ^
drivers/nvme/common/auth.c:39:20: note: 'name' declared here
   39 |         const char name[16];
      |                    ^~~~
drivers/nvme/common/auth.c: In function 'nvme_auth_hmac_name':
drivers/nvme/common/auth.c:117:13: error: the comparison will always evaluate as 'true' for the address of 'hmac' will never be NULL [-Werror=address]
  117 |             !hash_map[hmac_id].hmac ||
      |             ^
drivers/nvme/common/auth.c:94:20: note: 'hmac' declared here
   94 |         const char hmac[15];
      |                    ^~~~
drivers/nvme/common/auth.c: In function 'nvme_auth_digest_name':
drivers/nvme/common/auth.c:127:13: error: the comparison will always evaluate as 'true' for the address of 'digest' will never be NULL [-Werror=address]
  127 |             !hash_map[hmac_id].digest ||
      |             ^
drivers/nvme/common/auth.c:95:20: note: 'digest' declared here
   95 |         const char digest[8];
      |                    ^~~~~~
drivers/nvme/common/auth.c: In function 'nvme_auth_hmac_id':
drivers/nvme/common/auth.c:139:21: error: the comparison will always evaluate as 'true' for the address of 'hmac' will never be NULL [-Werror=address]
  139 |                 if (!hash_map[i].hmac || !strlen(hash_map[i].hmac))
      |                     ^
drivers/nvme/common/auth.c:94:20: note: 'hmac' declared here
   94 |         const char hmac[15];
      |                    ^~~~
drivers/nvme/common/auth.c: In function 'nvme_auth_hmac_hash_len':
drivers/nvme/common/auth.c:152:13: error: the comparison will always evaluate as 'true' for the address of 'hmac' will never be NULL [-Werror=address]
  152 |             !hash_map[hmac_id].hmac ||
      |             ^
drivers/nvme/common/auth.c:94:20: note: 'hmac' declared here
   94 |         const char hmac[15];
      |                    ^~~~


--
Regards
Sudip

                 reply	other threads:[~2022-07-15 23:13 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=YtH0fux43jxgnCCC@debian \
    --to=sudipm.mukherjee@gmail.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sagi@grimberg.me \
    /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