From: Kees Cook <keescook@chromium.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
"David S. Miller" <davem@davemloft.net>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Dan Williams <dan.j.williams@intel.com>,
Keith Packard <keithp@keithp.com>,
Miguel Ojeda <ojeda@kernel.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
Dmitry Antipov <dmantipov@yandex.ru>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Nathan Chancellor <nathan@kernel.org>,
kernel test robot <lkp@intel.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: [PATCH v2 0/2] stddef: Allow attributes to be used when creating flex arrays
Date: Tue, 13 Feb 2024 15:42:09 -0800 [thread overview]
Message-ID: <20240213234023.it.219-kees@kernel.org> (raw)
v2:
- don't add a new helper, just add __VA_ARGS__ (Rasmus)
v1: https://lore.kernel.org/all/20240210011452.work.985-kees@kernel.org/
Hi,
We're going to have more cases where we need to apply attributes
(e.g. __counted_by) to struct members that have been declared with
DECLARE_FLEX_ARRAY. Add an optional 3rd argument to allow for this and
annotate one such user in linux/in.h.
I kept the acks/reviews since it's effectively the same...
-Kees
Kees Cook (2):
stddef: Allow attributes to be used when creating flex arrays
net/ipv4: Annotate imsf_slist_flex with __counted_by(imsf_numsrc)
include/linux/stddef.h | 6 +++---
include/uapi/linux/in.h | 3 ++-
include/uapi/linux/stddef.h | 10 +++++-----
3 files changed, 10 insertions(+), 9 deletions(-)
--
2.34.1
next reply other threads:[~2024-02-13 23:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 23:42 Kees Cook [this message]
2024-02-13 23:42 ` [PATCH v2 1/2] stddef: Allow attributes to be used when creating flex arrays Kees Cook
2024-06-08 16:26 ` Vincent Mailhol
2024-02-13 23:42 ` [PATCH v2 2/2] net/ipv4: Annotate imsf_slist_flex with __counted_by(imsf_numsrc) 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=20240213234023.it.219-kees@kernel.org \
--to=keescook@chromium.org \
--cc=adobriyan@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=davem@davemloft.net \
--cc=dmantipov@yandex.ru \
--cc=edumazet@google.com \
--cc=gustavoars@kernel.org \
--cc=keithp@keithp.com \
--cc=kuba@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=lkp@intel.com \
--cc=nathan@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=pabeni@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.