Compiler recursion guard warning bypass via closures

[HackingRepo]

Hello, The rust team

I try the fallowing code

fn call<F: Fn()>(f: F) -> () {
    f();
}

fn main() {
    call(|| {
        self::main();
    });
}

or

fn main() {
    let a = || {
        self::main()
    };
    a();
}

I get PS E:\Programming\Rust\testrust> cargo run

thread 'main' (18180) has overflowed its stack

In os level this safe but the problem in bare metal can be corrupt the stack an attacker can exploit this.

My rust version

PS E:\Programming\Rust\testrust> rustc --version --verbose
rustc 1.91.0 (f8297e351 2025-10-28)
binary: rustc
commit-hash: f8297e351a40c1439a467bbbb6879088047f50b3
commit-date: 2025-10-28
host: x86_64-pc-windows-msvc
release: 1.91.0
LLVM version: 21.1.2
PS E:\Programming\Rust\testrust\src> 

[bjorn3]

in bare metal can be corrupt the stack an attacker can exploit this.

That is why flip-link exists to make it a reliable crash on bare metal too.

Compiler recursion guard warning bypass via closures

This warning is just a lint for the most basic subset of recursion (guaranteed self-recursion). There are many valid use cases of recursion that can still trigger a stack overflow as well as many cases where recursion is not caught by this lint. This is not a bug. The lint is merely an attempt at catching some easy to catch mistakes. It is not a thorough protection.

[hanna-kruppe]

This is another instance of #57965