[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <DE85FD8C-CA6B-4231-9B5E-7B6BEAFA3594@linux.dev>
Date: Wed, 18 Jun 2025 16:57:38 +0200
From: Thorsten Blum <thorsten.blum@...ux.dev>
To: Peter Rosin <peda@...ntia.se>,
Kees Cook <kees@...nel.org>,
"Gustavo A. R. Silva" <gustavoars@...nel.org>,
Thorsten Blum <thorsten.blum@...ux.dev>,
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
krzysztof.kozlowski@...aro.org
Cc: linux-kernel@...r.kernel.org,
linux-hardening@...r.kernel.org
Subject: Re: [PATCH RESEND] mux: Convert mux_control_ops to a flex array
member in mux_chip
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@...ux.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
Powered by blists - more mailing lists