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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 21 Sep 2021 08:55:59 +0300
From:   Kalle Valo <>
To:     "Gustavo A. R. Silva" <>
Cc:     Len Baker <>,
        Arend van Spriel <>,
        Franky Lin <>,
        Hante Meuleman <>,
        Chi-hsien Lin <>,
        Wright Feng <>,
        Chung-hsien Hsu <>,
        "David S. Miller" <>,
        Jakub Kicinski <>,
        "Gustavo A. R. Silva" <>,
        Kees Cook <>,
        Shawn Guo <>,,,,,,
Subject: Re: [PATCH] brcmfmac: Replace zero-length array with flexible array member

Kalle Valo <> writes:

> "Gustavo A. R. Silva" <> writes:
>> On Sat, Sep 04, 2021 at 11:22:17AM +0200, Len Baker 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].
>>> Also, make use of the struct_size() helper in devm_kzalloc().
>>> [1]
>>> [2]
>>> Signed-off-by: Len Baker <>
>> Reviewed-by: Gustavo A. R. Silva <>
>> I'll take this in my -next tree. :)
> Why? It should go to wireless-drivers-next.

Gustavo, so have you dropped this from your tree now? I do not want to
get any conflicts because of this.

I'll reiterate again: do not take any patches touching
drivers/net/wireless unless I have acked them.


Powered by blists - more mailing lists