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] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 16 Oct 2023 11:39:46 +1100
From:   Stephen Rothwell <>
To:     Rodrigo Siqueira Jordao <>
Cc:     Alex Deucher <>,
        "Wentland, Harry" <>,
        "Lei, Jun" <>,
        "Dhere, Chaitanya" <>,
        "Zhuo, Qingqing" <>,
        Alex Deucher <>,
        Roman Li <>,
        Linux Kernel Mailing List <>,
        Linux Next Mailing List <>
Subject: Re: linux-next: build failure after merge of the amdgpu tree

Hi Rodrigo,

On Tue, 10 Oct 2023 15:14:46 -0600 Rodrigo Siqueira Jordao <> wrote:
> I think I have a fix for that, but some things are unclear to me. I'm
> only able to see this issue when using allmodconfig. Additionally,
> when I inspected the function, it had a few local variables, not
> enough to explode the stack size fwiu. Is there any option in the
> allmodconfig that makes it easy to see this issue? Maybe something
> that I'm missing in my custom config file? Is it possible that
> allmodconfig enables some option that might increase the stack size?
> Perhaps the FPU flags from GCC include something else in the stack?
> Also, for investigating this issue, I'm considering the local
> variables, but as you can see from dml_core_mode_support, it has a
> few pointers. Am I missing something?

This could possibly be caused by inlining of other functions that are
static within the same file.

Other than that, I am also at a loss.
Stephen Rothwell

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists