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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 01 Apr 2022 14:43:26 +0300
From:   Kalle Valo <>
To:     "Gustavo A. R. Silva" <>
Cc:     "Gustavo A. R. Silva" <>,
        Kees Cook <>,
        Luca Coelho <>,
        "David S. Miller" <>,
        Jakub Kicinski <>,,,,
Subject: Re: [PATCH][next] iwlwifi: fw: Replace zero-length arrays with flexible-array members

"Gustavo A. R. Silva" <> writes:

> On 3/28/22 00:47, Kalle Valo wrote:
>> "Gustavo A. R. Silva" <> writes:
>>> On Wed, Feb 16, 2022 at 12:35:14PM -0800, Kees Cook wrote:
>>>> On Wed, Feb 16, 2022 at 01:50:15PM -0600, Gustavo A. R. Silva wrote:
>>>>> There is a regular need in the kernel to provide a way to declare
>>>>> having a dynamically sized set of trailing elements in a structure.
>>>>> Kernel code should always use “flexible array members”[1] for these
>>>>> cases. The older style of one-element or zero-length arrays should
>>>>> no longer be used[2].
>>>>> [1]
>>>>> [2]
>>>>> Link:
>>>>> Signed-off-by: Gustavo A. R. Silva <>
>>>> Reviewed-by: Kees Cook <>
>>> Hi all,
>>> Friendly ping: can someone take this, please?
>>> ...I can take this in my -next tree in the meantime.
>> Like we have discussed before, please don't take any wireless patches to
>> your tree. The conflicts just cause more work of us.
> Sure thing. I just removed it from my tree.
> I didn't get any reply from wireless people in more than a month, and
> that's why I temporarily took it in my tree so it doesn't get lost. :)

That increases the risk of conflicts and, because of multiple trees we
have, the conflicts cause more work for us. Please don't take ANY
wireless patches to your tree (or any other tree for that matter) unless
Johannes or me has acked them.

If you don't get reply to your patch for few weeks (and the merge window
is not open), you can ping in the list or contact me.


Powered by blists - more mailing lists