From: Kees Cook <keescook@chromium.org>
To: linux-kernel@vger.kernel.org
Cc: Kees Cook <keescook@chromium.org>, Arnd Bergmann <arnd@arndb.de>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
clang-built-linux@googlegroups.com,
linux-hardening@vger.kernel.org
Subject: [PATCH 0/5] Enable -Warray-bounds and -Wzero-length-bounds
Date: Wed, 18 Aug 2021 01:11:13 -0700 [thread overview]
Message-ID: <20210818081118.1667663-1-keescook@chromium.org> (raw)
Hi,
In support of the improved buffer overflow detection for memcpy(),
this enables -Warray-bounds and -Wzero-length-bounds globally. Mostly
it involves some struct member tricks with the new flex_array() macro.
Everything else is just replacing stacked 0-element arrays with actual
unions in two related treewide patches. There is one set of special
cases that were fixed separately[1] and are needed as well.
I'm expecting to carry this series with the memcpy() series in my
"overflow" tree.
Thanks!
-Kees
[1] https://lore.kernel.org/lkml/20210818043035.1308062-1-keescook@chromium.org/
Kees Cook (5):
stddef: Add flexible array union helper
treewide: Replace open-coded flex arrays in unions
treewide: Replace 0-element memcpy() destinations with flexible arrays
Makefile: Enable -Warray-bounds
Makefile: Enable -Wzero-length-bounds
Makefile | 2 --
drivers/crypto/chelsio/chcr_crypto.h | 14 +++++---
drivers/net/can/usb/etas_es58x/es581_4.h | 2 +-
drivers/net/can/usb/etas_es58x/es58x_fd.h | 2 +-
drivers/net/wireless/ath/ath10k/bmi.h | 12 +++----
drivers/net/wireless/ath/ath10k/htt.h | 7 ++--
.../net/wireless/intel/iwlegacy/commands.h | 6 ++--
.../net/wireless/intel/iwlwifi/dvm/commands.h | 6 ++--
.../net/wireless/intel/iwlwifi/fw/api/tx.h | 6 ++--
drivers/scsi/aic94xx/aic94xx_sds.c | 6 ++--
drivers/scsi/qla4xxx/ql4_def.h | 4 +--
drivers/staging/r8188eu/include/ieee80211.h | 6 ++--
drivers/staging/rtl8712/ieee80211.h | 4 +--
drivers/staging/rtl8723bs/include/ieee80211.h | 6 ++--
fs/hpfs/hpfs.h | 8 ++---
include/linux/filter.h | 6 ++--
include/linux/ieee80211.h | 34 +++++++++----------
include/linux/stddef.h | 10 ++++++
include/scsi/sas.h | 12 ++++---
include/uapi/linux/dlm_device.h | 4 +--
include/uapi/linux/stddef.h | 13 +++++++
include/uapi/rdma/rdma_user_rxe.h | 6 ++--
include/uapi/sound/asoc.h | 6 ++--
23 files changed, 112 insertions(+), 70 deletions(-)
--
2.30.2
next reply other threads:[~2021-08-18 8:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 8:11 Kees Cook [this message]
2021-08-18 8:11 ` [PATCH 1/5] stddef: Add flexible array union helper Kees Cook
2021-08-18 8:11 ` [PATCH 2/5] treewide: Replace open-coded flex arrays in unions Kees Cook
2021-08-18 9:56 ` Marc Kleine-Budde
2021-08-18 21:51 ` Kees Cook
2021-08-18 8:11 ` [PATCH 3/5] treewide: Replace 0-element memcpy() destinations with flexible arrays Kees Cook
2021-08-18 8:11 ` [PATCH 4/5] Makefile: Enable -Warray-bounds Kees Cook
2022-02-02 16:09 ` Guenter Roeck
2022-02-02 20:56 ` Kees Cook
2022-02-02 23:33 ` Guenter Roeck
2022-02-03 3:03 ` Kees Cook
2022-02-02 22:02 ` Kees Cook
2022-02-02 22:11 ` Kees Cook
2022-02-02 23:21 ` Guenter Roeck
2022-02-03 3:02 ` Kees Cook
2021-08-18 8:11 ` [PATCH 5/5] Makefile: Enable -Wzero-length-bounds Kees Cook
2021-08-25 21:17 ` Nick Desaulniers
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=20210818081118.1667663-1-keescook@chromium.org \
--to=keescook@chromium.org \
--cc=arnd@arndb.de \
--cc=clang-built-linux@googlegroups.com \
--cc=gustavoars@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@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 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).