LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org> To: linux-kernel@vger.kernel.org Cc: Kees Cook <keescook@chromium.org>, Andrew Morton <akpm@linux-foundation.org>, Miguel Ojeda <ojeda@kernel.org>, Nathan Chancellor <nathan@kernel.org>, Nick Desaulniers <ndesaulniers@google.com>, Daniel Micay <danielmicay@gmail.com>, Christoph Lameter <cl@linux.com>, Pekka Enberg <penberg@kernel.org>, David Rientjes <rientjes@google.com>, Joonsoo Kim <iamjoonsoo.kim@lge.com>, Vlastimil Babka <vbabka@suse.cz>, Dennis Zhou <dennis@kernel.org>, Tejun Heo <tj@kernel.org>, Masahiro Yamada <masahiroy@kernel.org>, Michal Marek <michal.lkml@markovi.net>, clang-built-linux@googlegroups.com, linux-mm@kvack.org, linux-kbuild@vger.kernel.org, linux-hardening@vger.kernel.org Subject: [PATCH 0/5] Add __alloc_size() for better bounds checking Date: Tue, 17 Aug 2021 22:08:36 -0700 [thread overview] Message-ID: <20210818050841.2226600-1-keescook@chromium.org> (raw) Hi, GCC and Clang both use the "alloc_size" attribute to assist with bounds checking around the use of allocation functions. Add the attribute, adjust the Makefile to silence needless warnings, and add the hints to the allocators where possible. These changes have been in use for a while now in GrapheneOS. To build without warnings, this series needs a couple small fixes for allmodconfig, which I sent separately: https://lore.kernel.org/lkml/20210818044540.1601664-1-keescook@chromium.org/ https://lore.kernel.org/lkml/20210818044252.1533634-1-keescook@chromium.org/ https://lore.kernel.org/lkml/20210818043912.1466447-1-keescook@chromium.org/ I figure I can take this via my "overflow" series, or it could go via -mm? -Kees Kees Cook (5): Compiler Attributes: Add __alloc_size() for better bounds checking slab: Add __alloc_size attributes for better bounds checking mm/page_alloc: Add __alloc_size attributes for better bounds checking percpu: Add __alloc_size attributes for better bounds checking mm/vmalloc: Add __alloc_size attributes for better bounds checking Makefile | 6 +++- include/linux/compiler_attributes.h | 6 ++++ include/linux/gfp.h | 4 +-- include/linux/percpu.h | 6 ++-- include/linux/slab.h | 50 ++++++++++++++++++----------- include/linux/vmalloc.h | 22 ++++++------- 6 files changed, 58 insertions(+), 36 deletions(-) -- 2.30.2
next reply other threads:[~2021-08-18 5:08 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-18 5:08 Kees Cook [this message] 2021-08-18 5:08 ` [PATCH 1/5] Compiler Attributes: Add __alloc_size() for better bounds checking Kees Cook 2021-08-18 13:07 ` Miguel Ojeda 2021-08-18 17:58 ` Kees Cook 2021-08-18 18:04 ` Nathan Chancellor 2021-08-18 21:04 ` Kees Cook 2021-08-18 5:08 ` [PATCH 2/5] slab: Add __alloc_size attributes " Kees Cook 2021-08-18 5:31 ` Joe Perches 2021-08-18 6:16 ` Kees Cook 2021-08-18 6:30 ` Joe Perches 2021-08-19 0:27 ` Matthew Wilcox 2021-08-19 1:10 ` Joe Perches 2021-08-19 2:16 ` Matthew Wilcox 2021-08-19 2:59 ` Joe Perches 2021-08-18 5:08 ` [PATCH 3/5] mm/page_alloc: " Kees Cook 2021-08-18 5:08 ` [PATCH 4/5] percpu: " Kees Cook 2021-08-18 5:08 ` [PATCH 5/5] mm/vmalloc: " Kees Cook 2021-08-19 9:09 ` [PATCH 0/5] Add __alloc_size() " Christoph Hellwig 2021-08-19 14:18 ` Daniel Micay 2021-08-25 10:01 ` Christoph Lameter 2021-08-25 16:34 ` Kees Cook
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=20210818050841.2226600-1-keescook@chromium.org \ --to=keescook@chromium.org \ --cc=akpm@linux-foundation.org \ --cc=cl@linux.com \ --cc=clang-built-linux@googlegroups.com \ --cc=danielmicay@gmail.com \ --cc=dennis@kernel.org \ --cc=iamjoonsoo.kim@lge.com \ --cc=linux-hardening@vger.kernel.org \ --cc=linux-kbuild@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=masahiroy@kernel.org \ --cc=michal.lkml@markovi.net \ --cc=nathan@kernel.org \ --cc=ndesaulniers@google.com \ --cc=ojeda@kernel.org \ --cc=penberg@kernel.org \ --cc=rientjes@google.com \ --cc=tj@kernel.org \ --cc=vbabka@suse.cz \ /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: linkBe 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).