linux-kernel - Reference to non-existing CONFIG_X86_FEATURE_CALL

lists.openwall.net		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-next>] [day] [month] [year] [list]

Message-ID: <CAKXUXMx3cgTA66h_ezNTqyVo_Oa-Q0H=FeBM64zntZ4E0YCT6g@mail.gmail.com>
Date:   Mon, 31 Oct 2022 10:14:03 +0100
From:   Lukas Bulwahn <lukas.bulwahn@...il.com>
To:     Thomas Gleixner <tglx@...utronix.de>,
        Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
        X86 ML <x86@...nel.org>
Cc:     Dave Hansen <dave.hansen@...ux.intel.com>,
        "H. Peter Anvin" <hpa@...or.com>,
        kernel-janitors <kernel-janitors@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Reference to non-existing CONFIG_X86_FEATURE_CALL_DEPTH

Dear Thomas, dear Peter,

in your work on call depth tracking mitigation, commit 5d8213864ade
("x86/retbleed: Add SKL return thunk") on linux-next references the
configuration symbol CONFIG_X86_FEATURE_CALL_DEPTH, which is not
introduced in any Kconfig file.

Is this just some left-over from some previous iteration of this
feature or is there still a patch to come that will introduce that
configuration symbol in some Kconfig file?

This issue was identified with ./scripts/checkkconfigsymbols.py.

Best regards,

Lukas