From: Kees Cook <kees@kernel.org>
To: Peter Rosin <peda@axentia.se>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thorsten Blum <thorsten.blum@linux.dev>
Cc: Kees Cook <kees@kernel.org>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH RESEND] mux: Convert mux_control_ops to a flex array member in mux_chip
Date: Wed, 18 Jun 2025 14:21:20 -0700 [thread overview]
Message-ID: <175028167750.3187549.3330233881854530836.b4-ty@kernel.org> (raw)
In-Reply-To: <20250610104106.1948-2-thorsten.blum@linux.dev>
On Tue, 10 Jun 2025 12:40:59 +0200, Thorsten Blum wrote:
> Convert mux_control_ops to a flexible array member at the end of the
> mux_chip struct and add the __counted_by() compiler attribute to
> improve access bounds-checking via CONFIG_UBSAN_BOUNDS and
> CONFIG_FORTIFY_SOURCE.
>
> Use struct_size() to calculate the number of bytes to allocate for a new
> mux chip and to remove the following Coccinelle/coccicheck warning:
>
> [...]
Applied to for-next/hardening, thanks!
[1/1] mux: Convert mux_control_ops to a flex array member in mux_chip
https://git.kernel.org/kees/c/4bfbc2691de8
Take care,
--
Kees Cook
prev parent reply other threads:[~2025-06-18 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 10:40 Thorsten Blum
2025-06-18 14:57 ` Thorsten Blum
2025-06-18 21:21 ` Kees Cook [this message]
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=175028167750.3187549.3330233881854530836.b4-ty@kernel.org \
--to=kees@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=thorsten.blum@linux.dev \
/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
all inboxes | Powered by JetHome®