From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
"Horia Geantă" <horia.geanta@nxp.com>,
"Pankaj Gupta" <pankaj.gupta@nxp.com>,
"Gaurav Jain" <gaurav.jain@nxp.com>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org
Subject: mainline build failure on arm hosts
Date: Mon, 30 Jan 2023 12:17:02 +0000 [thread overview]
Message-ID: <Y9e1PoEJgq3TPNtP@debian> (raw)
Hi All,
The mainline kernel branch had been failing native build on arm hosts
for some weeks with the error:
drivers/crypto/caam/desc_constr.h: In function 'append_data.constprop':
./include/linux/fortify-string.h:57:29: error: argument 2 null where non-null expected [-Werror=nonnull]
57 | #define __underlying_memcpy __builtin_memcpy
| ^
./include/linux/fortify-string.h:578:2: note: in expansion of macro '__underlying_memcpy'
578 | __underlying_##op(p, q, __fortify_size); \
| ^~~~~~~~~~~~~
./include/linux/fortify-string.h:623:26: note: in expansion of macro '__fortify_memcpy_chk'
623 | #define memcpy(p, q, s) __fortify_memcpy_chk(p, q, s, \
| ^~~~~~~~~~~~~~~~~~~~
drivers/crypto/caam/desc_constr.h:167:3: note: in expansion of macro 'memcpy'
167 | memcpy(offset, data, len);
| ^~~~~~
./include/linux/fortify-string.h:57:29: note: in a call to built-in function '__builtin_memcpy'
57 | #define __underlying_memcpy __builtin_memcpy
| ^
./include/linux/fortify-string.h:578:2: note: in expansion of macro '__underlying_memcpy'
578 | __underlying_##op(p, q, __fortify_size); \
| ^~~~~~~~~~~~~
./include/linux/fortify-string.h:623:26: note: in expansion of macro '__fortify_memcpy_chk'
623 | #define memcpy(p, q, s) __fortify_memcpy_chk(p, q, s, \
| ^~~~~~~~~~~~~~~~~~~~
drivers/crypto/caam/desc_constr.h:167:3: note: in expansion of macro 'memcpy'
167 | memcpy(offset, data, len);
| ^~~~~~
cc1: all warnings being treated as errors
The commit 4f289826fee0 ("crypto: caam - Avoid GCC memset bug warning")
in linux-next fixes the build.
--
Regards
Sudip
next reply other threads:[~2023-01-30 12:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 12:17 Sudip Mukherjee [this message]
2023-02-18 10:51 ` mainline build failure on arm hosts Sudip Mukherjee
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=Y9e1PoEJgq3TPNtP@debian \
--to=sudipm.mukherjee@gmail.com \
--cc=davem@davemloft.net \
--cc=gaurav.jain@nxp.com \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.gupta@nxp.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).