From: Thorsten Blum <thorsten.blum@linux.dev>
To: Peter Rosin <peda@axentia.se>, Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Thorsten Blum <thorsten.blum@linux.dev>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
krzysztof.kozlowski@linaro.org
Cc: 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 16:57:38 +0200 [thread overview]
Message-ID: <DE85FD8C-CA6B-4231-9B5E-7B6BEAFA3594@linux.dev> (raw)
In-Reply-To: <20250610104106.1948-2-thorsten.blum@linux.dev>
On 10. Jun 2025, at 12:40, 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:
>
> WARNING: Use struct_size
>
> Use size_add() to safely add any extra bytes.
>
> No functional changes intended.
>
> Link: https://github.com/KSPP/linux/issues/83
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
> ---
Hi all, since Peter isn't reachable, could someone else take care of
this one? Is there anything else I can do to get this merged?
I also noticed that Krzysztof recently changed the status of the mux
subsystem from "Maintained" to "Odd Fixes" in ff91020412085.
Thanks,
Thorsten
next prev parent reply other threads:[~2025-06-18 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 10:40 [PATCH RESEND] mux: Convert mux_control_ops to a flex array member in mux_chip Thorsten Blum
2025-06-18 14:57 ` Thorsten Blum [this message]
2025-06-18 21:21 ` 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=DE85FD8C-CA6B-4231-9B5E-7B6BEAFA3594@linux.dev \
--to=thorsten.blum@linux.dev \
--cc=bartosz.golaszewski@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
/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