linux-kernel - Re: [PATCH][next] leds: Avoid -Wflex-array-member-not-at-end warning

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <0a1f5cad-3ebb-4063-bb79-117574da521c@embeddedor.com>
Date: Mon, 31 Mar 2025 11:04:02 -0600
From: "Gustavo A. R. Silva" <gustavo@...eddedor.com>
To: Thomas Weißschuh <thomas@...ssschuh.net>
Cc: "Gustavo A. R. Silva" <gustavoars@...nel.org>, Lee Jones
 <lee@...nel.org>, Pavel Machek <pavel@...nel.org>,
 Benson Leung <bleung@...omium.org>, Guenter Roeck <groeck@...omium.org>,
 linux-leds@...r.kernel.org, chrome-platform@...ts.linux.dev,
 linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org
Subject: Re: [PATCH][next] leds: Avoid -Wflex-array-member-not-at-end warning

> My issue was with the general usage of DEFINE_RAW_FLEX(), the reply was
> placed badly. For somebody not knowing this construct it's not clear
> what is happening under the hood.
> It's probably fine in a regular header file with some explanation,
> but in a random driver it looks off.
> 
> The following is what I had in mind. Now actually tested.

OK, let's go with that :)

https://lore.kernel.org/linux-hardening/Z-rKcgFjsyKvd58q@kspp/

Thanks!
--
Gustavo