aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKees Cook <keescook@chromium.org>2021-08-17 11:56:36 -0700
committerKees Cook <keescook@chromium.org>2021-08-18 01:13:23 -0700
commitb07d5e8190ca172b1ffddd1412b921296000b379 (patch)
tree549c281ee4dec39b1d4904b599556b226752b7f6
parentecc23a9ee765008e439113eea38fb1cbbd3d7c83 (diff)
downloadlinux-b07d5e8190ca172b1ffddd1412b921296000b379.tar.gz
Makefile: Enable -Wzero-length-boundskspp/array-bounds/next-20210816/v1
With all known internal zero-length accesses fixed, it is possible to enable -Wzero-length-bounds globally. Since this is included by default in -Warray-bounds, we just need to stop disabling it. Cc: "Gustavo A. R. Silva" <gustavoars@kernel.org> Cc: Arnd Bergmann <arnd@arndb.de> Cc: Masahiro Yamada <masahiroy@kernel.org> Cc: linux-kbuild@vger.kernel.org Signed-off-by: Kees Cook <keescook@chromium.org>
-rw-r--r--Makefile1
1 files changed, 0 insertions, 1 deletions
diff --git a/Makefile b/Makefile
index 58e3314b8c202..ca3383167fb0f 100644
--- a/Makefile
+++ b/Makefile
@@ -1071,7 +1071,6 @@ KBUILD_CFLAGS += -Wno-pointer-sign
KBUILD_CFLAGS += $(call cc-disable-warning, stringop-truncation)
# We'll want to enable this eventually, but it's not going away for 5.7 at least
-KBUILD_CFLAGS += $(call cc-disable-warning, zero-length-bounds)
KBUILD_CFLAGS += $(call cc-disable-warning, stringop-overflow)
# Another good warning that we'll want to enable eventually