linux-kernel - Re: [PATCH] Reset task stack state in bringup

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-prev] [day] [month] [year] [list]

Date:   Sat, 11 Mar 2023 21:29:06 +0100
From:   Johannes Berg <johannes@...solutions.net>
To:     David Woodhouse <dwmw2@...radead.org>, mark.rutland@....com,
        Richard Weinberger <richard@....at>,
        Anton Ivanov <anton.ivanov@...bridgegreys.com>,
        linux-um@...ts.infradead.org
CC:     catalin.marinas@....com, dvyukov@...gle.com,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        peterz@...radead.org, quic_qiancai@...cinc.com,
        valentin.schneider@....com, will@...nel.org, woodylin@...gle.com
Subject: Re: [PATCH] Reset task stack state in bringup_cpu()




>Hm, in the !CONFIG_GENERIC_SMP_IDLE_THREAD case, idle_thread_get() will
>have returned NULL. Won't these then crash?
>
>Admittedly that seems to be *only* for UM, as all other architectures
>with SMP seem to set CONFIG_GENERIC_SMP_IDLE_THREAD.

UM doesn't even have SMP, so maybe CONFIG_GENERIC_SMP_IDLE_THREAD can just be removed?

johannes 
-- 
Sent from my phone.