linux-hardening - Re: [RFC] wireless: ti: Can we just remove this flexible array?

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]

Date: Wed, 20 Mar 2024 10:10:37 -0700
From: Jeff Johnson <quic_jjohnson@...cinc.com>
To: Johannes Berg <johannes@...solutions.net>,
        "Gustavo A. R. Silva"
	<gustavo@...eddedor.com>,
        Kalle Valo <kvalo@...nel.org>
CC: <linux-wireless@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>,
        <linux-hardening@...r.kernel.org>
Subject: Re: [RFC] wireless: ti: Can we just remove this flexible array?

On 3/20/2024 2:03 AM, Johannes Berg wrote:
> On Tue, 2024-03-19 at 18:42 -0600, Gustavo A. R. Silva wrote:
>>
>>>> -       /* payload */
>>>> -       u8 data[];
>>>>    } __packed;
>>>
> 
> Why not keep (or even add in the cases where it's not) the comment
> though?

For something called <foo>_header isn't it implicit that something will
probably follow?