On 03/21/2018 08:58 AM, Johannes Berg wrote:
On Wed, 2018-03-21 at 08:57 -0500, Gustavo A. R. Silva wrote:
SHA_DESC_ON_STACK is currently being used in multiple places. But, yeah,
I think we can define multiple macros of the same kind and adjust to the
characteristics of each the component.
On 03/21/2018 08:48 AM, Johannes Berg wrote:
On Wed, 2018-03-21 at 08:42 -0500, Gustavo A. R. Silva wrote:
In preparation to enabling -Wvla, remove VLAs and replace them
with dynamic memory allocation instead.
The use of stack Variable Length Arrays needs to be avoided, as they
can be a vecto
In preparation to enabling -Wvla, remove VLAs and replace them
with dynamic memory allocation instead.
The use of stack Variable Length Arrays needs to be avoided, as they
can be a vector for stack exhaustion, which can be both a runtime bug
or a security flaw. Also, in general, as code evolves it
On Wed, 2018-03-21 at 08:57 -0500, Gustavo A. R. Silva wrote:
>
> SHA_DESC_ON_STACK is currently being used in multiple places. But, yeah,
> I think we can define multiple macros of the same kind and adjust to the
> characteristics of each the component.
>
> How big do you think tfm can get?
I
On Wed, 2018-03-21 at 08:42 -0500, Gustavo A. R. Silva wrote:
> In preparation to enabling -Wvla, remove VLAs and replace them
> with dynamic memory allocation instead.
>
> The use of stack Variable Length Arrays needs to be avoided, as they
> can be a vector for stack exhaustion, which can be bot
