On Wed, Sep 26, 2018 at 5:43 PM Kees Cook <keescook@xxxxxxxxxxxx> wrote:
> On Wed, Sep 26, 2018 at 2:51 AM, Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> wrote:
>
> I think the depth warning is minor (90 bytes over), so I don't think
> it's high priority to backport the fix. I'm fine either way, of
> course.
The way I see these warnings, anything that is close to 1 kilobyte of
stack usage
is a serious issue. The warning limit was just picked because we have some
existing functions that are known to be safe and close to the limit.
Arnd
