From: Kees Cook <keescook@chromium.org>
To: "Darrick J . Wong" <djwong@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Keith Packard <keithp@keithp.com>,
Francis Laniel <laniel_francis@privacyrequired.com>,
Daniel Axtens <dja@axtens.net>,
Dan Williams <dan.j.williams@intel.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Guenter Roeck <linux@roeck-us.net>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Tadeusz Struk <tadeusz.struk@linaro.org>,
Zorro Lang <zlang@redhat.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Andy Shevchenko <andriy.shevchenko@intel.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: [PATCH v2 0/2] Introduce flexible array struct helpers
Date: Mon, 24 Oct 2022 10:20:56 -0700 [thread overview]
Message-ID: <20221024171848.never.522-kees@kernel.org> (raw)
Hi,
Here's a trimmed-down version of my original proposal, which just includes
flex_cpy(), as this is needed by XFS.
-Kees
v2: only include flex_cpy(), leaving remaining helpers for the future
v1: https://lore.kernel.org/all/20220504014440.3697851-1-keescook@chromium.org/
Kees Cook (2):
Introduce flexible array struct helpers
xfs: Use flex_cpy() to check extent copying
fs/xfs/xfs_bmap_item.c | 7 +-
include/linux/flex_array.h | 325 ++++++++++++++++++++++++++++++++++++
include/linux/string.h | 1 +
include/uapi/linux/stddef.h | 14 ++
4 files changed, 344 insertions(+), 3 deletions(-)
create mode 100644 include/linux/flex_array.h
--
2.34.1
next reply other threads:[~2022-10-24 18:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 17:20 Kees Cook [this message]
2022-10-24 17:20 ` [PATCH v2 1/2] Introduce flexible array struct helpers Kees Cook
2022-10-24 18:35 ` Keith Packard
2022-10-26 20:33 ` Kees Cook
2022-10-25 6:12 ` kernel test robot
2022-10-25 8:57 ` Andy Shevchenko
2022-10-24 17:20 ` [PATCH 2/2] xfs: Use flex_cpy() to check extent copying Kees Cook
2022-10-25 8:58 ` Andy Shevchenko
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=20221024171848.never.522-kees@kernel.org \
--to=keescook@chromium.org \
--cc=andriy.shevchenko@intel.com \
--cc=dan.j.williams@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dja@axtens.net \
--cc=djwong@kernel.org \
--cc=geert@linux-m68k.org \
--cc=gustavoars@kernel.org \
--cc=keithp@keithp.com \
--cc=laniel_francis@privacyrequired.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=pabeni@redhat.com \
--cc=tadeusz.struk@linaro.org \
--cc=vincenzo.frascino@arm.com \
--cc=zlang@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.